On May 15, 2010, at 2:41 PM, Thomas Adam wrote:
[Cc'ing fvwm-workers@ so I don't lose track of this]
Sorry it's taken me a few days to get back to you.
On Wed, May 12, 2010 at 02:05:33PM -0700, Omar Zakaria wrote:
Well, good news, then. I've finished the app. What's a good way to get it
to you?
I am still unable to run this application via VisualWorks, but it doesn't
matter, as just trying to launch VisualWorks itself (which maps windows)
seems to exhibit the same problem.
Heh. I hope you don't misunderstand me when I say I'm glad to hear it.
Tricky little devil of a bug.
But beyond that, I can't see why this thing is failing in the way it is.
I've done some pretty in-depth analysis of the event-handling code in FVWM
-- the events it receives are all handled properly. Out of interest, does
the following (albeit drastic -- it's only for testing) help with your
problem?
Style * Unmanaged
Yes, surprisingly, that seems to work. I'm not entirely certain what that
means, though. I'm still learning about FVWM.
With that line set, we don't see any problems at all launching the
VisualWorks app and all windows draw themselves correctly the first
time through.
I am really hoping it will -- because then FVWM bails even bother trying to
reparent the window into its frame.
I am going to look into this some more. It's really interesting.
Thanks again for looking at this. I really appreciate it. Let me know if
I can help in any way.
--
Omar Zakaria
Agilent Technologies
W: 707-577-4214
