Is there a way to prevent an individual module from recycling, but have all others recycle as normal? If not, please read below so I can explain the dilemma I'm having and maybe someone here will have ideas.

On the theme I'm working on, I'm using the following modules:
xLabel 3.55
xPopup 1.2 (1.2.5 I don't like as much)
xTaskbar 1.4
xTray 1.0
Command

A problem I keep running into is that when I go to a full screen application (like a computer game) when I return from it, many of the graphics to my modules lose their AlwaysOnTop status, or disappear completely. I might be able to solve this by having an automatic recycle on a screen change and have everything start hidden, but xPopup presents a problem there.

I really like xPopup's caching feature. Unfortunately it takes it a minute to cache everything before it works (1.2.5 won't cache everything for me for some reason, there's still an initial delay in the menus). I don't mind this loading lag when Litestep first starts up, but to have it happen everytime I go in and out of a full screen application would be impractical. Does anyone have an idea how I might work around any of these problems?

Rather than recycling, you might try doing a !netreloadmodule of all the affected modules, excluding xpopup. Stick them all in an !execute [][][] sequence and bind it to a hotkey. That might restore all of the borked features.

Personal preference:

I hate modules or images set to always on top.
Major downfall for games or full screen apps.
I prefer to cut holes in the images with magic pink for transparent areas.
Then place the img or modules to fit in nicely...

IMO the better work around.

Boreas: I haven't worked with !netreloadmodule, I'll be sure to check it out. Thanks.

Immortal: I'm not sure if I follow what you're saying. I get the feeling my theme might not accommodate what you're talking about. As for the always on top thing, I like it, but I assign a hotkey to hide everything for when I do want to do fullscreen applications. The problem is when I come back out of that.


Also, I've found that xLabel looks pretty solid, after a series of tests, it didn't mess up once. Good code there.

If xlabel is working well for you, you could just hook the taskbar/tray/command in to their own labels.

Yargh, more crap to learn. But thanks xcal, this will probably be a cleaner solution. I never investigated that aspect of xlabel much prior to this. At least I know this should be possible now.

I don't have any docs in front of me...but don't some of those modules have an AlwaysOnTop bang?

AFAIK all of the xmodules have that bang.

The module hooks seem to be working well except for xTaskbar, it's completely ignoring the settings I have for icon size, text displayed, etc. Am I implementing it incorrectly?

Apparently. =P

Your settings should all be prefixed with 'xtaskbar' unless you've given your taskbar a name (you can do this in order to define multiple taskbars). If you've named your taskbar, then you need to prefix the settings with your specific taskbarname instead.

Alright help me out a bit if you don't mind. I'm not at my computer right now, but here are the settings I recall:

xTaskbarLoadInBox
xTaskbarWidth 438
xTaskbarHeight 39
(misc other settings that work fine without using the hook module)

Under labels I have this:

*Label LabelTask
LabelTaskModuleHook !xTaskbarLSBoxHook

LabelTaskWidth 438
LabelTaskHeight 39
LabelTaskX 272
LabelTaskY -39
LabelTaskImage taskbar.png

Beyond this, I don't know how to implement xTaskbar's features into the label. xTaskbarShowText for example. I have that normally set to false, but it is obviously being ignored when I hook the module in as a label. How do I add this setting so that the label implements it?

Thanks again

Try this instead:

*LabelTaskModuleHook !xTaskbarLSBoxHook xtaskbar

Thanks, looks like that worked!