Problem with [noir] VWM? Thread last updated on 2005-11-03 18:04:00

Posted by member 78566 on 2005-11-02 06:10:01

Got a problem that's really beginning to annoy me.

[noir] has 6 VMs by default, and you can switch between them either by the bar or using hotkeys.

The problem I have, is that when I have apps open and maximized, whenever I go forward through the VMs it carries that app with it. So if I open say Opera in VM1, then move to VM2, it moves Opera to VM2. Very annoying. It doesn't move them the other way, so once Opera is in VM2, if I move back to VM1 then it stays in VM2.

Is this a problem with [noir] or one of the modules?

How do I fix it? It's only recently started doing this :-(

Posted by member 148416 on 2005-11-02 06:53:11 link

It's a module error... and... *tada*... there is a fix :)

Change rabidvwm version to rabidvwm-1.2.1i and all will be golden :)

*note--I dont use vwm's and have only been told about the supposed 'fixed' version that this release is. So, yah.

Posted by member 1316 on 2005-11-02 12:18:36 link

yep, rabidvwm-1.2.1i fixes it. I'm running it right now. basically, previous versions of rabidvwm didn't like windows visual styles, so if you were using anything other that the Classic Windows style, you would get the behavior you explained above.

Posted by member 248213 on 2005-11-02 20:10:43 link

I noticed that with 1.2.1i I lose maximised windows on !recycle

happen with anyone else?
must be related to this fix...

Posted by member 1885 on 2005-11-03 02:42:08 link

No... I don't think so. Running1.2.1i here, and maximized windows stay maximized on recycle.

Posted by member 212670 on 2005-11-03 04:16:50 link

Maximized windows on other desktops seem to minimize on a recycle for me. Maximized windows on the current desktop stays maximized.

Posted by member 78566 on 2005-11-03 08:10:44 link

Ok, so how do I update rabidvwm?

And on a slightly related note - has anyone got, or does anyone know where I can get, a copy of the windowsblinds theme for [noir]? I've got the vis styles one (that explains why rabidvwm only just started complaining, btw) but it doesn't cover everything. I think he took it down from everywhere, but [noir] was my first entry into different shells and windows styles, and I had the full suite. I have fond memories *wipes a tear from his eye*

Posted by member 1316 on 2005-11-03 11:30:39 link

I've gotten that behavior a couple times, but it's not constant. !vwmgather brings them right back though.

in the theme, where it says
*netloadmodule rabidvwm-1.2.x
change it to
*netloadmodule rabidvwm-1.2.1i

Posted by member 78566 on 2005-11-03 11:58:26 link

hmm. That line isn't there. Is it safe to add it?

Posted by member 12025 on 2005-11-03 12:26:10 link

Not if it isn't OTS2. If it's not, copy the NLM setup from your step.rc into the theme's step.rc, find the line where it currently loads rabidvwm, comment it or delete it, then add the NLM line to load it.

Posted by member 78566 on 2005-11-03 12:54:06 link

I've checked the readme and it is OTS2 compliant. I guess that explains why there isn't a step.rc for the theme itself.

(Quick note - I'm a newb when it comes to fiddling with the workings of ls - the best I've done so far is transparant popup and customize the content of it.)

Here's my step.rc

;------------------------------------------------------------------------------
; define critical folder locations
;------------------------------------------------------------------------------

PersonalDir "$AppData$\LiteStep\personal\"
ThemesDir "$AppData$\LiteStep\themes\"



;------------------------------------------------------------------------------
; load personal settings and theme
;------------------------------------------------------------------------------

include "$ThemesDir$themeselect.rc"
include "$ThemeDir$config\_compatibility_patch.rc"

IF ThemeIsOTS1Compliant
ShortcutsDir "$Desktop$"
ModulesDir "$ThemeDir$modules\"
include "$PersonalDir$personal.rc"
include "$ThemeDir$step.rc"

ELSE
ThemeIsOTS1Compliant false
ModulesDir "$LiteStepDir$modules\"
LoadModule "$LiteStepDir$NLM\NetLoadModule2.dll"
*NetLoadModuleSite "http://www.loose-screws.com/download.php?netloadmodule="
*NetLoadModuleSite "http://modules.shellfront.org/"
NetLoadModulePath "$ModulesDir$"
NetLoadModuleDocPath "$ModulesDir$docs\"
NetLoadModuleZipPath "$ModulesDir$archive\"
NetLoadModuleAliasFile "$LiteStepDir$NLM\NetLoadModule.ini"
include "$PersonalDir$personal.rc"
include "$ThemeDir$theme.rc"
ENDIF


