Seems I have trouble with my theme only on startup.The shortcuts and some boxes only show up when moused, clicked or recycled. Then the problem goes away till the next startup.
Install this theme then log off windows then log back in. I have no clue where to start on this. I've tried a script that waits then unloads and reloads LSbox, but that does not fix it. I've tried to destroy and create boxes, but again it did not solve the problem.
So, I take nobody has a worthwhile answer to this question?
Does 2.95 work fine?
When I have this problem, either there's a setting or two I messed up, or I have the image files being used open.
Try redoing the boxes, shortcuts, etc. again from scratch--it's worked for me in 2.95.
I don't know about the 3.0 previews.
I thing I tried 2.95 already but I'll try again thanks
this problem makes me mad too it happens with all themes using lsbox no matter what version it is... i hope it gets fixed sometime if not im not to good to recycle.
weird. never had any such startup problems with my lsbox themes, irrespective of v.2.95 or v.3.0_pre
I believe the issue arises from using taskbar3 in a box. If thier is at least one window open it doesn't happen. Example: when I start my pc I log in and immediately hit Ctrl Alt Del to open a dialog and litestep loads fine. If I do not do this I have to recycle for it work properly.
Can't be, TechRonin, at least as a usiversal thing, as I've expereinced it all the time and have not used a taskbar module in any theme yet, and I recycle all the time, always with several windows up. The easy solution is to use xLabel, but I've found it still has some quirks to work out, too (like some boxed labels not doing a onLeftClick action).
I think it may be a general windows config thing, because for me it will happen about 1/4 of every theme load for any theme using LsBox, while some people have never seen it.
I use Taskbar3 for all my themes and have noticed the difference in having a window open as opposed to not could be just how my theme was put to gether. I could try unloading that module and testing it.
xlabel 3.0 final should be out tomorrow, maybe you can wait until then and use it instead of lsbox. :)
there were many times i also had trouble with lsbox, but it was always related to some really tiny detail(s)... only when trying other's themes there were strange errors, but i never tried figuring out what they were caused by.