Just wanted to provide a quick update and report a few bugs that have I been observing.
I am running the latest version from the cvs. Some of you may remember, a few months ago I had a big issue with maple and its behavior of flooding fvwm with thousands of events: https://www.mail-archive.com/fvwm-workers@fvwm.org/msg03650.html The fix by Dominik seems to work well. I've had fvwm crush twice since then... but I could not reproduce the issues and it wasn't when a program was starting. Here are a few non-critical bugs that I see often: 1) Some windows sometimes start "outside" of the desktop, meaning when they start, I know they are running but they are not visible on any of my pages. I use a 9 page, single desktop set up via: DeskTopSize 3x3 This happens quite a bit with skype, but also other apps as well (for example spotify). I think it's most likely to happen if the app was not closed properly (after a power outage for example). I get them to become visible by running: Next (Spotify) MoveToPage 0 0 It would be good if the apps were forced to only be first drawn somewhere where they can be seen by the user (ideally, by default, on the desktop the user was on, when invoking the app). 2) I use EdgeThickness 1 to scroll between pages with a mouse. When I scroll from page to page, the Balloons (i.e hints) on the FvwmPager often don't disappear. The chain of events is the following: - Say i'm on a particular desktop page and the mouse in on top of the pager. The pager balloon/hint will pop up. - The pager is right at the edge of the page (at the bottom). So say now I move my mouse downwards, and switch to the page below. - The page switches, and the mouse is no longer on top of the pager, but now somewhere near the top... - ... but the pager balloon/hint is still showing as if the mouse was still hovering on top of the FvwmPager The only way to get rid of it, is to move my mouse over the pager, then move the mouse off the pager, but not while switching the page at the same time. 3) This is very similar to previous bug, but with FvwmButtons which live at the top of every the page. I have them setup where the buttons of FvwmButtons are highlighted when the mouse hovers over them. Here again when a given button is highlighted (because the mouse is on top of it), and I then switch the page (move mouse up to the page at the top), sometimes the button stays highlighted even though the mouse is not on top of it anymore. Issues (2) and (3) seem very similar - basically sometimes fvwm is not aware that the mouse has moved "away" from FvwmPager of FvwmButtons, in particular when pages are switched. I should stress that I do use FvwmEvents when switching pages, like so: *Events: new_page ChangePageEventFunc DestroyFunc ChangePageEventFunc AddToFunc ChangePageEventFunc + I CloseAllConsoles + I DeSchedule $[schedule.last] + I Next (FvwmPager) RaiseToTop + I All (FvwmPager) Schedule 700 Lower thanks!
