You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected Behavior:
The main window should ignore all user inputs while file dialogs are open, but should still be "responsive" and not halt the program. This would prevent accidental changes while the dialog is open, but would ensure that the program behaves.
Observed Behavior:
When opening a file dialog, the main window is marked "unresponsive" by the OS. Attempting to move or resize the main window with a dialog open results in graphical artifacts. CPU usage of the "AppRun" process drops to 0% when a dialog is open. This has been present since atleast release 0.13.0, and has persisted through the custom file dialogs, tinyfiledialogs, and nativefiledialogs/sbus versions/releases.
Workaround: Click "wait" or dismiss the message after the dialogue is closed. Save frequently between imports. Do not click Force Quit until you have saved.
Program becoming Unresponsive with open dialog:
Normal CPU utilization with no dialog open:
0% CPU utilization with open dialog:
The text was updated successfully, but these errors were encountered:
You may see me use dialogue/dialog interchangably, dialog is shorthand.
Using action ci #405 AppImage.
Expected Behavior:
The main window should ignore all user inputs while file dialogs are open, but should still be "responsive" and not halt the program. This would prevent accidental changes while the dialog is open, but would ensure that the program behaves.
Observed Behavior:
When opening a file dialog, the main window is marked "unresponsive" by the OS. Attempting to move or resize the main window with a dialog open results in graphical artifacts. CPU usage of the "AppRun" process drops to 0% when a dialog is open. This has been present since atleast release 0.13.0, and has persisted through the custom file dialogs, tinyfiledialogs, and nativefiledialogs/sbus versions/releases.
Workaround: Click "wait" or dismiss the message after the dialogue is closed. Save frequently between imports. Do not click Force Quit until you have saved.
Program becoming Unresponsive with open dialog:
Normal CPU utilization with no dialog open:
0% CPU utilization with open dialog:
The text was updated successfully, but these errors were encountered: