Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prusa Slicer 2.3.1 not activating non-modal settings window if settings window is minimized #6548

Closed
clivius opened this issue May 23, 2021 · 2 comments

Comments

@clivius
Copy link

clivius commented May 23, 2021

Version

PS Version 2.3.1+win64

Operating system type + version

Windows 10Pro 2004 build 19041.985
I have dual monitors setup but I'm only working on one monitor with PS.

3D printer brand / version + firmware version (if known)

i3MK3S+ firmware 3.10

Behavior

I have my PS GUI set to use non-modal settings window. I noticed that If the Settings window is minimized to the taskbar, clicking on the Settings icon at the top of the graphics window or any of the gear icons in the right options window next to Print Settings/Fillament/Printer does not pop up the Settings window. Neither does pressing Ctrl + 2, 3 or 4. I have to activate first on the taskbar. Then if it's behind other windows, using any of the methods above will pop it on top and make it active.

It's very frustrating and I feel like this is a bug. Using any of those methods should pop up the settings window no matter what.

Thanks/Livius

@rtyr rtyr added the UI label May 24, 2021
YuSanka added a commit that referenced this issue Jun 4, 2021
(this change allow us to use menu bar in SettingsDialog)

+ fix for #6548 - Prusa Slicer 2.3.1 not activating non-modal settings window if settings window is minimized
YuSanka added a commit that referenced this issue Jun 8, 2021
(this change allow us to use menu bar in SettingsDialog)

+ fix for #6548 - Prusa Slicer 2.3.1 not activating non-modal settings window if settings window is minimized
YuSanka added a commit that referenced this issue Jun 14, 2021
(this change allow us to use menu bar in SettingsDialog)

+ fix for #6548 - Prusa Slicer 2.3.1 not activating non-modal settings window if settings window is minimized
YuSanka added a commit that referenced this issue Jun 16, 2021
(this change allow us to use menu bar in SettingsDialog)

+ fix for #6548 - Prusa Slicer 2.3.1 not activating non-modal settings window if settings window is minimized
YuSanka added a commit that referenced this issue Jun 18, 2021
(this change allow us to use menu bar in SettingsDialog)

+ fix for #6548 - Prusa Slicer 2.3.1 not activating non-modal settings window if settings window is minimized
YuSanka added a commit that referenced this issue Jun 18, 2021
* MSW specific: Dark Mode: First implementation

* Use menu instead of NoteBook

* Implemented MessageDialog
+ Fixed DarkMode for all dialogs and ColorPicker

* MSW DarkMode: Added missed updates for the switching between modes

* MSW DarkMode: Updated all existed context menus after switching of the mode
+ Added markers for the menu item witch is related to the selected tab

* Used wxFrame instead of wxDialog for SettingsDialog
(this change allow us to use menu bar in SettingsDialog)

+ fix for #6548 - Prusa Slicer 2.3.1 not activating non-modal settings window if settings window is minimized

* Implemented "Always use Dark mode colors" preference option

* Fixes for non_MSW build

* Next fixes for non-MSW builds

* Preferences: Fixed selection of the Settings Layout for non-MSW platforms
+ Updated DarkMode for colorpickers

* Windows DarkMode next fixes

* MSWDarkMode: Suppress to use system color to the PrusaSlicer
Select "Preferences -> Use Dark color mode (experimental)" to allow dark mode for the application

* Fixed MSW build

* MSWDarkMode: Upadteed color mode for ExtruderSequenceDialog and for dialogs related to the DoubleSlider

* Implemented Auto recreation of the PrusaSlicer when color mode is changed.

* Preferences: Added option "Set settings tabs as menu items (experimental)"
@lukasmatena
Copy link
Collaborator

I believe this is fixed in PrusaSlicer 2.4.0-beta1. Can we close this?

@clivius
Copy link
Author

clivius commented Nov 8, 2021

Awesome. Thank you!

@clivius clivius closed this as completed Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants