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
Hi, I've been using this bar for a while now, and it's helped me make my windows experience very enjoyable — I never liked the windows desktop, but this paired with a few other tweaks have made me feel more at home on Windows as a deeply-rooted Linux user.
Today was one of those days that I felt like tinkering with my desktop a bit more, and decided that I would like this bar to appear on my second monitor, too. After a little bit of messing around, I found that I can just make a second instance by cloning the skin folder.
I like my bar to always be visible, so I have it reserve space, and have it set to be topmost to prevent overlap. For the most part, this works fine on my primary monitor.
Screenshots
Example of multiple tiled windows. The top right one is tiled neatly against the top bar.
Example of a single maximized window. The Top Bar correctly reserves space to remain visible at all times.
However, on my secondary display, it is failing to reserve the space. It also likes to extend off-screen until I refresh the skin.
Screenshots
The Discord application is clearly under the bar.
There is supposed to be a CPU and Clock visible here, but they get cut off.
The last two screenshots were taken from a secondary screen, which does identify itself to Windows as a seperate screen that extends from the primary screen; as you can see from this screenshot.
Screenshots
Windows identifies the second screen as a second screen, and does not see it and the primary screen as a single unified screen.
Unsure of wether this information is of any value in this issue, but I figured I include it just in case.
# Replicating the issue
Something odd I noticed is that even when telling the second instance of the bar to exist on display 2, it remains on display 1, requiring me to adjust its coordinates on the screen to displace it to the intended location.
Here are the settings I've configured for it on Rainmeter itself
Screenshots
Selected Monitor №2, and adjusted the coordinates to actually be on the secondary monitor.
Yet another case of "I don't know if this matters, but I'm including it anyway."
And finally, the settings for the bar instance itself:
Screenshots
Reserve Space is enabled.
Reserved space amount matches bar height. There should be no errors in this configuration.
I hope there is a solution to this issue. Its not that big of a deal, but it would certainly make my experience a LOT more enjoable.
It should be noted however that I have slightly customized my instances of the bar to use a segmented display font on the clock, a small tweak purely out of personal preference. However, I do not believe that is of much issue as the tweak specifically targets the date/time display by setting a font family value. As well as adding a simple colon-seperator blinker, which I only added one module for. If necessary, I can provide my tweaked version of the bar for comparison and troubleshooting though.
The text was updated successfully, but these errors were encountered:
Hi, I've been using this bar for a while now, and it's helped me make my windows experience very enjoyable — I never liked the windows desktop, but this paired with a few other tweaks have made me feel more at home on Windows as a deeply-rooted Linux user.
Today was one of those days that I felt like tinkering with my desktop a bit more, and decided that I would like this bar to appear on my second monitor, too. After a little bit of messing around, I found that I can just make a second instance by cloning the skin folder.
I like my bar to always be visible, so I have it reserve space, and have it set to be topmost to prevent overlap. For the most part, this works fine on my primary monitor.
Screenshots
Example of multiple tiled windows. The top right one is tiled neatly against the top bar.
Example of a single maximized window. The Top Bar correctly reserves space to remain visible at all times.
However, on my secondary display, it is failing to reserve the space. It also likes to extend off-screen until I refresh the skin.
Screenshots
The Discord application is clearly under the bar.
There is supposed to be a CPU and Clock visible here, but they get cut off.
The last two screenshots were taken from a secondary screen, which does identify itself to Windows as a seperate screen that extends from the primary screen; as you can see from this screenshot.
Screenshots
Windows identifies the second screen as a second screen, and does not see it and the primary screen as a single unified screen.
Unsure of wether this information is of any value in this issue, but I figured I include it just in case.
# Replicating the issue
Something odd I noticed is that even when telling the second instance of the bar to exist on display 2, it remains on display 1, requiring me to adjust its coordinates on the screen to displace it to the intended location.
Here are the settings I've configured for it on Rainmeter itself
Screenshots
Selected Monitor №2, and adjusted the coordinates to actually be on the secondary monitor.
Yet another case of "I don't know if this matters, but I'm including it anyway."
And finally, the settings for the bar instance itself:
Screenshots
Reserve Space is enabled.
Reserved space amount matches bar height. There should be no errors in this configuration.
I hope there is a solution to this issue. Its not that big of a deal, but it would certainly make my experience a LOT more enjoable.
It should be noted however that I have slightly customized my instances of the bar to use a segmented display font on the clock, a small tweak purely out of personal preference. However, I do not believe that is of much issue as the tweak specifically targets the date/time display by setting a font family value. As well as adding a simple colon-seperator blinker, which I only added one module for. If necessary, I can provide my tweaked version of the bar for comparison and troubleshooting though.
The text was updated successfully, but these errors were encountered: