-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Workspace number at changes -- system freeze #997
Comments
Hi @rasatpc Yes, it's a bug. I think I need to check the DesktopSize broadcast module issue as this implicitly sends a M_NEW_PAGE packet each time. That being said, the way you've written this panel is written to spawn itself on a new_page event each time seems weird to me. I would instead use a single sticky FvwmButtons instance, and use SendToModule to change the button's text. |
When updating modules about changes to monitors, etc., only send the DesktopSize command once, as this is proliferated for every module for all pages, which is redundant. Fixes #997
When updating modules about changes to monitors, etc., only send the DesktopSize command once, as this is proliferated for every module for all pages, which is redundant. Fixes #997
Please can you try compiling fvwm3 on the |
Slightly better with milder freeze.
|
So it does help? Good. Whatever you're referring to re UseSkipList, has nothing to do with this issue. |
Slight help, but still freezes, Ok, |
I don't have any freezes here. Can you see if there's other factors here which could be contributing to this? |
Earlier I test with all Kise configs. RightPanel's FvwmPager mini-windows are shaking, stops and system freeze. Did you make any new changes in |
When a module requests information about what it needs to know, it does so to fvwm by asking "Send_ConfigInfo". However, if this happens, and fvwm is already sending information to all modules (such as via a DesktopSize command), then an infinite loop can take place. Fixes #997
No, but I have just pushed another fix on that branch -- please Note also that your config example is still going to spawn a new FvwmButtons each time there's a new_page event. You should rewrite it per my earlier suggestion -- until you do, you will notice flickering as fvwm is trying to deal with that. |
Thank you, the Page Indicator works fine.
I don't understand those technical words. Will ask tomorrow. It is late here in Helsinki.... 01:35. Good night. |
When updating modules about changes to monitors, etc., only send the DesktopSize command once, as this is proliferated for every module for all pages, which is redundant. Fixes #997
When a module requests information about what it needs to know, it does so to fvwm by asking "Send_ConfigInfo". However, if this happens, and fvwm is already sending information to all modules (such as via a DesktopSize command), then an infinite loop can take place. Fixes #997
fvwm3 --version
)fvwm3 1.1.0 (released)
Expected Behaviour
This config has worked well until fvwm3 1.1.0 release.
https://fvwmforums.org/t/any-idea-to-display-the-workspace-number-at-changes/1822/6
It was copied and modified to a PageIndicator script.
https://github.com/rasatpc/Fvwm-KISe/blob/main/core/1Functions/PageIndicator/deskPgNo.sys
Fvwm3 1.1.0 makes FvwmPager flicker and freezes the system for a few seconds. Any action freezes the whole system.
I have not been able to pinpoint the issue, but it seems to do with
Module FvwmEvent
Is it a bug or a config error?
The text was updated successfully, but these errors were encountered: