Hi list!
I've noticed this some time ago, but never had the time to look into
it. Now that I did, I couldn't find the reason for FvwmForm's
behaviour.
What I'm seeing is the following:
I'm using FvwmForm to query the user (me) if some action should not be
taken if a menu entry is merely hit by accident - such as 'quit'.
Now, when FvwmForm loads, I don't see any text. I can somewhat see
where buttons would be displayed (even though they are not fully drawn
either), but the text is entirely missing.
If I hit any key (pressing ctrl is enough), the window gets properly
painted.
To give you an idea what I'm talking about, I made screenshots:
<http://ft.bewatermyfriend.org/tmp/forms_initial.png>
<http://ft.bewatermyfriend.org/tmp/forms_drawn.png>
'forms_initial.png' is the window right after loading.
'forms_drawn.png' is the very same window right after I pressed ctrl.
This form has the following configuration:
[snip]
DestroyModuleConfig DialogStdAppsVerify: *
*DialogStdAppsVerify: GrabServer
*DialogStdAppsVerify: WarpPointer
*DialogStdAppsVerify: Font terminus-12
*DialogStdAppsVerify: ButtonFont terminus-12
*DialogStdAppsVerify: InputFont terminus-12
*DialogStdAppsVerify: TimeoutFont terminus-12
*DialogStdAppsVerify: Line center
*DialogStdAppsVerify: Text "So, do you really want to launch these
programs?"
*DialogStdAppsVerify: Line expand
*DialogStdAppsVerify: Button quit "yeah, buddy. Get going!" ^M
*DialogStdAppsVerify: Command Exec exec $[FVWM_USERDIR]/load_std.pl
*DialogStdAppsVerify: Button quit "nope, sorry to bother you" ^[
*DialogStdAppsVerify: Command Nop
[snap]
The menu entry that loads for form is this:
Module FvwmForm DialogStdAppsVerify
And finally, the style used for FvwmForm is:
Style "*FvwmForm" !Handles, !Title, Colorset 8
With Colorset 8 being:
Colorset 8 bg gray40
All of this is happening using:
[snip]
% fvwm --version
fvwm 2.5.26 compiled on May 29 2008 at 21:55:23
with support for: ReadLine, RPlay, Stroke, XPM, PNG, SVG, Shape, XShm,
SM, Bidi text, Xinerama, XRender, XCursor, XFT, NLS
[snap]
...installed via debian's fvwm package version '1:2.5.26-1'.
Any clues are appreciated, as I'm completely out of ideas.
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
