| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1682
|
12 Sep 2019 |
Pintaudi Giorgio | Info | History panels in custom pages | > > A new tag has been implemented to display
history panels in custom pages, integrated
in the
|
|
|
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
|
|
|
1684
|
13 Sep 2019 |
Pintaudi Giorgio | Info | History panels in custom pages | Dear Stefan,
thank you very much for the prompt reply.
Your suggestions worked wonderfully. Now |
|
|
2166
|
12 May 2021 |
Pierre Gorel | Bug Report | History formula not correctly managed | OS: OSX 10.14.6 Mojave
MIDAS: Downloaded from repo on April 2021.
|
|
|
2201
|
02 Jun 2021 |
Konstantin Olchanski | Bug Report | History formula not correctly managed | > OS: OSX 10.14.6 Mojave
> MIDAS: Downloaded from repo on April 2021.
>
|
|
|
1719
|
06 Oct 2019 |
Nik Berger | Bug Report | History data size mismatch | Logging a list of variables to the history
via links in the history ODB subtree,
we get messages as follows at every run start:
|
|
|
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 |
|
|
1721
|
10 Oct 2019 |
Konstantin Olchanski | Bug Report | History data size mismatch | >
> In our history, a long list of doubles
(64 Bit) fas followed by three floats (32 |
|
|
1722
|
10 Oct 2019 |
Nik Berger | 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 |
|
|
1723
|
10 Oct 2019 |
Stefan Ritt | Bug Report | History data size mismatch | > Yes, we could have
> kept that apart, yes, in this case a double
would also work (and not break things), but |
|
|
473
|
23 Mar 2008 |
Konstantin Olchanski | Info | History SQL database poll: MySQL, PgSQL, ODBC? | I would like to hear from potential users
on which SQL database would be
preferable for storage of MIDAS history data.
|
|
|
Draft
|
20 Jun 2017 |
Richard Longland | Forum | High Rate | |
|
|
2595
|
08 Sep 2023 |
Nick Hastings | Forum | Hide start and stop buttons | The wiki documents an odb variable to enable
the hiding of the Start and Stop buttons
on the mhttpd status page
|
|
|
2596
|
08 Sep 2023 |
Nick Hastings | Forum | Hide start and stop buttons | > Is there now some other mechanism to hide
the start and stop buttons?
> Note that this is for a pure slow control |
|
|
2599
|
13 Sep 2023 |
Stefan Ritt | Forum | Hide start and stop buttons | Indeed the ODB settings are obsolete. Now
that the status page is fully dynamic
(JavaScript), it's much more powerful to |
|
|
2600
|
13 Sep 2023 |
Nick Hastings | Forum | Hide start and stop buttons | Hi Stefan,
> Indeed the ODB settings are obsolete.
|
|
|
2601
|
13 Sep 2023 |
Stefan Ritt | Forum | Hide start and stop buttons | > Hi Stefan,
>
> > Indeed the ODB settings are obsolete.
|
|
|
2602
|
14 Sep 2023 |
Konstantin Olchanski | Forum | Hide start and stop buttons | I believe the original "hide run start / stop"
was added specifically for ND280 GSC MIDAS.
I do not know
|
|
|
2603
|
14 Sep 2023 |
Nick Hastings | Forum | Hide start and stop buttons | Hi
> > > Indeed the ODB settings are obsolete.
|
|
|
2604
|
14 Sep 2023 |
Stefan Ritt | Forum | Hide start and stop buttons | > I believe the original "hide run start /
stop" was added specifically for ND280 GSC
MIDAS. I do not know
|
|