FvwmEvent monitor_enabled

[rasatpc]

• Fvwm3 version (run: fvwm3 --version)
  fvwm3 1.1.4 (1.1.3-21-ga15c008f)

Problem

To replace my current bash script, which runs specific FvwmButtons and pagers on the monitor when connected to the laptop, it was suggested to use "FvwmEvent monitor_enabled". Without going into details, this simple test config to run xterm when the monitor is connected does not work, nor does "monitor_disabled" (on laptop when disconnected).

DestroyModuleConfig FvwmEvent-MonitorTest: *
*FvwmEvent-MonitorTest: monitor_enabled "Exec xterm" # or "Exec exec xterm"

Module FvwmEvent FvwmEvent-MonitorTest

Current setting:

DesktopConfiguration per-monitor

aRandR:

#!/bin/sh
xrandr --output eDP-1 --mode 1920x1080 --pos 1920x0 --rotate normal --output HDMI-1 --primary --mode 1920x1080 --pos 0x0 --rotate normal

[ThomasAdam]

Hi @rasatpc

Thanks.

Could you put fvwm3 into verbose logging mode, and send me the logs, please?

If you don't know how to do that, the issue template here tells you...

[somiaj]

That test works fine here. When do you you enable your monitor. If it is enabled at start/before fvwm3 is running, fvwm won't catch the event. But as stated share your logs.

[rasatpc]

@somiaj When do you you enable your monitor.
Monitor is connected when MX Linus login screen appears. When disconnected, after Fvwm is loaded, the monitor cable is connected, and RandR is restarted, the FvwmEvent doesn't start.

@ThomasAdam, into verbose logging mode.

Here, verbose login (fvwm -v) on a fresh install Fvwm. RandR startup and FvwmEvent syntax are added at the end of the default fvwm config. Monitor started the fvwm login.

[1759742514.690563] FScreenInit: Using RandR 1.6
[1759742514.740810] scan_screens: Case 1: Add new monitors
[1759742514.740931] monitor_mark_new: Added new monitor: eDP-1 (0x55cad433c5c0)
[1759742514.741049] monitor_mark_new: Added new monitor: HDMI-1 (0x55cad433c730)
[1759742514.751886] main: Loading window states via (null)
[1759742515.284675] scan_screens: Case 2: processing 2 monitors
[1759742515.284816] monitor_mark_changed: HDMI-1: x: 1920, y: 0, w: 1920, h: 1080 comp: x: 0, y: 0, w: 1920, h: 1080
[1759742515.284832] scan_screens: Case 2.2: HDMI-1 changed
[1759742515.285025] monitor_mark_changed: eDP-1: x: 0, y: 0, w: 1920, h: 1080 comp: x: 1920, y: 0, w: 1920, h: 1080
[1759742515.285050] scan_screens: Case 2.2: eDP-1 changed
[1759742515.395024] monitor_emit_broadcast: HDMI-1: emit: 256
[1759742515.395048] monitor_emit_broadcast: HDMI-1: emit monitor changed
[1759742515.395203] _execute_command_line: No such command 'RandRFunc'
[1759742515.395215] monitor_emit_broadcast: HDMI-1: emit monitor primary change
[1759742515.395323] _execute_command_line: No such command 'RandRFunc'
[1759742515.395334] monitor_emit_broadcast: eDP-1: emit: 256
[1759742515.395340] monitor_emit_broadcast: eDP-1: emit monitor changed
[1759742515.395447] _execute_command_line: No such command 'RandRFunc'
[1759742515.395597] scan_screens: Case 2: processing 2 monitors
[1759742515.398755] monitor_emit_broadcast: HDMI-1: emit monitor primary change
[1759742515.398890] _execute_command_line: No such command 'RandRFunc'
[1759742515.398903] dispatch_event: Ignoring duplicate event 3380
[1759742515.398976] scan_screens: Case 2: processing 2 monitors
[1759742515.402079] monitor_emit_broadcast: HDMI-1: emit monitor primary change
[1759742515.402201] _execute_command_line: No such command 'RandRFunc'
[1759742515.402212] dispatch_event: Ignoring duplicate event 3380
[1759742519.602251] is_pan_frame: Window is PanFrame right
[1759742520.110341] is_pan_frame: Window is PanFrame right

[rasatpc]

I did a test with RandRFunc, and it works fine.

DestroyFunc RandRFunc
AddToFunc   RandRFunc
+ I Exec exec xmessage "A screen changed"

FvwmEvent monitor_enabled and monitor_disabled not working.

[rasatpc]

I did further tests with RandRFunc and noticed that xmessage and FvwmButtons are duplicating on dual monitors. Fresh install (default config), it duplicates six times when logging in with the plugin monitor.
Screenshot:
https://rasatpc.net/screenshot/fvwm3/RandRfunc.png

[ThomasAdam]

It will duplicate due to how the events are received.

[rasatpc]

These syntax additions were added at the end of the default config.

Exec exec sh $[FVWM_USERDIR]/aRandrStart.sh
DesktopConfiguration per-monitor

DestroyFunc RandRFunc
AddToFunc   RandRFunc
+ I Exec exec xmessage "A screen changed"

[ThomasAdam]

I suspect what I will have to do here is add an extra command for: RandREvents or something, which will allow the user to specify which RandR events should be subscribed to -- and then add extra variables: $[monitor.event.X] where X is something like: new or changed such that they can be used in the Test command.