A while ago I posted a msg on the webboard about the above as follows:
If the cursor is within a get field in an editable browse, a first click on a pushbutton exits the get field but does not activate the button so a second click is then needed to activate the button...
The push button already has a CARGO "CANCEL" on it but that does nothing in this instance.
Is this known behaviour? Is there any way around it?
Your reply was:
Yes, this has been the behavior for many years because cell editing is done
in a sub loop rather than the main loop.
If I had it to do over again, I would have done it differently but I didn't
know as much back then (9 years ago) as I do now.
Tell me what version of eXpress++ you are using and I'll give you a change
to the source code that may be a sufficient workaround for you.
And now that we've updated to build 253 can you perhaps let me know what the workaround may be?