You are not logged in.
I'll investigate it, I've never heard of this hook config... you sure you aren't confused with ion? :-D
no, skoal mentioned it in another thread... you can hook-client, but there's no unhook action (that's the name hook-client)
Offline
Dusty wrote:I'll investigate it, I've never heard of this hook config... you sure you aren't confused with ion? :-D
no, skoal mentioned it in another thread... you can hook-client, but there's no unhook action (that's the name hook-client)
Yep, I found it, it works perfectly. Now you tell me there's no unhook action. Grrrr. Oddly enough though, I can't find the action in any of the conf files, so who the hell is saving it!?
Offline
hmmm according to the code, there *is* an unhook action...
it's saved in wmi.session like:
client.<classname>::<instancename>.hooked = <workspacename>
or at least it should be
Offline
You're on roll, keep on contradicting me.
You're right, the hooked line IS there now. When I looked at it before I hadn't logged out of wmi yet, so apparently wmi.session isn't updated until you log out.
I can't find unhook-client on the input bar.
Dusty
Offline
I can't find unhook-client on the input bar.
Yeah, I can't either... but it's in the code... weird... I guess you can just remove the session line...
Offline
so I've discovered some things about wmii:
I like it
The part I didn't like was the configuration. However, it's not supposed to work that way. For now it is a barebones setup. I'm going to throw together a rough python configuration system to make it easier - talking to people on the wmi-devel list now about it.
If all goes well, the new version of wmizer will incorporate the interface as well (which will allow for dynamic changing of properties... no need to restart).
I'll try suggesting a fix for the unhook-client thing to wmi-10, though it's no longer in development, perhaps they'll still accept patches...
Offline
I'll follow you wherever you go....
Dusty
Offline
Dusty wrote:I can't find unhook-client on the input bar.
Yeah, I can't either... but it's in the code... weird... I guess you can just remove the session line...
AHA! unhook-client only appears if the focused client is hooked
Offline
only its not working.... cause I have firefox hooked, and its focused... and there's no unhook-client in the input bar...
Dusty
Offline
huh? hooked? you lost me there
DaDeXTeR (Martin Lefebvre)
My screenshots on PicasaWeb
[img]http://imagegen.last.fm/dadexter/recenttracks/dadexter.gif[/img]
Offline
only its not working.... cause I have firefox hooked, and its focused... and there's no unhook-client in the input bar...
Dusty
hmmm gmail is down right now, but i asked the wmi-devel list about it... and the head developer responded with "it works fine for me, it only comes up when it's in the right context"
however I looked at the code... when a window is hooked, the it sets the value of the hooked property to the window's name, when it is unhooked it is set to "" - but the validation function for unhook-client only returns true if (client->hooked() == "")... which I don't think is right...
Offline
gmail is down?
that's bad... I thought I had felt a great disturbance in the force... that was it!!!
P.S.: I'm at work, bored and tired... and done in 5 minuites so you'll have to excuse me
DaDeXTeR (Martin Lefebvre)
My screenshots on PicasaWeb
[img]http://imagegen.last.fm/dadexter/recenttracks/dadexter.gif[/img]
Offline
when a window is hooked, the it sets the value of the hooked property to the window's name, when it is unhooked it is set to "" - but the validation function for unhook-client only returns true if (client->hooked() == "")... which I don't think is right...
yeah, validation is wrong... I changed it in the source to check... works perfect now...
Offline