stein@WRC.XEROX.COM (Adam Stein) (02/21/91)
I haven't seen this bug mentioned anywhere before so I'm mentioning it now.
Any window that has the WM_SAVE_YOURSELF protocol will set WM_COMMAND
if they should ever receive a WM_SAVE_YOURSELF message. It turns out that
if an xview program is executed with the -Wl option (window label) with a
string of more than 23 characters, then when that program receives a
WM_SAVE_YOURSELF it screws up WM_COMMAND. The only 3 programs I have
observed this with are xrolo and OpenWindow's cm and mailtool. I start all
3 with whatever label they had when I saved their state (which is longer than
23 characters) and when they save their state in WM_COMMAND it's always
screwed up (I determined that 23 was the most the label string could have
by changing the size of the string I used for the -Wl option). For example, I
would start xrolo with:
xrolo -Wp 29 278 -Ws 592 309 -WP 1085 241 -Wl "Rolo - .work (Card 1 of 1)"
If xrolo was sent a WM_SAVE_YOURSELF, WM_COMMAND would look like:
xrolo -Wp 29 278 -Ws 592 309 -WP 1085 241 1)" -Wl "Rolo - .work (Card 1 of 1)"
Xview always screws up by putting the last characters from the label string at
the end of the X and Y icon locations (-WP option). In the above example,
'... -WP 1085 241 1)" -Wl ...' is screwed up (the '1)"' coming from the end of
the -Wl string). Has anybody else noticed this?
Adam Stein
--
Adam Stein @ Xerox Corporation Email: stein.wbst129@xerox.com
stein@arisia.xerox.com
Disclaimer: Any/All views expressed ...!uunet!xerox.com!stein.wbst129
here have been proved to be my own. Hopefully one of the above will work.