Skip to content
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

FvwmEvent monitor_* events are not processing their functions correctly. #266

Open
NsCDE opened this issue Oct 20, 2020 · 1 comment
Open
Assignees
Labels
has:config Issue has config attached type:bug Something's broken!

Comments

@NsCDE
Copy link
Contributor

NsCDE commented Oct 20, 2020

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
Copy link

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

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

@issue-label-bot issue-label-bot bot added the type:bug Something's broken! label Oct 20, 2020
@ThomasAdam ThomasAdam added this to the 1.0.2 milestone Dec 7, 2020
@ThomasAdam ThomasAdam self-assigned this Dec 7, 2020
@ThomasAdam ThomasAdam removed this from the 1.0.2 milestone Dec 14, 2020
@ThomasAdam ThomasAdam added this to the 1.0.3 milestone Dec 20, 2020
@ThomasAdam ThomasAdam added has:config Issue has config attached relates:fvwm3 and removed relates:fvwm3 labels Dec 20, 2020
@ThomasAdam ThomasAdam removed this from the 1.0.3 milestone Apr 17, 2021
@ThomasAdam ThomasAdam moved this to To do in FVWM3 Sep 18, 2022
@ThomasAdam ThomasAdam added this to FVWM3 Sep 18, 2022
@ThomasAdam ThomasAdam added this to the 1.0.9 milestone Sep 5, 2023
@ThomasAdam ThomasAdam removed this from the 1.0.9 milestone Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has:config Issue has config attached type:bug Something's broken!
Projects
Status: To do
Development

No branches or pull requests

2 participants