| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1629
|
23 Jul 2019 |
Stefan Ritt | Forum | How to convert C midas frontends to C++ | Have you left any "extern C" in your frontend
program or in any of the used header file.
Seems
|
|
|
1637
|
30 Jul 2019 |
Stefan Ritt | Forum | How to convert C midas frontends to C++ (my problem solved) | > as a side comment, not all drivers are c++
compatible yet (e.g. mscbvr), so changes
needed are small
|
|
|
1638
|
30 Jul 2019 |
Stefan Ritt | Info | Limitations of MSL | > Would it be possible to add something like
the following?
> 343 if (!isdigit(value1_var[i]) && value1_var[i] |
|
|
1639
|
01 Aug 2019 |
Stefan Ritt | Forum | How to convert C midas frontends to C++ (my problem solved) | >
> Ok, so the detail that I missed was that
the dummy functions
|
|
|
1640
|
05 Aug 2019 |
Stefan Ritt | Info | Precedence of equipment/common structure | Today I fixed a long-annoying problem. We
have in each front-end an equipment structure
|
|
|
1643
|
06 Aug 2019 |
Stefan Ritt | Info | Precedence of equipment/common structure | Hi Thomas,
the change only affects Eqipment/<name>/common |
|
|
1644
|
06 Aug 2019 |
Stefan Ritt | Info | Precedence of equipment/common structure | After some internal discussion, I decided
to undo my previous change again, in order
not to break existing habits. Instead, I |
|
|
1652
|
08 Aug 2019 |
Stefan Ritt | Suggestion | midas cmake migration | Each CMakeLists.txt should specify which version
of CMake it requires. The MIDAS CMakeLists.txt
requires CMake 3.1 or later.
|
|
|
1655
|
08 Aug 2019 |
Stefan Ritt | Suggestion | midas cmake migration | I just tried CMake 3.1.0 and it worked with
midas. So I believe all versions between
3.1.0 and 3.6.1 are ok.
|
|
|
1661
|
13 Aug 2019 |
Stefan Ritt | Info | Precedence of equipment/common structure | > Lacking any ideas for improvements, I vote
for the status quo. (plus a review of the
documentation to ensure we have clearly
|
|
|
1662
|
14 Aug 2019 |
Stefan Ritt | Info | New history plot facility | During my visit at TRIUMF we rewrote the history
plotting functionality of midas. Instead
of
|
|
|
1666
|
28 Aug 2019 |
Stefan Ritt | Forum | History plot problems for frontend with multiple indicies | My first question would be why are you using
several font-ends at all? That makes things
more
|
|
|
1674
|
06 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > 1) it would be nice to have an option to
format the label output (see attachment 1)
|
|
|
Draft
|
07 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > This I found out, yet the attachment here
shows another case where it would be useful
to be |
|
|
1678
|
07 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > This I found out, yet the attachment here
shows another case where it would be useful
to be
|
|
|
1679
|
08 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > 1) it would be nice to have an option to
format the label output (see attachment 1)
|
|
|
1683
|
12 Sep 2019 |
Stefan Ritt | Info | History panels in custom pages | Indeed there was a bug in some JavaScript
code, which I fixed here: https://bitbucket.org/tmidas/midas/commits/d2b1a783240e252820c622001e15c09c5d7798c0
|
|
|
1690
|
16 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > Also the new system is still incomplete,
i.e. there is no trivial way to save a history
plot into a file:
|
|
|
1702
|
26 Sep 2019 |
Stefan Ritt | Forum | Open a hotlink to a single element in an ODB array | [quote="Pintaudi Giorgio"]Hello!
Just a little question about the ODB hotlinks.
Is it possible to open a hotlink
|
|
|
1720
|
06 Oct 2019 |
Stefan Ritt | Bug Report | History data size mismatch | I wonder why do you this via ODB links. The
"standard" way of writing to the history
should be to create events for an equipment |
|