Wow, doesn't litestep just kick ass? I'm pretty new to litestep and after a few frustrating screw-ups (but those aren't important now) things are going nice. Ok so here's my question.

I have winamp 5.0 up and running (lets say its on VWM #3, and lets say i also have a website up (on VWM #1 for example). Now i want to see my desktop b/c i want to select a icon so i click on VWM #2 to see my desktop(for example)
Now winamp decides this is a good time to pop up to let me know its still running.
So how do I stop winamp from jumping from VWM to VWM.

and if this has already been ansered in another thread dont yell at me, the search feature is down.

In your WinAmp Preferences there are two options you have to shut off to disable LS VWM Support. They are pretty obvious but since I don't have it in front of me I can't point you there. Once those are off you should be golden.

i found them. Ur right they are pretty obvious. Thnx

what number to call for details.... ;)

so most likely i'm being stupid, but I used to know where these options to uncheck were in old winamps.. however, I can't seem to find them in winamp 5.2, anybody want to give me a hint, the delayed following is getting to be a big pain in the ***

nevermind.. found the problem

*from winamp forums*
"(this is why freeform doesn't support the litestep option, though we might be able to devise something in the future)."

grrr... oh well, back to wasabi until some alternate future, thanks for reading

??

translation for those of us just jumping back into using litestep after being away for a few years and have no idea what you're talking about :D (also known as "g'**mn noobs")

your VWM module allows for applications to follow you on all VWMs.

ok, now that makes sense.. thanks... one moe question though, will the vwm module let you lock an application to only one vwm as opposed to following you?

yes

I think that's what *VWMFix is for.

Dunno, that seems like a very strange questions, since it's the default behavior. If you're talking about tool windows or other child windows, then *VWMFix is indeed the stuff. If the window in question pretends to be a litestep window (which is very rare) or uses some other trick, it may not be possible.

It's also possible that the effect you want is covered by *VWMStartWindowsOnDesktop, read the docs and see.

Oh, and it might be the StyleXP bug rearing its ugly head again. Ironhead has informed me of a fix for this, but I have yet to implement it. So if you've got XP styles going, turn it off. :P

thanks all, apparently I have more reading to do..

It seems to me that *VWMFix is only to let children windows stick to the parent window like toolbars in Photoshop or in Dreamweaver or anything...
So it might just simply not work for a certain window and besides even though the options in Winamp 5 are fairly obvious they just don't work. Maybe because of the windows-styles in XP again (but it looks so ougly without it in my opinion), maybe because of the Winamp skin, maybe it is something else...
I tried to fix the Classname and some of the hidden childwindows but it doesn't really work.
What actually confuses me a little is that *VWMFix doesn't include a desktop specific variable... is there something similar that does?
Maybe someone could write a module that is similar to the winamp playlist, in glaze for example it could easily fit between the amp_controls and the systemtray. Wouldn't that be cool? ;7

Alright, I finally went and installed WA5, and I see the problem with the "Modern" skin. Winamp is being a little rude here, it's aggressively trying to keep you from moving its windows offscreen, which is exactly what the VWM wants to do.

The Classic skin is a different matter... Their LiteStep preferences don't seem to have any effect at all (at least with RabidVWM), and the playlist seems to be refusing to move for some reason. I suspect it has something to do with the fact that you can resize the playlist. (it looks like it's responding to WM_WINDOWPOSCHANGED by changing its position, which doesn't seem like the best way to achieve whatever effect they're trying to achieve, but I could be wrong, especially considering that I have no clue.)

Anyway, the only thing that I have found to reliably contain Winamp is to use VWMHideTaskOnSwitch and the Classic skin. If VWMHideTaskEtc worked better, you could probably use the Modern skin, but alas it ain't so.

I'm not completely sure why *VWMFix doesn't work on the playlist window (it has an owner...), but I am completely tired.

i think what nullsoft was trying to do here was keep winamp from running off the screen on you in a regular (using explorer as the shell) environment. they added the "always on litestep virtual desktops" option so that you could keep it in front if you wanted to. i like to always have winamp in the front in it's compact form, and i do sometimes use that option. not always tho, which is why it's nice to have it be a selectable option.

coolbtk@mchsi.com