🚀 go-pugleaf

In article <da+3fwa@rpi.edu>, rogerj@aix.rpi.edu (Diversion (Jeff Rogers)) writes:
|> bane@vtx.ma.man.ac.uk (Michael!) writes:
|> 

|> >2) what do you mean by "change rooms"? 
|> >   IF
|> >     changing workspaces under ctwm
|> >        then I have no problems and the same root window image is everywhere
|> 
|> My comment on this comes from when I saw a ctwm user using xfractint with
|> -onroot. The fractal would display correctly, but when changing workspaces,
|> ctwm would repaint the screen with it's (the current workspace's) designated
|> background (the diamonds, etc). The fractal would continue generating (if it
|> still was) where it last was on the screen, but everything that was there
|> before was painted over by the ctwm background. If there's a no-background
|> option (there probably is, I re-restate, I don't use it and don't know what
|> options are available), then that probably solves the problem. My informash
|> comes from looking over people's shoulders.


ha-ha I see what you mean; I had not used the option for different root window
images before and had the same for all w/spaces; however, having messed about 
with it I can see why it's so annoying - ruddy frustrating in fact. Grrrr - this
MUST be sorted out - what;s the point in it just giving you back the default
image (NB this doesnt happen if you dont use the options to set up different
root images to start with)


|> 
|> >     changing rooms - ie terminals
|> >        then how do other WMs remember the last root window image?????
|> 
|> Through the XTransferRootImageToNewTerminalWhenLoggedOntoDifferentTerminal
|> call ;-).

That's what I'll have to ask santa for next year, along with one of those
XWarpToWindowWhereUserIsLookingNotWhereCursorIsActive :-)))

|> 
|> Diversion
|> -- 
|> "I can see 'em                          | "Want me to create a diversion?"
|>     I can see 'em                       | Diversion
|>         Someone wake me when it's over" | rogerj@rpi.edu

Michael