rabidvwm error Thread last updated on 2003-11-06 03:31:13

Posted by member 33819 on 2003-11-03 04:16:49

I'm using rabidvwm-1.01 adn nearly every other time I recycle I get a 'failed to register window class' error message.

is this a know issue with vwm or would it be something specific to my setup?

Posted by member 7223 on 2003-11-03 09:06:45 link

Are you sure the "failed to register window class" apply to RabidVWM ?

Posted by member 99 on 2003-11-03 10:22:01 link

Make sure you aren't loading it in two places. Otherwise this shouldn't happen. This is only expected on recycles after rvwm crashes. (and it shouldn't crash...)

Posted by member 33819 on 2003-11-03 17:27:06 link

in my theme.rc:
*NetInstallModule rabidvwm-1.01


in my script.rc, before the lsbox thats going to hold it is created:
*script exec !reloadmodule "$modulesdir$rabidvwm-1.01.dll"


this sounds right to you?

Posted by member 99 on 2003-11-03 21:04:35 link

That should work, but it's a little weird. Is there a reason you can't use *NetLoadModule? (or is that for the freeze-on-startup bug? :6 )

Actually paying attention to Smurth for a moment, if the error message is not "Error registering window class" then it isn't RabidVWM.

Posted by member 12025 on 2003-11-03 21:24:39 link

I had the same thing, and it was something wrong with loading it into a box (I think I had VWMLoadInBox spelled wrong, but not sure, since I had the problem and fixed it a couple weeks ago).

Posted by member 33819 on 2003-11-04 11:47:30 link

I dont want to use NetLoadModule do if I'm gonna load it into a box? I just want to install the module and then load it when im going to create the box

Cerbie sounds like the same thing you may have had. you know how you fixed it?

Posted by member 33819 on 2003-11-04 11:51:24 link

I'm assuming the error is with RabidVWM because the error dialog box's title is 'RabidVWM' =D

also it doesnt do it every recycle. only maybe half the time. it's very odd....

Posted by member 99 on 2003-11-05 00:15:31 link

Oh ok, I see.

Are you creating the box from the same script as where you're loading rabidvwm? It might be related to the !reloadmodule synchronization problem.

Posted by member 33819 on 2003-11-05 05:06:21 link

from theme.rc:

*NetLoadModule grdtransparent-1.1_beta_1
*NetLoadModule desktop2-2.0
*NetLoadModule popup2-2.0
*NetLoadModule lsbox-2.95
*NetLoadModule mzscript-0.9_beta-11-jam3

*NetInstallModule lsxcommand-1.8.4
*NetInstallModule taskbar3-0.306_alpha-3
*NetInstallModule rabidvwm-1.01
;*NetInstallModule ckvwm-1.40
*NetInstallModule systray2-2.0


from script.rc:
*script bang !vwmboxload
*script exec !reloadmodule "$modulesdir$rabidvwm-1.01.dll"
*script exec !pause 1000
*Script gotoif ("%{VwmBoxStyle}" = "horiz") load_horiz
*Script gotoif ("%{VwmBoxStyle}" = "vert") load_vert
*Script exit
*Script label load_horiz
*script exec !lsboxcreate "$themedir$config\vwmhoriz.box"
*script exec !VWMMove 18 2
*script exec !VWMSize 160 40
*script exec !VWMSetDesks 4 1
*Script exit
*Script label load_vert
*script exec !lsboxcreate "$themedir$config\vwmvert.box"
*script exec !VWMMove 2 24
*script exec !VWMSize 40 160
*script exec !VWMSetDesks 1 4
*Script exit
*script ~bang

Posted by member 99 on 2003-11-06 00:49:36 link

Hm, I don't know if !pause is enough to make it load the module at that point. Does it ever fail if you take the !reloadmodule out and manually execute them as two separate commands from lsxcommand?

I know this isn't a viable solution, but if it is the !reloadmodule problem, you may have to wait for the next release of litestep. (or use *NetLoadModule and live with the extra resources) And if it isn't, well then I probably have to fix something.

Posted by member 33819 on 2003-11-06 03:31:13 link

ok I've tried using NetLoadModule and everything seems to work fine. recycled about 10 times and no error.

whats the difference in terms of overhead, mem usage etc in using NetLoadModule and using NetInstallModule followed by a !reloadmodule?

and thanks for your help Rabid and the rest =)