>
> Scott> ***Control over the icon pixmap vs. the 'icon text' the floats under
> Scott> the icon pixmap (or is the sole piece of the icon when there is no
> Scott> pixmap):
> Scott> I'm really picky on space, and for programs like cm the icon
> Scott> pixmap is sufficient and I don't want the icon text to even
> Scott> appear. For most other things, I don't want there to be any icon
> Scott> pixmap, just the icon text (trying to give a small 'invisible' pixmap,
> Scott> just results in the icon text being as small in width as the pixmap).
>
> Check out the man page where it describes the 'Style' command,
> specifically the 'NoIconTitle' and the 'Icon/NoIcon' parts.
>
Cool, that covers half of what I want, but I think I want a new set of
styles 'IconPixmap/NoIconPixmap' so that I can choose to just show the
Icon Title w/o any attached pixmap:
Style "*" IconTitle, NoIconPixmap
>
> Scott> ***Ability to use a double-click when the second click is held down:
> Scott> I currently use the following setup, which allows me to click
> Scott> and release to get a menu, as well as click and hold to get a menu,
> Scott> but I can't double-click and hold to get the other menu.
>
> Scott> Popup "Mouse1Popups"
> Scott> Popup "Click" FVWM_control
> Scott> Popup "Motion" FVWM_control
> Scott> Popup "DoubleClick" screen_locks
> Scott> EndFunction
>
> I think that something like this will work in 2.xx, but I've never
> tried it... Nope - a quick test shows that it doesn't work there
> either. I'll take a look and see if this is a bug or working as
> designed and how easily fixed/implemented.
>
You got my confidence up enough to look at my 1.24r code; and I got it
to work they way I want with this patch:
__________________________________cut-here
1422,1427c1422,1427
< if((HaveDoubleClick) && (type == ONE_AND_A_HALF_CLICKS) &&
< (IsClick(x,y,ButtonReleaseMask, &d)))
< {
< type = DOUBLE_CLICK;
< ev = &d;
< }
---
> if((HaveDoubleClick) && (type == ONE_AND_A_HALF_CLICKS))
> {
> IsClick(x,y,ButtonReleaseMask, &d);
> type = DOUBLE_CLICK;
> ev = &d;
> }
__________________________________cut-here
Without the IsClick(...) line, it is faster than the release of the
second-click, a sleep could be used, but I think that using IsClick
might also do some nice handling of quick movement after a
double-click (with a hold on the second click)----
I'm not sure if it was intentionally coded the other way before, but
it appeared to drop the case where I double click with a hold on the
second click.....
> Hope I've been of assistance.
Very much so, I recommend you get a raise!!!
Another satisfied FVWM customer,
shr
PS If your curious, I'm not jumping to 2.0 beta now since you keep
saying that the official 2.0 will be put out soon (not that I'm afraid
of beta's, I just don't want to make two updates in two weeks). Just
don't announce that you've decided it will be FVWM '96. ;-)
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Sep 26 1995 - 18:58:06 BST