LiteStep.net Forums

Does ckvwm (1.42) support getting hooked to xlabel?

The docs don't really talk about hooking and I can't seem to get it to work.

All I really need is a fadein/fadeout and support for alphatransparency. If this is possible without xlabel I'll take suggestions for that too.

Yeah, it does. Look under bang commands in the help file.

It does what? Fade or hook?

Here's what I have now:

VWMLoadInBox

*Label VWMContainer

*VWMContainerModuleHook !VWMLoadBoxHook

VWMContainerX 100

VWMContainerY 100

VWMContainerWidth $ShelfWidth$

VWMContainerHeight $VWMContainerWidth/1.5$

VWMContainerImage object.png

VWMContainerMovable

The label and the VWM are completely separate.

think xcal was saying it can be hooked, with the use of the hooking bang ;)

Ya, that's what I was saying.

jqubit, your syntax is wrong. It's !VWMLsBoxHook. See the bang section in the help file.

Also, make sure you're loading xlabel after the module you're hooking. Generally, it's a good idea to load xlabel last, unless you're loading labels in to xpopup or something.

I quote from the docs:

/****************** v1.42 (Seg@) 2004-10-23************///
//
// Added:
// - !VWMLoadBoxHook as a wharf mode hack
// Fixed:
// - Drag-n-Drop now works properly when VWM window is
// docked on wharf
// - VWMx and VWMy are interpreted as coordinates,
// so they can be defined as percents of the screen
// width/height and calculated from the center of the screen
// (see LiteStep core documentation for details).
// Added:
// - Documentation converted to the LSMD 0.3p format.
// This text file is still available.
//

This is the only place the work "hook" appears anywhere in the docs for ckvwm.

I'll try LSBoxHook, though.

hrm let me see here...

*vwmboxModuleHook !VWMLoadBoxHook

i used that to hook a vwm into a label, but im using RabidVWM-1.2.2. the VWM in the !VWMLoadBoxHook part is the name of the label, so if you want it to be hooked into for example a label called abc, you would put

*vwmboxModuleHook !abcLoadBoxHook

hope that helped.

History
Version 1.42, 2004-10-26 (Seg@)

ADDED: !VWMLsBoxHook implemented as a wharf mode hack

and

!VWMLsBoxHook
It's a bang which can be used in *ModuleHook lines of the LsBox and similar modules. See corresponding modules' documentation for details. Don't call this bang manually!

Like I said twice before, see the help file. You're looking in the text file.

stalefist: thats wrong. The !hook bang is used by the module that gets hooked. (I think your thinking of hooking labels into labels though)

Forgot to look for a chm - sorry!

Is NLM ever going to support extracting them?

I think it does now... whats the latest build someone? it was in the ls-u news recently... or something... :p

Yeah, 2.5.0. Of course if it had shipped as html instead of chm there wouldn't be a problem either. :P

yeah, I hate chm's, I mean... WHY!?

Why? Well, because you can arrange the documentation into chapters without the need to have several html files OR one huge doc that you'll have to scroll and scroll and scroll through... Imagine what the xLabel help file would be like if it was one single html doc :)

...it would look like the xPopup doc, but be several times larger :)

Or several linked html's? I'd prefer that I think (like at xdocs :)

Yet somehow I managed to get manageable single-page html docs for rabidvwm and lsxcommand. Sure, they're not xlabel, but they're not simple either.

The benefit I've had mentioned was that it's all in one file so you can just open that from the zip. Whatever.

I'm just saying that NLM was there before these chm docs appeared (else it would have supported them from the start), so it's not like it should have been a surprise. The choice to use (or continue using) chm was made with the knowledge that the docs would not be installed by NLM. (or so I assume) ISTM to make more sense to complain about the action that caused the problem rather than the inaction.

But anyway, upgrade and be happy. It all works now.