I’m seeing a bug (or is it by design?) where a movable modal isn’t modal unless called by the ShowModal method (then, code won’t continue unless I use a timer or other techniques to call the rest of the code).
In Xojo, there is the “frame” property (Movable modal/Modal dialog) and the method (ShowModal/ShowModalWithin), so four cases:
1: frame=movable modal, called with ShowModal: shows a modal window (visually) and prevents other windows to be brought to the front.
2: frame=movable modal, called with Show, but not ShowModal: shows a visually modal window but acts like a document window (can be put to the background).
3: frame≠movable modal, called with ShowModal: this only implies the code waits for the window to hide, be it any kind of window.
4: frame≠movable modal, called without ShowModal: normal cases for documents/floating windows.
Other than seeming like a mess because the same word is used twice for different meanings, none of these cases permit to show a modal window (i.e. preventing other apps to be brought to the front) while not stopping the code flow.
I would have expected case 2 to do that but the frame “modal” alone (without calling ShowModal) treats the window like a regular one. What’s the purpose of this frame type if it depends on how the window is shown?
Can it not be a bug?