| ID | Date | Author  | Topic | Subject | Text |  | 
| 2531 | 13 Jun 2023 | Thomas Senger | Forum | Include subroutine through relative path in sequencer | Hi, I would like to restructure our sequencer scripts and the paths. Until now many things
 are not generic at all. I would like to ask
 |  | 
| 2753 | 03 May 2024 | Thomas Senger | Suggestion | Possible addition to IF Statements | Hello there, in our setup we use many variables with many
 different exceptions. Would it be possible
 |  | 
| 2776 | 21 May 2024 | Thomas Senger | Bug Report | Params not initialized when starting sequencer | Hi all, On develop, the issue seems to be still there
 and is not fixed.
 |  | 
| 2779 | 22 May 2024 | Thomas Senger | Bug Report | Params not initialized when starting sequencer | Hi Zaher, thanks for your help.
 I just tried the bug fix, but it still seems
 |  | 
| 904 | 13 Sep 2013 | Thomas Lindner | Bug Report | mhttpd truncates string variables to 32 characters | I find that new mhttpd has strange behaviour for ODB strings.
 
 |  | 
| 1054 | 13 May 2015 | Thomas Lindner | Forum | Check if Client is running from Javascript | [quote="Andreas Suter"]Is there currently an easy way to check from javascript if a
 midas client is
 |  | 
| 1072 | 16 Jul 2015 | Thomas Lindner | Bug Report | jset/ODBSet using true/false for booleans | MIDAS does not seem to be consistent (or at least convenient) with how it
 handles booleans in AJAX functions.
 |  | 
| 1098 | 20 Aug 2015 | Thomas Lindner | Bug Report | MIDAS message page auto-size (horizontally) is annoying | New version of MIDAS has a feature where it seems to automatically resize the
 message page horizontally in order to fix
 |  | 
| 1100 | 21 Aug 2015 | Thomas Lindner | Info | mhttpd HTTPS/SSL server updated | > > I recommend that you use "mhttpd --mg"
 as the alternative for running "mhttpd -p"
 |  | 
| 1107 | 09 Sep 2015 | Thomas Lindner | Info | mhttpd HTTPS/SSL server updated | > > > > I find that I don't understand this recommendation
 to use secure mongoose
 |  | 
| 1108 | 09 Sep 2015 | Thomas Lindner | Info | mhttpd/SSL error message on MacOS | On my macbook (OS X 10.10.3) I get this error message when starting mhttpd with mongoose-SSL:
 
 |  | 
| 1109 | 09 Sep 2015 | Thomas Lindner | Info | Documentation regarding specifying custom pages | Hi, 
 We have recently been changing the code in
 |  | 
| 1159 | 05 Feb 2016 | Thomas Lindner | Suggestion | reducing sleep time in mhttpd main loop (for sequencer) | There were some complaints that the MIDAS sequencer was slow.  Specifically, the
 complaint was that even lines in the sequence
 |  | 
| 1160 | 05 Feb 2016 | Thomas Lindner | Suggestion | reducing sleep time in mhttpd main loop (for sequencer) | > There were some complaints that the MIDAS sequencer was slow.  Specifically, the
 > complaint was that even lines in the sequence
 |  | 
| 1162 | 15 Feb 2016 | Thomas Lindner | Suggestion | reducing sleep time in mhttpd main loop (for sequencer) | > > I checked how much extra CPU was used
 if the sleep was reduced from 100ms to
 |  | 
| 1169 | 10 Mar 2016 | Thomas Lindner | Info | New rootana forum | rootana web display tools | We have started a new elog for discussions
 of the ROOTANA MIDAS analyzer package
 |  | 
| 1177 | 11 May 2016 | Thomas Lindner | Info | MacOS 10.11 (El Capitan) openssl compilation errors | I recently upgraded my macbook to MacOS 10.11. The compilation of MIDAS failed after the
 upgrade,
 |  | 
| 1217 | 25 Oct 2016 | Thomas Lindner | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail | > > I've recently run into issues when using JSON.parse on ODB keys containing
 > > 8-bit data.
 |  | 
| Draft | 04 Nov 2016 | Thomas Lindner | Bug Report | problem with error code DB_NO_MEMORY from  db_open_record() call when establish additional hotlinks | Hi Tim, 
 I reproduced your problem and then managed
 |  | 
| 1220 | 04 Nov 2016 | Thomas Lindner | Bug Report | problem with error code DB_NO_MEMORY from  db_open_record() call when establish additional hotlinks | Hi Tim, 
 I reproduced your problem and then managed
 |  |