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
I am using nwg-shell as my daily driver in work and home. Sometimes I am working on my laptop with lid closed and two external screens attached, and sometimes I am working with lid opened and no external screen attached. The issue with nwg-panel is that I would like to have nwg-panel on one screen, not all, and my lid screen and the external screens have different names. Every time when I switching to external screens and from external screens to the lid, the nwg-panel is not visible and I have to reconfigure it to display on another screen. Is there any way to have nwg-panel always on the "primary" screen?
The text was updated successfully, but these errors were encountered:
I think it will be userful to add option to multi-select screen names on that nwg-panel should appear, it should also do the job. I think it is common to have external screens in the office, and working with lid only when have to work outside so, I think it should be userful to implement multi-selection of screen names.
It's absolutely doable, but must wait some time. Until nwg-dock-hyprland is ready. Sorry, but switching from golang to python and back again gives me a headache.
Hello
I am using nwg-shell as my daily driver in work and home. Sometimes I am working on my laptop with lid closed and two external screens attached, and sometimes I am working with lid opened and no external screen attached. The issue with nwg-panel is that I would like to have nwg-panel on one screen, not all, and my lid screen and the external screens have different names. Every time when I switching to external screens and from external screens to the lid, the nwg-panel is not visible and I have to reconfigure it to display on another screen. Is there any way to have nwg-panel always on the "primary" screen?
The text was updated successfully, but these errors were encountered: