Bug: Initial "Scanner" visible check/unchecked state in wrong state #131
Comments
cristian64
added a commit
to cristian64/dolphin-memory-engine
that referenced
this issue
May 12, 2024
…nt loop tick. Previously, the initial size of the main splitter was used to initialize the checkable action. However, that size is not accurate until the main window has been shown. The action is now initialized in the next event loop tick, when the GUI is ready. Fixes aldelaro5#131.
cristian64
added a commit
to cristian64/dolphin-memory-engine
that referenced
this issue
May 12, 2024
…nt loop tick. Previously, the initial size of the main splitter was used to initialize the checkable action. However, that size is not accurate until the main window has been shown. The action is now initialized in the next event loop tick, when the GUI is ready. Fixes aldelaro5#131.
cristian64
added a commit
that referenced
this issue
May 12, 2024
…nt loop tick. Previously, the initial size of the main splitter was used to initialize the checkable action. However, that size is not accurate until the main window has been shown. The action is now initialized in the next event loop tick, when the GUI is ready. Fixes #131.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The "Scanner" on a fresh install / no config of DME will incorrectly have the Scanner checkbox unchecked while the Scanner is shown, thus clicking it or pressing F3 will need to be done twice to hide it properly.
The text was updated successfully, but these errors were encountered: