If I set the width for my VWM to any value below 100 the VWM is displayed at the correct width. If I set the width to any value greater than 99 the VWM is display 20 pixels less wide than what is should be.

For example
Specified Width - Displayed Width
84 pixels - 84 pixels
99 pixels - 99 pixels
100 pixels - 80 pixels
164 pixels - 144 pixels

Should this be expected? It's a pain as I use VWMWidth to position other elements.

That shouldn't happen. I've never seen or heard of it happening before either. and yet, it always happens :6 I'm getting a difference of 24 when VWMWidth>100.

For now, addThat seems to fix it, I'll try to get VWMWidth alone to work properly for the next release. Sorry for that :/

Thanks a heap for the work around :) It's appreciated.

This is a really, really strange bug.

It looks like the y-coordinate for the position is somehow affecting the width of the vwm, but only when the number is the last part of the setting and the width is >=100. (VWMWidth 100' actually works.)

Yes, that would be right. My Y is 20 and that's how much smaller it made X. I don't know what you mean by "only when the number is the last part of the setting" though.

Did you recieve my e-mail about another problem I found. I sent it a couple of days ago. VWMHideTaskOnSwitch is causing litestep to crash if I do a recycle. I sent that e-mail from work so if you've replied you can ignore this comment.

Yeah, sorry, I've been a little slow with email recently. I'm gonna need more information, like the exact text (and title) of the error message.

The error message is

.../modules/rabidvwm.dll
Exception while quitting module

Only happens if I recycle with VWMHideTaskOnSwitch enabled. I have to log out and log back in again to recover from it.