ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2455
|
08 Feb 2023 |
Stefan Ritt | Suggestion | histories capture 'ruy' | > The histories capture key events from 'r'
'u' 'y' and 'Escape' for various functions
like rescaling etc. However, this also means |
|
|
2454
|
31 Jan 2023 |
Stefan Ritt | Suggestion | "Soft interlock" possible? | > Is it possible to impose requirements on
certain output variables in an interlock-like
fashion? For example: "As long as the temperature |
|
|
2453
|
31 Jan 2023 |
Lukas Gerritzen | Suggestion | "Soft interlock" possible? | Is it possible to impose requirements on certain
output variables in an interlock-like fashion?
For example: "As long as the temperature |
|
|
2452
|
13 Jan 2023 |
Stefan Ritt | Suggestion | Debug printf remaining in mhttpd.cxx | These debug statements were added by K.O.
on June 24, 2021. He should remove it.
|
|
|
2451
|
13 Jan 2023 |
Denis Calvet | Suggestion | Debug printf remaining in mhttpd.cxx | Hi everyone,
It has been a long time since my last message. |
|
|
2450
|
17 Nov 2022 |
Konstantin Olchanski | Bug Fix | "Detected duplicate or non-monotonous data" in history files | > > serious (but rare) bug was fixed in the
history reader.
> previous fix was incomplete. please update |
|
|
2449
|
17 Nov 2022 |
Konstantin Olchanski | Bug Fix | O_CREAT in open in split.cxx | > > midas currently does not compile on linux
> > fix is to give open in midas/examples/lowlevel/split.cxx
a default mode, e.g. 006600
|
|
|
2448
|
12 Nov 2022 |
Stefan Ritt | Bug Fix | O_CREAT in open in split.cxx | > midas currently does not compile on linux
>
> /usr/include/x86_64-linux-gnu/bits/fcntl2.h:50:24: |
|
|
2447
|
11 Nov 2022 |
Frederik Wauters | Bug Fix | O_CREAT in open in split.cxx | midas currently does not compile on linux
/usr/include/x86_64-linux-gnu/bits/fcntl2.h:50:24: |
|
|
2446
|
05 Nov 2022 |
Zaher Salman | Suggestion | histories capture 'ruy' | The histories capture key events from 'r'
'u' 'y' and 'Escape' for various functions
like rescaling etc. However, this also means |
|
|
2445
|
29 Oct 2022 |
Stefan Ritt | Suggestion | read_only odbxx? | Ok, I implemented and committed that. Just
call
|
|
|
2444
|
26 Oct 2022 |
Lars Martin | Suggestion | read_only odbxx? | > Having a "const midas::odb" probably does
not work (at least I would not know how to
implement that).
|
|
|
2443
|
24 Oct 2022 |
Stefan Ritt | Suggestion | read_only odbxx? | > I really like the concept of the odbxx interface.
> I think it would be a nice feature if one
could have a read_only connection, e.g. by |
|
|
2442
|
22 Oct 2022 |
Lars Martin | Info | Allow onchange to refer to arbitrary js function | Actually, now that I look again, there is
a mistake in the instructions:
you say
|
|
|
2441
|
22 Oct 2022 |
Lars Martin | Suggestion | read_only odbxx? | I really like the concept of the odbxx interface.
I think it would be a nice feature if one
could have a read_only connection, e.g. by |
|
|
2440
|
22 Oct 2022 |
Lars Martin | Info | Allow onchange to refer to arbitrary js function | I figured I wasn't the first to have this
idea.
Works great, thanks! |
|
|
2439
|
14 Oct 2022 |
Ben Smith | Info | Allow onchange to refer to arbitrary js function | > I would like to use a function defined in
the <script> block of my custom page as an
onchange callback.
|
|
|
2438
|
14 Oct 2022 |
Lars Martin | Suggestion | Allow onchange to refer to arbitrary js function | Maybe this is already possible, I have a hard
time understanding the mhttpd source code.
|
|
|
2437
|
10 Oct 2022 |
Zaher Salman | Suggestion | JSON-RPC function to read files | Hello ,
The midas sequencer uses the function js_seq_list_files |
|
|
2436
|
23 Aug 2022 |
Konstantin Olchanski | Bug Fix | "Detected duplicate or non-monotonous data" in history files | > serious (but rare) bug was fixed in the
history reader.
|
|