-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Related to #59.
The fix for #59 is still not satisfactory. The FLExTools window does come back to the fore, but because of the last processing that a module has to do, the FLExTools window may not come back for a couple seconds. I think it can be confusing to the user because the QT window is gone and so is the FLExTools window and they wonder what happened. Can we explore another fix that would keep the FLExTools window from going to the back at all?
In the case of the FLExTrans Settings window, the FLExTools window never comes back to the fore so the user has to hunt for it to bring it back. I've now implemented the same user32.SetForegroundWindow(hwnd) fix as done with the 2nd commit in #59 and that seems to bring it back after some delay.