-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Proposal: FvwmEvent new events in FVWM3 #26
Comments
This adds the work necessary to make FvwmEvent listen for RandR events. Three events are supported: * monitor_enabled -- when a monitor is "plugged" in, and active; * monitor_disabled -- when a monitor is "unplugged" and deactivated; * monitor_changed -- when an enabled monitor changes resolution/rotation An "emit" flag is used to track events, separate from the on-going state of RandR itself. Fixes #26
Hi, So please see the
Due to how RandR works, the finer-grained distinction between enable/add and disable/remove aren't reliable at all. But hopefully the above three should help cover most basis that people are interested in. I've also added an example to |
This adds the work necessary to make FvwmEvent listen for RandR events. Three events are supported: * monitor_enabled -- when a monitor is "plugged" in, and active; * monitor_disabled -- when a monitor is "unplugged" and deactivated; * monitor_changed -- when an enabled monitor changes resolution/rotation An "emit" flag is used to track events, separate from the on-going state of RandR itself. Fixes #26
This adds the work necessary to make FvwmEvent listen for RandR events. Three events are supported: * monitor_enabled -- when a monitor is "plugged" in, and active; * monitor_disabled -- when a monitor is "unplugged" and deactivated; * monitor_changed -- when an enabled monitor changes resolution/rotation An "emit" flag is used to track events, separate from the on-going state of RandR itself. Fixes #26
This adds the work necessary to make FvwmEvent listen for RandR events. Three events are supported: * monitor_enabled -- when a monitor is "plugged" in, and active; * monitor_disabled -- when a monitor is "unplugged" and deactivated; * monitor_changed -- when an enabled monitor changes resolution/rotation An "emit" flag is used to track events, separate from the on-going state of RandR itself. Fixes #26
Hi, This has been working well enough for me, and hence I'll merge the pull-request associated with this issue, to master. Feel free to open a new issue if there's problems. Thomas |
This adds the work necessary to make FvwmEvent listen for RandR events. Three events are supported: * monitor_enabled -- when a monitor is "plugged" in, and active; * monitor_disabled -- when a monitor is "unplugged" and deactivated; * monitor_changed -- when an enabled monitor changes resolution/rotation An "emit" flag is used to track events, separate from the on-going state of RandR itself. Fixes #26
This adds the work necessary to make FvwmEvent listen for RandR events. Three events are supported: * monitor_enabled -- when a monitor is "plugged" in, and active; * monitor_disabled -- when a monitor is "unplugged" and deactivated; * monitor_changed -- when an enabled monitor changes resolution/rotation An "emit" flag is used to track events, separate from the on-going state of RandR itself. Fixes fvwmorg#26
As FvwmEvent handles new_page and new_desk window manager event, it will be nice to make RandR screen events acessible through it.
According to debug output, FVWM3 sees when monitor is added or removed, enabled or disabled, or when pointer changes active screen.
Proposal for exposing events is:
add_monitor
remove_monitor
enable_monitor
disable_monitor
change_screen
That way, user can configure custom actions and functions for this situations if wanted/needed.
The text was updated successfully, but these errors were encountered: