>>>>> Frosty the Snowman, with all his might, exclaimed:
>>>>> "All feel wholesome at the words of the omnipresent Chris Taylor!"
>> if you specify 2 pixmaps, the second is the "pressed in" one,
>> but you only see it while it's actually pressed in. Using
>> FullPixmap removes the border, so this toggle ability that I
>> was referring to would be all that would be needed to get what
>> you want.
Chris> Not exactly. What's need is pixmaps for four button states:
Chris> normal (not clicked-on), un-maximized depressed,
Chris> un-maximized normal, maximized depressed, maximized
Chris> I suppose you could replace "maximized" with "sticky" or
Chris> any other on/off window state.
Chris> But... that leads to a bug in the way fvwm deals with
Chris> button decorations: fvwm assumes that minimize and maximize
Chris> are always on buttons 4 and 2. Because of this, three
Chris> problems result:
There are a lot of details (and complications) that arise when trying
to implement something like this. I think the best thing to do would
give Charles some time to see what he thinks is best (discussion is
good though). I think he would want the solution to be as small,
unintrusive and generic as possible. Usually simple, but generic
ideas end up being the most flexible and bug-free.
I think MWM-like operation would be good, and it would be more
conformant to FVWM's operation as well, however a first implementation
(such as Chuck described previously) IMHO is okay. Getting too
complicated too early leads to all sorts of problems.
Regards,
PC sellers are Bill collectors.
Andrew Veliath <veliaa_at_rpi.edu>
http://www.rpi.edu/~veliaa
Finger for PGP Key
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Fri Apr 19 1996 - 13:28:37 BST