Alright, so As most have read my other post, I've moved from shortcut to xlabel because it's just better.... Moving on...
My question now is how does Zorder work in xLabel. I don't mean Zorder with application windows, but I mean Zorder with other labels.
What I am trying to do is put one label under all the other labels. Now, does the label group have anything to do with this or is there something else that needs to be done?
*wish : Be able to group labels together in "layers" like for example Photoshop!
(labelname)BehindWindow "xLabel" "(labelname)"
If the labels are not dynamically changing z-order, that should be able to be used to do the trick. You'll need to work them into layers yourself (it's possible, but unless you have dozens of labels to worry about, likely not worth doing), or just use a one-directional list.
Be aware, this sometimes won't work right immediately. If that happens, show and hide all the labels. That has always fixed it for me (the z-order will stick once it is done, so only needs doing right after NLM finishes loading modules).
Ok, I tried it a few times, restarted, reloaded, recycles, the whole deal and to no avail.
BarBehindWindow "xLabel" "seperator"
Also having a problem with xTaskbar not wanting to be on top, and xTray. Can I do the same thing for these two modules?
Is there a way I can put multiple Labels in? like comma seperated. I can get it to work but for only one label.
Does your label on the bottom ever need to come to the surface for any reason? If not, just hook the upper labels in to the lower one.
*parentModuleHook !LabelLsBoxHook child
Doing that will essentially make the parent label the child label's desktop. So x/y positions are relative to the inside of the parent.
A parent label can have multiple child labels, and child labels can have their own children.
you can also use magic pink and cut the area out on the bottom labels...
Ok, I'm not sure I understand exactly how the *parentModuleHook works. I understand the concept but I think I need more info. Is there some good documentation somewhere that I can read about it?
Make two labels like normal. One to be the "container" which will appear as the bottom label. Make another to be the label that goes inside the container label. Lets say the container (aka parent) is named Big, and the label that's going in to the container is named Boobies (aka the child). Your hook line will look like:
*BigModuleHook !LabelLsBoxHook Boobies
Then, you have to keep in mind, that the x/y coords to position Boobies, inside of Big, is relative to Big's top/left corner (which Boobies will see as 0/0 - so if you give Boobies x/y coords of 10x/10y, it'll be 10px off of Big's top/left).
10px is *not* very big, xcal.
Sweet, that works. Thanks for the help there. This makes things so much nicer. :)
Ok, I've got a new problem now... when I "hook" on other modules, as soon as I click on the Big label the modules fall behind it and won't come forward again. Is there a way to fix this? The Labels work great though... Actually, I have a question about them too, the AlphaMap doesn't work with them now... Is there a way to fix this?
I could have sworn that Andymon discussed all of those things in the included help file... ;)
Yeah, free help time is over...time to open the xlabel help file.
(I only explained hooking because that can be tricky at first, and I wanted to say Boobies. Plus, I didn't quite get the new problem.)
This happens so often it's disgusting... Ya know if the help file explained it well enough I wouldn't be asking so many questions... the fact of the matter is I've searched the file and read it all and there just isn't enough information there. I've done EXACTLY as the file says and it still doesn't work. Anyway... forget this.
Well, more help is going to require seeing what you've been trying, and what you're trying to do. Don't give up yet. If it's too much crap to post here, email me.
I agree with xcal...but what you have tried shouldn't take up all that much so post it here. Maybe it will help someone else down the line.
Ok, here is my "Hook" part.
*BarModuleHook !LabelLsBoxHook LS_Menu
*BarModuleHook !LabelLsBoxHook Dingy_Hide
*BarModuleHook !LabelLsBoxHook Seperator_1
*BarModuleHook !RainmeterLsBoxHook
*BarModuleHook !LabelLsBoxHook Seperator_2
*BarModuleHook !xTaskbarLSBoxHook Taskbar
*BarModuleHook !LabelLsBoxHook Seperator_3
*BarModuleHook !LabelLsBoxHook VWM_Back
*BarModuleHook !LabelLsBoxHook Seperator_4
*BarModuleHook !LabelLsBoxHook Command_Back
*BarModuleHook !LabelLsBoxHook Seperator_5
*BarModuleHook !LabelLsBoxHook Seperator_6
*BarModuleHook !xTrayLsBoxHook
*BarModuleHook !LabelLsBoxHook Seperator_7
*BarModuleHook !LabelLsBoxHook Clock_Back
;*BarModuleHook !ClockWorkHook
*BarModuleHook !LabelLsBoxHook Digital_Clock
*BarModuleHook !LabelLsBoxHook Date_Text
*Label Bar
BarX 0
BarY -62
BarWidth 1600
BarHeight 62
BarToolTip ""
BarAlphaMap FALSE
BarAlwaysOnTop FALSE
BarImage $scheme$taskbar.png
BarHoverImage .none
BarPressedImage .none
BarOnLeftClick .none
BarAddToGroup 4
BarCustomAlphaFade 10 10
Now, a few problems I am having here...
#1 Alpha Transparency doesn't work within the Box.
#2 xTaskbar doesn't update, it loads in the beginning but that's it, it isn't "Active" what I mean it is just like an image that is sitting there.
#3 Also if I hook Clockwork it falls behind the bar. If it is unhooked it's fine.
I think that's it for now...
1. That's right. If you set AlphaMap with a png, that label can no longer hook, or be hooked. But, since everything that's hooked takes on the parent's attributes, you can still set AlphaTransparency for the parent - it's all or nothing, though.
2. "!xTaskbarLSBoxHook Taskbar" Unless you've named your taskbar "Taskbar," that should be !xTaskbarLSBoxHook xTaskbar.
3. Not sure about that one, but...
Also, load order matters. Modules that are to be hooked must be loaded BEFORE xlabel. Generally, it's a good idea to always load xlabel last in your theme.rc. (The only situation I can think of where you wouldn't want to, is if you're hooking labels in to xpopup.)
Example:
Wrong order if hooking xTaskbar:
*NetLoadModule xlabel-3.5
*NetLoadModule xTaskbar-1.4.1
Right way:
*NetLoadModule xTaskbar-1.4.1
*NetLoadModule xlabel-3.5
So you are saying I can't use AlphaMap at all if I have other labels inside a parent label? If I turn AlphaTransparency on in the parent label all of the other ones don't show up, as though they don't exist. If I turn it off the PNG's have black backgrounds instead of transparent, note that this is with AlphaMap=TRUE.
Also, I changed the stuff with xTaskbar, and am still having problems with it. All modules are loaded before xLabel too. Not sure exacly why it does this.
This is kind along but here is my xTaskbar code, is there something wrong with it?
REMOVED cause it was worthless...
I'm in a rush, and about to go out, but off the top of my head:
This setting doesn't do anything to a hooked xTaskbar (or labels):
xTaskbarCustomAlphaFade 10 10
This setting has to go. You can't use alphamap images with a hooked xTaskbar (or labels):
xTaskbarAlphaMap TRUE
You're also defining a lot of settings that are already default. For example: xTaskbarFontOutline FALSE. It's false by default.
Ok, here is what I've done... Cause now I have it working.
I have a "Bar" that contains all of my labels and modules. I killed clockwork cause it was having problems, it looks pretty but not worth the trouble at the moment... Anyway...
I hooked all the modules onto the bar and that works great, all of the labels I removed from being hooked and now it works great. They float above the bar and the bar stayes behind them, a long with all of my modules. And they all stay behind my probram windows now.. Woot. Also, this way I can use AlphaMap on the labels cause they aren't attached to the parent.
Thanks a lot for all of your help everyone. I really appreciate it. I think I know what I might be doing now!... Haha. I'll be back though, I promise.