I have a template that opens webhelp for procedures.
Today I discovered that if I had two procedures , browse + form, that each had the same ALERT
statement, the second statement deactivated the first.
Help says ALERT should work for the currently active window, but apparently, it overrwrites the scope? Is this supposed to be?
I used 0{Prop:Alrt,255}=MyHelpCode to work around it.
Using Clarion 10.
Is it maybe just where you placed the code? Like in the form, if you had the ALERT before opening the form window, I think it would act on the current window, which would be the browse window?
Unfortunately, no. The code is placed after opening window, right before the call to SetAlerts. Event if I had misplaced it, it should work in the first procedure, but that is where it stops working after returning from the form.
I am not able to reproduce in a minimal application, so it is probably something else disturbing it.
Do you also have a PROP:Alrt on a FEQ that you might have selected after returning from the form? Maybe there’s some competition there?
I found it
The most likely reason was an emtpy ALERT() somewhere.
I have a lot of 3rdParty accessoiries in the application, my own included, and it was my own, old listboxformatter that had an empty ALERT when killed.
Found it searching with Notepad++