And the NLM bit from my theme.rc
;///---Modules---\\\
;DO NOT EDIT THE ORDER OF LOADING UNLESS YOU ARE HAVING UNUSUAL ERRORS

*NetLoadMOdule grdtransparent-1.1_beta_1
*NetLoadMOdule shortcut2-2.0
*NetLoadMOdule vtray-1.06
VtraySettingsCompatibility
*NetLoadMOdule tasks-0.92-b3
*NetLoadMOdule jdesk-0.711
*NetLoadMOdule jamptoo-1.4
*NetLoadMOdule lsmail-4.3
*NetLoadMOdule lsslider-1.71
*NetLoadMOdule geekamp-1.9.7
*NetLoadMOdule popup2-2.0
*NetLoadMOdule label-1.99
*NetLoadMOdule ckvwm-1.40
*NetLoadMOdule mzscript-0.9_beta-11-jam3

Posted by member 212670 on 2005-11-03 13:29:42 link

Ah ha, it's using ckvwm. Change ckvwm-1.40 to rabidvwm-1.2.1i. I don't think the syntax is completely the same for the configuration of those modules, so you may have to do some tweaking.

You'll find the docs in \Litestep\modules\docs

Posted by member 78566 on 2005-11-03 13:38:08 link

Eep. Config. :-(

Posted by member 78566 on 2005-11-03 14:15:01 link

Ok, installed it and it worked from the start, which was fun. The only thing that's confusing me is that the desktop number (it doesn't have any of the visual reps of the desktop, and to be honest I don't think I want one) doesn't change! So I don't know which desktop I'm on!

This is vwm.rc:
;---///Virtual Window Change Scripts\\\---
*Script bang !one
*Script exec !windowsettext "Window 1"
*Script exec !vwmdesk 1
*Script exec !varSet ckvwm 1
*Script exec !varsaveall replace
*Script ~bang

*Script bang !two
*Script exec !windowsettext "Window 2"
*Script exec !vwmdesk 2
*Script exec !varSet ckvwm 2
*Script exec !varsaveall replace
*Script ~bang

*Script bang !three
*Script exec !windowsettext "Window 3"
*Script exec !vwmdesk 3
*Script exec !varSet ckvwm 3
*Script exec !varsaveall replace
*Script ~bang

*Script bang !four
*Script exec !windowsettext "Window 4"
*Script exec !vwmdesk 4
*Script exec !varSet ckvwm 4
*Script exec !varsaveall replace
*Script ~bang

*Script bang !five
*Script exec !windowsettext "Window 5"
*Script exec !vwmdesk 5
*Script exec !varSet ckvwm 5
*Script exec !varsaveall replace
*Script ~bang

*Script bang !six
*Script exec !windowsettext "Window 6"
*Script exec !vwmdesk 6
*Script exec !varSet ckvwm 6
*Script exec !varsaveall replace
*Script ~bang

;end


The VMWDesk works, so must be common to ckvwm. And the "*Script exec !varSet ckvwm 6" bit sets the last vwm used to no. 6, so it loads that on startup.

It must be the "*Script exec !windowsettext "Window 6"" bit, which wasn't part of ckvwm.

I'm confused :-(

Wish [morph] was still around.

PS: I have RTFM for Rabid, there is now windowsettext.

Posted by member 212670 on 2005-11-03 15:18:04 link

Ok, I'll give you the answer since it's not completely obvious.

In the theme.rc, for the sake of organization, scroll down to VWM Settings section. Add the following on its own line in that section:
vwmOnSwitchTo ^@#d^VWMOnSwitchTo^@dc^^@#d^

Now, for each VWMOnSwitchTo(#) line, put the command part in quotes. For example:

VWMOnSwitchTo3 "!Execute [!three]"

Note: The "!Execute" part is actually not necessary and can be removed. It's for running a series of !bangs, and not needed for just one !bang. It could simply just be, for example:

VWMOnSwitchTo3 "!three"

And so on.

Posted by member 78566 on 2005-11-03 17:12:24 link

Thanks! That's that bit working.

Just now, any maximized apps outside of the current desktop get minimized on recycle. This confuses me further!

:-(

Posted by member 212670 on 2005-11-03 18:04:00 link

Well... for all the times you need to recycle during normal operation of your computer, it really shouldn't be an issue.