Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

Single Monitor Usage #11

Open
bergsm opened this issue Jan 3, 2020 · 2 comments
Open

Single Monitor Usage #11

bergsm opened this issue Jan 3, 2020 · 2 comments

Comments

@bergsm
Copy link

bergsm commented Jan 3, 2020

Hey there!
First off, I love this fork! Thanks so much for making it!

The lock works great when using multi monitors, however, when I disconnect my laptop from my external monitor and use it, the lock screen image appears to be too large.

I'm wondering if it's using the external monitors image when disconnected maybe?

Any insight to using the multilock when disconnected from an external monitor would be great! :)

@jeffmhubbard
Copy link
Owner

Any time you make changes to your display setup, you will have to update multilockscreen.

i3lock only accepts one background image, so to make multiple displays work we have to piece together several images into one large image. When you disconnect the external, the cached images are larger than your current resolution. You are probably seeing the portion of the image where your external should be.

When I add or remove displays with xrandr, I usually need to restart i3 as well. I use this in my i3 config: exec_always --no-startup-id multilockscreen -u $HOME/Wallpapers/Shuffle Now every time I restart i3 it updates multilockscreen too.

@bergsm
Copy link
Author

bergsm commented Jan 4, 2020

I suppose that would be one workaround. I also understand now that it may be difficult to account for user workflows when connecting/disconnecting monitors as there currently is no standard procedure. I, for example, do not restart i3 when changing configurations.

I did notice however that the cache also stores the lock screen images for each monitor. Using this, I was able to hack a solution together that detects the number of displays in use and uses the cached lock image for my laptop screen if the number of displays is 1. That commit is here: bergsm@7ff7bb0.

Admittedly this solution is a hack for my personal use, but perhaps that concept could be built upon to create a more general solution?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants