| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2151
|
13 Apr 2021 |
Stefan Ritt | Forum | Client gets immediately removed when using a script button. | > I have followed your suggestions and the
program still stops immediately. My status
as returned from "cm_yield(100)" is always |
|
|
2150
|
13 Apr 2021 |
Konstantin Olchanski | Info | bk_init32a data format | Until commit a4043ceacdf241a2a98aeca5edf40613a6c0f575
today, mdump mostly did not work with bank32a
data.
|
|
|
2149
|
13 Apr 2021 |
Isaac Labrie Boulay | Forum | Client gets immediately removed when using a script button. | > I think it would be useful to find the minimal
example that exhibits this behaviour.
>
|
|
|
2148
|
12 Apr 2021 |
Ben Smith | Forum | Client gets immediately removed when using a script button. | I think it would be useful to find the minimal
example that exhibits this behaviour.
|
|
|
2147
|
12 Apr 2021 |
Isaac Labrie Boulay | Forum | Client gets immediately removed when using a script button. | > > if I use the script button, the logic_controller
program is immediately deleted by MIDAS.
>
|
|
|
2146
|
12 Apr 2021 |
Ben Smith | Forum | Client gets immediately removed when using a script button. | > if I use the script button, the logic_controller
program is immediately deleted by MIDAS.
|
|
|
2145
|
12 Apr 2021 |
Isaac Labrie Boulay | Forum | Client gets immediately removed when using a script button. | Hi all,
I'm running into a curious problem when I |
|
|
2144
|
09 Apr 2021 |
Lars Martin | Suggestion | Time zone selection for web page | The new history as well as the clock in the
web page header show the local time
of the user's computer running the browser.
|
|
|
2143
|
05 Apr 2021 |
Konstantin Olchanski | Info | blog - convert mfe frontend to tmfe c++ framework | Result is here:
https://bitbucket.org/expalpha/chronobox_software/src/master/fechrono_tmfe.cxx
|
|
|
2142
|
05 Apr 2021 |
Konstantin Olchanski | Info | blog - convert mfe frontend to tmfe c++ framework | notes from converting ALPHA-g chronobox frontend
fechrono to tmfe c++ framework.
|
|
|
2141
|
04 Apr 2021 |
Konstantin Olchanski | Info | Change of TID_xxx data types | >
> To be consistent, I renamed the old types:
>
|
|
|
2140
|
04 Apr 2021 |
Konstantin Olchanski | Info | bk_init32a data format | In April 4th 2020 Stefan added a new data
format that fixes the well known problem
with alternating banks being
|
|
|
2139
|
30 Mar 2021 |
Konstantin Olchanski | Forum | INT INT32 in experim.h | > >
> > /* define integer types with explicit
widths */
|
|
|
2138
|
30 Mar 2021 |
Konstantin Olchanski | Info | INT64/UINT64/QWORD not permitted in ODB and history... Change of TID_xxx data types | > We have to request of a 64-bit integer data
type to be included in MIDAS banks.
> Since 64-bit integers are on some systems |
|
|
2137
|
25 Mar 2021 |
Lars Martin | Bug Report | Minor bug: Change all time axes together doesn't work with +- buttons | Version: release/midas-2020-12
In the new history display, the checkbox |
|
|
2136
|
24 Mar 2021 |
Lars Martin | Bug Report | Time shift in history CSV export | I think from my perspective the separate files
are fine. I personally don't really like
the format
|
|
|
2135
|
24 Mar 2021 |
Stefan Ritt | Bug Report | Time shift in history CSV export | I confirm there is a problem. If variables
are from the same equipment, they have the
same
|
|
|
2134
|
23 Mar 2021 |
Lars Martin | Bug Report | Time shift in history CSV export | Tried with export of two different time ranges,
and the shift appears to remain the same,
|
|
|
2133
|
23 Mar 2021 |
Lars Martin | Bug Report | Time shift in history CSV export | History is from two separate equipments/frontends,
but both have "Log history" set to 1. |
|
|
2132
|
23 Mar 2021 |
Lars Martin | Bug Report | Time shift in history CSV export | Version: release/midas-2020-12
I'm exporting the history data shown in elog:2132/1 |
|