-
Notifications
You must be signed in to change notification settings - Fork 6
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
Can't Load profile if process already running #4
Comments
If you manually load a profile, the existing running process will detect a screen change and change the screen according to your profile afterwards, overriding the manual load. Is this what you wanted to happen? |
@rliou92 that is the thing, it happened a couple of times the running process did not detect the setup, I had to trigger it manually. My solution was to kill it and start it again, but Or maybe add a new option to reload the whole thing for such cases, for instance
What do you think? |
Yes, I like both ideas! Though the root cause of the problem is that the running process failed to detect a change in setup. Are you able to reproduce such a scenario? |
towards the root cause, I think it might be my hardware, I am currently using autorandr (don't remember why I switched), and I have some issues, I am going to remove it to give umonitor a try again. I'll come back wen I see issues. |
Ok. Monitor setup detection is pretty tricky. |
It is, that is why I am suggesting some workarounds in case sometimes it just doesn't work :) |
I implemented this if you still need it. Not sure how the program responds in practical situations, but the functionality is there. |
Because of this:
python-umonitor/umonitor/umonitor.py
Line 119 in 6175f3f
Can't load a profile when the process is already running, which is kind of annoying.
I had to delete my "laptop" profile (no external screens) because the thing kept turning off screens when I disconnected the HDMI cable, and I could not load it manually while I was debugging.
Is there a reason for this?
The text was updated successfully, but these errors were encountered: