m-stgt

Problem solved. rexxref.pdf of ooRexx 4.2.0 describes in 8.11 SysCreateEventSem about argument 'name': If you omit name, SysCreateEventSem creates an unnamed, shared event semaphore. I concluded, w/ name it creates an event semaphore that is not shared. Moreover: SysCreateEventSem returns a null string ("") if the semaphore cannot be created or already exists. Using the same name within SysCreateEventSem in another program returned a handle, not a null string. Thus a semaphore with that name does...

TY for the hint about the thread with almost identical topic. It is very instructive, e. g. SysRequestMutexSem rc = 128 (= abandoned) was new to me (missing in 4.2.0 reference). But, frankly, I doubt a bit when you say All semaphores are system-wide and visible to every program in the operating system. That's their purpose. Maybe I simply wasn't aware of this fact, and up to now had no interference between semaphores. I use two in the same program, one with "tripple use" as described in OP, the other...

Chapter B.2.1 "RexxUtil Semaphore functions" in ooRexx Documentation 5.0.0, Open Object Rexx Reference lists several deprecated functions which are superseded by EventSemaphore Class and MutexSemaphore Class. While I currently try to make sure some of my programs will work with ooRexx 5.2.0 too, two questions arise about EventSemaphores. 1) I use SysWaitEventSem simultaneously to i) end the thread in case of shutdown, ii) throttle CPU usage by check only 5 times a second if there is something to...

but I should think it'd be much easier to see some aspects of what it's doing by dumping storage (to find rexx's variable storage) when it is running. TY for this hnt. Now I'm diving into Sysinternals -- currently as obscure for me as rexxc output.

When I publish a "running phase" or "codeless executable" prepared with rexxc, would it be possible to extract data from it that is included as Array Term. How much effort would it take to disentangle how array terms are converted by rexxc? Why I ask? When I look into the output of rexxc I easily spot many strings while all else is pretty obscure (for me). Two strings I found are numbers, 9821 and .211327 what is for those interested in HP pocket calculators an unmissable hint which simple and well-known...

The version of ooDialog distributed in ooRexx 5.2.0 is ooDialog 4.2.3.

Settings like 'numeric digits' or 'signal on' are always local to methods It's even local to subroutines. Example: call nutsup /* get firmware and more */ numeric digits 15 /* fails if in nutsup: */ Took quite a while untuil I grasped numeric digits can't be set in a setup subroutine.

Hello Erich, ty for taking your time to look into this strange behaviour. First: your example works here as expected. Then: by "failure" I mean the returned value is (newly) always 0, no matter if Ctrl is pressed or not. It's a "soft" failure, w/o error message. My code which worked so far: /* act on "Remove" button */ ::method RRF unguarded expose pgd. PGnum NumPG select when pgd.PGnum.1 <> pgd., , 1 - .Keyboard~getAsyncKeyState(.VK~CONTROL), then dc = RxMessageBox('To remove a nonempty page press...