Glitch with VWM Thread last updated on 2003-04-08 13:53:50

Posted by member 2112 on 2003-01-30 01:19:50

For years I have b!!!ed about the windows shell. Would you believe it's taken me this long to discover Litestep?

Anyhoo, is there a glitch with VMW in litestep? I've found that if you have an application maximised when you switch between screens the application would carry along with it. I noticed this with the standard, simplicity, theme and with the Elegence theme (http://tronn.deviantart.com/) that is meant to be OTS. Or is this a feature of Litestep? I now have the Sputnik theme installed (http://www.lsthemes.com/theme.php?id=53) but this theme doesn't seem to let you switch when an app is maximised.

cheers

Posted by member 7 on 2003-01-30 02:09:24 link

Does it happen no matter what app is maximized? If so then it's a knwon bug which no one seems to have found the cause for so far. It's hard to track down since it seems to happen rarely and randomly. It usually just disappears after a while. If you can narrow it down to a certain module combination or certain step.rc settings please let us know, it'll help a lot in fixing this.

Posted by member 265 on 2003-01-30 03:45:57 link

i believe this bug appears when xp's visual styles are in use. perhaps you could try switching to classic mode to see if that solves the problem...

Posted by member 2112 on 2003-01-30 19:32:19 link

You're right. Does seem to be with XP's visual styles. I found that it was consistant with the Simplicity theme and random with the Elegence theme.

Posted by member 186 on 2003-01-30 20:39:21 link

*sings* They call him Dr. Worm.
Good morning. How are you? He's Dr. Worm.
He's interested in things.
He's not a real doctor,
But he is a real worm;
He is an actual worm.
He lives like a worm.

TMBG

http://www.sing365.com/music/lyric.nsf/SongUnid/E3B9527019947C62482568B1003069A2

Posted by member 182 on 2003-04-02 19:19:42 link

i hate this bug. it's not like every shell or vwm does it either - just litestep's .. what gives?

Posted by member 99 on 2003-04-02 21:07:05 link

it's not? Can you point me towards some VWM (with source available) that doesn't have this problem? Even if it's not litestep, it might be instructive.

Posted by member 31 on 2003-04-04 12:23:06 link

Any VWM, that hides the window instead of moving them, doesn't have the problem. Most non-litestep VWM's do it this way.

RabidCow, the best way I've come up with to handle this is to add an option that restores the window to an unmaximized state when switching VWs. Of course, if you are keeping track of what windows are on what VW, then you could tag that window as being maximized, and maximize it when switching back to the VW it is on.

if( !g_bKeepMaximized && IsZoomed(hWnd) )
{
ShowWindow(hWnd, SW_SHOWNOACTIVATE);
}


The only problem with this, is that you can not do it using the DeferWindowPos handler, so you will see the affect when switching VWs. :(

But, it works... And it isn't too annoying, since a simple hotkey bound to maximize a window will get you back to where you were when switching back to the window that used to be maximized.

Posted by member 99 on 2003-04-05 18:23:48 link

Ah, so everything would be happy with VWMHideTaskOnSwitch?

Un-maximizing the windows is a good idea, but it would take some work to get the miniwindows to still behave. (if I want to keep this fix transparent, which I would prefer) I could have it remember to remaximize the windows, except across recycles, reloads, and crashes.

(and I can think of a way to hide the restored window stuff while switching, but it would be silly)

Posted by member 31 on 2003-04-07 16:48:24 link

Good luck with it :) If you ever find a nicer way than hiding or restoring a window to make this problem go away, let me know. I don't like doing either. Especially the hiding. :/

BTW, I'm thinking of trying to start calling it all VDM (Virtual Desktop Manager) which I think you (or was it Maduin?) called it at one point. Since that kind of makes more sense in our MS world. I've already renamed everything internally to bangvwm.dll to such. Want to take the plunge with me, and confuse the heck out of everyone? :P

Posted by member 99 on 2003-04-07 21:28:52 link

The official position in the RabidVWM docs is "That W in the middle is actually just a D that looks like a W." So I feel justified in calling it a VWM (Virtual Desktop Manager) :)

Posted by member 31 on 2003-04-08 13:53:50 link

hehe, very well. :)