| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2915
|
04 Dec 2024 |
Konstantin Olchanski | Bug Report | ODB key picker does not close when creating link / Edit-on-run string box too large | > > Actual result:
> > The key picker does not close.
>
|
|
|
2916
|
05 Dec 2024 |
Konstantin Olchanski | Bug Report | ODB key picker does not close when creating link / Edit-on-run string box too large | > > Another more minor visual problem is the
edit-on-start dialog. There seems to be no
upper bound to the
|
|
|
1953
|
18 Jun 2020 |
Ruslan Podviianiuk | Forum | ODB key length | Hello,
I have a question about length of the name |
|
|
1954
|
18 Jun 2020 |
Stefan Ritt | Forum | ODB key length | No. But if you need more than 32 characters,
you do something wrong. The
information you want to put into the ODB |
|
|
2365
|
23 Mar 2022 |
Hunter Lowe | Forum | ODB has issue with example analyzer | Trying to play with midas file but I get error:
[Analyzer,ERROR] [odb.cxx:845:db_validate_name,ERROR] |
|
|
1367
|
04 May 2018 |
Francesco Renga | Forum | ODB full | Dear expert,
I'm developing a frontend and I'm getting
this kind of error at each event:
|
|
|
1368
|
04 May 2018 |
Stefan Ritt | Forum | ODB full | Two options:
1) Do NOT send your events into the ODB. |
|
|
1378
|
20 Jul 2018 |
Konstantin Olchanski | Forum | ODB full | Concurrence.
Normally, MIDAS data events are saved to |
|
|
1760
|
13 Jan 2020 |
Peter Kunz | Forum | ODB dump format: json - events 0x8000 and 0x8001 missing | MIDAS version: 2.1
GIT revision:
Tue Dec 31 17:40:14 2019 +0100 - midas-2019-09-i-1-gd93944ce-dirty |
|
|
1763
|
13 Jan 2020 |
Konstantin Olchanski | Forum | ODB dump format: json - events 0x8000 and 0x8001 missing | (Please post messages in "plain" mode, they
are much easier to answer)
|
|
|
1768
|
13 Jan 2020 |
Peter Kunz | Forum | ODB dump format: json - events 0x8000 and 0x8001 missing | Re: MIDAS versions
Thanks for pointing that out. I wasn't actually |
|
|
1772
|
13 Jan 2020 |
Konstantin Olchanski | Forum | ODB dump format: json - events 0x8000 and 0x8001 missing | For using the release branch read the messages
in this thread. Most of the time, the develop
branch is fine, except when we are developing |
|
|
202
|
24 Mar 2005 |
Stefan Ritt | Info | ODB dump format switched to XML | Dear midas users,
I have changed the ODB dump format to XML. |
|
|
203
|
29 Mar 2005 |
Stefan Ritt | Info | ODB dump format switched to XML | > All the XML functionality is implemented
in the new mxml.c/h library, which has
> been added to the distribution, and which |
|
|
204
|
31 Mar 2005 |
Konstantin Olchanski | Info | ODB dump format switched to XML | > > All the XML functionality is implemented
in the new mxml.c/h library
>
|
|
|
205
|
31 Mar 2005 |
Stefan Ritt | Info | ODB dump format switched to XML | > Looks like the midas mxml Makefile bits
did not make it to CVS. Current Makefile
> revision 1.67 does not have them and building |
|
|
3018
|
01 Apr 2025 |
Konstantin Olchanski | Bug Report | ODB corruption | We see ODB corruption crashes in the DS20k
vertical slice MIDAS instance.
|
|
|
Draft
|
01 Dec 2017 |
Frederik Wauters | Forum | ODB as JSON file and reverse | > Hi. Is it currently possible to automatically
save the MIDAS ODB as a JSON file?
> I can do it manually in odbedit, but it |
|
|
1193
|
07 Sep 2016 |
Wes Gohn | Forum | ODB as JSON file | Hi. Is it currently possible to automatically
save the MIDAS ODB as a JSON file?
I can do it manually in odbedit, but it looks |
|
|
1194
|
07 Sep 2016 |
Stefan Ritt | Forum | ODB as JSON file | > Hi. Is it currently possible to automatically
save the MIDAS ODB as a JSON file?
> I can do it manually in odbedit, but it |
|