Posted by member 71746 on 2003-10-29 11:47:16 link
Cerb, I agree wholeheartedly. I've wanted to specify mouse in/mouse out effects for LSboxes and especially for the builtin LSBox shortcut engine! (Sure, you can change the shortcut image on hover, but can't add anything else like showing/hiding other LSBoxes or setting the alpha-blend of a box)
Also, bang-controlled box-blending would be cool..
It's funny, you'd think any .RC setting should naturally be accompanied by its associated !bang command, but there's a TON of modules that only have function-related !bangs and no settings-related !bangs... It's just common sense people! :D
To get source for most LS Modules (at least, most current and commonly-available modules) check http://www.shellfront.org/modules/source/ :)
As for !ModuleUnHook and bang-controlled !BoxHook with as an argument, it could simply be implemented into LsBox instead of individual modules. Simply add a routine to allow on-the-fly hooking, with a syntax like
That way other modules wouldn't have to be altered and no new standard would have to be adopted for new modules..
Also, bang-controlled box-blending would be cool..
!LsBoxAlphaTrans (box name) (new blend level)
It's funny, you'd think any .RC setting should naturally be accompanied by its associated !bang command, but there's a TON of modules that only have function-related !bangs and no settings-related !bangs... It's just common sense people! :D
To get source for most LS Modules (at least, most current and commonly-available modules) check http://www.shellfront.org/modules/source/ :)
As for !ModuleUnHook and bang-controlled !BoxHook with as an argument, it could simply be implemented into LsBox instead of individual modules. Simply add a routine to allow on-the-fly hooking, with a syntax like
!LsBoxHook (module name) (hook command)
// example: !LsBoxHook BoxOne !CommandBoxHook
// this would hook LSXCommand to BoxOne when called.
// !LsBoxHook BarAnchor !LSMailHook
// this would hook LSMail to a Bar
!LsBoxUnHook (box name) (module)
// (module) would be taken in the same style as in grdTransparent, where you just specify the name of a loaded module without the path or extension.
// example: !LsBoxUnHook BoxOne lsxcommand-1.8.4
// example: !LsBoxHook BoxOne !CommandBoxHook
// this would hook LSXCommand to BoxOne when called.
// !LsBoxHook BarAnchor !LSMailHook
// this would hook LSMail to a Bar
!LsBoxUnHook (box name) (module)
// (module) would be taken in the same style as in grdTransparent, where you just specify the name of a loaded module without the path or extension.
// example: !LsBoxUnHook BoxOne lsxcommand-1.8.4
That way other modules wouldn't have to be altered and no new standard would have to be adopted for new modules..