I just started with RabidVWM since it supports lsbox hooking. I've read through both module documents and can't find out what I'm doing wrong.

This is my step.rc code


and this is my .box code



With that config RabidVWM does not load at all let alone inside the LSbox.
When I call !VWMmove 0 0, or !VWMsize 256 256 the box then appears outside the box in the top left corner with no images being used.
Where am I going wrong?

Well, looking at it now I've noticed I've called a few things mutliple times. I'm gonna clean that up and see how it goes.
:/

Yeah, even after cleaning the double entries I still get RabidVWM telling me to please specify VWMSize and that I have the number of desks set to 0.

Wich as you see in the code isn't true.

I've also loaded the VWM code in the step.rc after the "VWMLoadinBox" with no luck.

Don't put quotes around "VWMLoadInBox" I have no idea if it makes a difference, but it sounds like it might.

I recommend putting the VWM settings in step.rc rather than the box file for now, since it won't read from the box in .24.7 until I can rewrite some stuff.

Make sure you're loading rabidvwm before lsbox, or at least before the box is created.

Yeah, I moved all the settings to the step.rc but I'm still having no luck. Removed the quotes as well with no help.
As it is now, the VWM isn't showing anywhere on the desktop or in the box on a refresh, and when I call !VWMreset or !VWMmove 0 0 it appears in the top left outside the box.

/me bangs his head on his keyboard.

Okay... Are you using v1.01?

If that doesn't help, could you try the debug build at http://www.technoirotica.com/~rabidcow/RabidVWM-1.01-d.zip and send the c:\rabidvwmlog.html that it creates to me at rabidcow@juno.com?

am running rabidvwm.dll just nicely in lsbox.
all of rabidvwm settings are specified in step.rc (and none in *.box - well, except for: *ModuleHook !VWMLoadBoxHook).

here's my step.rc settings:
VWMLoadInBox true
VWMX 2
VWMY 0
VWMDesksY 4
VWMDesksX 1
VWMwidth 40
VWMheight 120
VWMDeskSpacing 10 10
VWMSnapWindowOnDrag true
VWMNoSwitchOnFocus true
VWMNoGathering true
VWMTitlebars true
VWMTitleForTitle true
VWMBackBmp vwm_back1.png
VWMSelAlpha 70
VWMSelColor C0BEBF
VWMSelBorderColor 000000
VWMWinAlpha 200
VWMWinColor ABABAB
VWMWinBorderColor 13181C
VWMTitleColor 216D94
VWMTitleBorderColor 13181C
VWMOnQuit !LsBoxSavePosition control.box

notice the VWMX and VWMY coordinates....

RabidCow: Yes I am useing 1.01, downloaded 4 days ago and I think it's just lack of experience with your VWM module and LSbox combine that is causing the problems. I appreciate your help though! :)

ceeslans: Right.. the VWMX and VWMY settings can also be done with VWMPOS X Y. :)
Something I'm currently missing is the "True" setting after VWMLoadInBox.

I'll throw that on and see if it help any.

No luck so far. Here's where I'm at currently with my attempts.

This is my step.rc


and here is my .box



If any of you can see something I've done wrong, slap me with it. :p

Thanks agian for the help.

This is wild.. useing the code above, I have no VWM at all untill I call !VWMReset.

When I do that, the VWM appears full screen outside of the box, and I can then call other VWM bangs and effect it.

Haveing a 1280x1024 VWM is ..... Interesting. :p

But other than that, the VWM isn't loading in box and doesn't respond to bangs untill !VWMReset is called.

Rabidcow: If I can't figure something out by tonight I'll download your debug build and see if we can't figure something out.

Any posible bugs with other modules?

Here's what I'm loading currently.

afaik lsbox-hooked modules must be loaded before lsbox itself. check whether that helps.
oh - and shouldnt vwmwidth|height be specified (these settings now seem commented out)

As long as I'm loading into a box I shouldn't need them. The VWM will take the full size of the lsbox size. But I've tried using them and it makes no difference.
Because they were commented out, when I did my !VWMReset the VWM took up my entire screen. A quick !VWMSize fixed that.

As for loading position, I've tried loading Rabidvwm.dll in multiple places with no luck.

and we have progress..
Rabid, need your opinion on this one..
I commented out
and got the VWM to finally load in the box.
However the VWM isn't displaying 2x2 properly, and without VWMTransparent and VWMUseTransBlt I can't use any images with transparency in them..

Could this be a possible bug with VWM and LSbox in regards to transparency?

Ok, I'm wrong on 1 thing.
The VWM is displaying 2x2 properly.

But I still can't use VWMTransparent or VWMUseTransBLT without the CPU going to 100% usage and cokeing the entire system.

Ah, VWMTransparent might not work in a box. (maybe if you also set the box to use alpha transparency) There's some weirdness in the way Windows deals with that. VWMUseTransBlt should be fine afaik.

and if you're loading the box on startup, you *MUST* load rabidvwm before lsbox or you will definitely get an empty box. If you're loading it later with !lsboxcreate, it doesn't matter.