FvwmEvent monitor_* events are not processing their functions correctly.

[NsCDE]

By using FvwmEvent to Echo some string into fvwm log, I get "-1" instead of that string from the function. As a base FvwmEvent configuration, NsCDE fvwm3_support branch is used. On this config:

https://github.com/NsCDE/NsCDE/blob/fvwm3_support/NsCDE/config/NsCDE-Event.conf

new config is appended for testing:

DestroyFunc f_EventTestME
AddToFunc f_EventTestME
+ I Echo EVENT DEBUG ME ============================> $*

DestroyFunc f_EventTestMD
AddToFunc f_EventTestMD
+ I Echo EVENT DEBUG MD ============================> $*

DestroyFunc f_EventTestMC
AddToFunc f_EventTestMC
+ I Echo EVENT DEBUG MC ============================> $*

DestroyFunc f_EventTestMF
AddToFunc f_EventTestMF
+ I Echo EVENT DEBUG MF ============================> $*

*MainLoop: monitor_enabled f_EventTestME __me__
*MainLoop: monitor_disabled f_EventTestMD __md__
*MainLoop: monitor_changed f_EventTestMC __mc__
*MainLoop: monitor_focus f_EventTestMF __mf__

This is the result:

[1603230503.629785] CMD_Echo: EVENT DEBUG MD ============================> -1 [1603230544.602999] CMD_Echo: EVENT DEBUG ME ============================> -1 [1603230250.458667] CMD_Echo: EVENT DEBUG MF ============================> -1

Additionally, it looks like monitor_focus is more often not triggered when it has to be then triggered. Moving pointer between the screens does not produce the output in log, while moving it to FvwmButtons based FrontPanel which has different Style options from other windows succeeds almost every time to produce output in log.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.84. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.