traverso-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Traverso-devel] Delegating keyfacts to other objects


From: Remon
Subject: [Traverso-devel] Delegating keyfacts to other objects
Date: Thu, 22 Mar 2007 16:45:16 +0100
User-agent: KMail/1.9.6

Hi list,

One can delegate a keyfact to another object now, only works for keyfacts that 
call a slot, not for plugins.

Example keymap entry (omitted non-relevant parameters):

<Object objectname="AudioClip" slotsignature="mute"  />


The keyfact, not shown here will call mute if AudioClip was under the mouse.
Now,  I don't want AudioClip::mute to be called, but say, Track::mute.
You can do so by:

<Object objectname="AudioClip" slotsignature="Track::mute"  />

Obviously, the object Track needs to be under the mouse as well, and slot mute 
has to exist for Track. (lol, what about using Track::solo, imagine how 
confusing that would be ...)

A special objectname is reserved for hold type of actions:

<Object objectname="HoldCommand" 
slotsignature="Interface::show_context_menu" />

When a hold action is active, the keymap is _always_ searched for 
objectname  "HoldCommand", so delegating a key fact to some other object for 
a hold command works for _all_ hold commands, no need to define for each and 
every hold command....


Hopefully you got that ;-)

Regards,

Remon





reply via email to

[Prev in Thread] Current Thread [Next in Thread]