On 25 Aug 2002 16:18:42 -0500, Len Philpot wrote:
>
> Agreed - Except that it's a bit difficult to accurately document
> something in terms someone else can understand when the "documetor"
> doesn't understand it. For example, I've seen the following examples for
> FvwmTaskBar :
>
> From the fvwm webpage :
>
> Style "FvwmTaskBar" NoTitle,BorderWidth 4, HandleWidth 4,Sticky,
> StaysOnTop,WindowSkipList,CirculateSkip
> #------------------------------------ taskbar
> *FvwmTaskBar: Back #c3c3c3
> *FvwmTaskBar: Fore black
> *FvwmTaskBar: TipsBack bisque
> *FvwmTaskBar: TipsFore black
> *FvwmTaskBar: Geometry +0-0
> *FvwmTaskBar: Font -adobe-helvetica-medium-r-*-*-14-*-*-*-*-*-*-*
> *FvwmTaskBar: SelFont -adobe-helvetica-bold-r-*-*-14-*-*-*-*-*-*-*
> *FvwmTaskBar: StatusFont fixed
>
>
> From the FvwmTaskBar 2.6 man page on my system :
>
> Style "FvwmTaskBar" NoTitle,BorderWidth 4, HandleWidth 4,Sticky,
> StaysOnTop,WindowSkipList,CirculateSkip
>
> #------------------------------------ taskbar
> *FvwmTaskBarBack #c3c3c3
> *FvwmTaskBarFore black
> *FvwmTaskBarTipsBack bisque
> *FvwmTaskBarTipsFore black
> *FvwmTaskBarGeometry +0-1
> *FvwmTaskBarFont -adobe-helvetica-medium-r-*-*-14-*-*-*-*-*-*-*
> *FvwmTaskBarSelFont -adobe-helvetica-bold-r-*-*-14-*-*-*-*-*-*-*
> *FvwmTaskBarStatusFont fixed
There is no such version 2.6. The man pages on the web are for fvwm 2.4.x.
You seem to use 2.2.x which is very old. Of course, you should contact
the man pages matching your version. In 2.4.x both syntaxes should work,
but the one in the man page is preferable. I think +0-0 is a more correct
geometry than +0-1, but 2.2.x may have some bugs about this.
> I am in no way singling out FvwmTaskBar - I just happened to be working
> with it lately. The second example works, the first doesn't (as far as I
> can tell). This is typical of what I'm apparently misunderstanding. It
> appears that fvwm plays very loose and fast with the config file in
> terms of syntax? Or am I just missing something? It appears that there's
> always more than one way to do anything, which I guess has its merits,
> but is almost always initially more confusing than a tightly controlled
> syntax. For example, do all of the parts of a function or menu
> definition need to be in one place (immediately under the AddToFunc or
> AddToMenu), or can they be spread around. If the latter, what's the
> advantage? It seems like you'd want them all grouped together anyway,
> just organizationally. I tend to look on config files in general much
> like source code - Make them modular, organized and as easy to read as
> possible.
>
> I've seen a couple of replies to my original post that I've yet to read
> carefully and digest, so I'll not waste bandwidth here asking questions
> they may answer.
>
>
> However, I do have one concerning FvwmTaskBar (no, make that two) :
>
> 1. With BorderWidth and HandleWidth set to 1 or 0, the taskbar doesn't
> occupy the full width of the screen. Is there a way to force this?
Yes, use the latest stable or unstable versions.
> 2. When I configure a Popup StartMenu, is there a way to accurately
> control where it appears on screen, in regard to the Start button? If I
> understood MenuStyle a bit better, maybe the answer is there
> (PopupOffset, or whatever it's called)...?
Yes, you may do this accurately in 2.5.1+, scan NEWS file.
In 2.4.x, you may do this too using Rectangle or Mouse hint (there are
examples in fvwm-themes), but not as accurately as in 2.5.x.
> OK - One more (general) question :
>
> Is there a way to globally turn off mouse pointer warping so that it
> never warps to a menu, window, whatever? That's one behavior I _really_
> would like to get rid of, particularly on popup menus.
Globally, no.
If you bind a menu to a key, it altomatically selects the first selectable
menu item (and thus warps the pointer), but after working with such menu
the original pointer position is restored. It is good when you work with
keyboard only. If you bind a menu to a mouse it does not warp.
For example, in the following if you press Ctrl-Shift-F10 it warps, but
Ctrl-Shift-Mouse1 does not:
Key F10 A CS Menu MenuFvwmRoot Rectangle 1x1+10+10 0 0
Mouse 1 R CS Menu MenuFvwmRoot Rectangle 1x1+10+10 0 0
What exactly annoys you about menus and windows? Provide configurations.
Regards,
Mikhael.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sun Aug 25 2002 - 17:21:44 BST