| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2304
|
01 Dec 2021 |
Lars Martin | Bug Report | Off-by-one in sequencer documentation | The documentation for the sequencer loop says:
<quote>
|
|
|
2305
|
02 Dec 2021 |
Stefan Ritt | Bug Report | Off-by-one in sequencer documentation | > The documentation for the sequencer loop
says:
>
|
|
|
2315
|
26 Jan 2022 |
Konstantin Olchanski | Bug Report | Off-by-one in sequencer documentation | > > 3 LOOP n,4
> > 4 MESSAGE $n,1
> > 5 ENDLOOP
|
|
|
2319
|
26 Jan 2022 |
Stefan Ritt | Bug Report | Off-by-one in sequencer documentation | > Shades/ghosts of FORTRAN. c/c++/perl/python
loops loop from 0 to n-1.
|
|
|
2321
|
26 Jan 2022 |
Konstantin Olchanski | Bug Report | Off-by-one in sequencer documentation | > > Shades/ghosts of FORTRAN. c/c++/perl/python
loops loop from 0 to n-1.
>
|
|
|
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: |
|
|
2448
|
13 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: |
|
|
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
|
|
|
2282
|
30 Sep 2021 |
Francesco Renga | Forum | OPC client within MIDAS | Dear all,
I need to integrate in my MIDAS project
the communication with an OPC UA
|
|
|
2334
|
10 Feb 2022 |
Francesco Renga | Forum | OPC client within MIDAS | Dear all,
I finally succeeded to get a working
driver for the communication with an OPC |
|
|
3225
|
29 May 2026 |
Zaher Salman | Info | ODBvalue timeout | Dear all, I implemented an optional timeout
for the wait ODBvalue command. The way it
works is similar to the standard wait command:
|
|
|
3226
|
29 May 2026 |
Stefan Ritt | Info | ODBvalue timeout | > Dear all, I implemented an optional timeout
for the wait ODBvalue command. The way it
works is similar to the standard wait command:
|
|
|
3227
|
29 May 2026 |
Zaher Salman | Info | ODBvalue timeout | >
> How can the MSL code figure out if the
wait succeeded or timed out?
|
|
|
3228
|
29 May 2026 |
Stefan Ritt | Info | ODBvalue timeout | > >
> > How can the MSL code figure out if the
wait succeeded or timed out?
|
|
|
3229
|
29 May 2026 |
Zaher Salman | Info | ODBvalue timeout | > > >
> > > How can the MSL code figure out if
the wait succeeded or timed out?
|
|
|
3230
|
29 May 2026 |
Stefan Ritt | Info | ODBvalue timeout | > > > >
> > > > How can the MSL code figure out if
the wait succeeded or timed out?
|
|
|
403
|
29 Aug 2007 |
Konstantin Olchanski | Forum | ODBv3, second try - Midas on a x86_64 - incompatible with x86_32 | > > > I agree to make 32-bit and 64-bit compatible.
In the long run, everything will be 64-bit,
so I would suggest
|
|
|
417
|
21 Nov 2007 |
Konstantin Olchanski | Forum | ODBv3, second try - Midas on a x86_64 - incompatible with x86_32 |
These changes to make 32-bit and 64-bit ODB
binary compatible with each other are now |
|
|
3030
|
29 Apr 2025 |
Pavel Murat | Bug Report | ODBXX : ODB links in the path names ? | Dear MIDAS experts,
does the ODBXX interface to ODB currently |
|
|
3033
|
30 Apr 2025 |
Stefan Ritt | Bug Report | ODBXX : ODB links in the path names ? | Indeed this was missing from the very beginning.
I added it, please report back if it's not
working.
|
|