PatFisher asked me on IRC why I've decided to have the actions the way they are. This is for multiple reasons, and most of them are due to limitations in compiz itself.
* We can't have actions in multi-lists yet, because things like BCOP would freak out (And there is no way to point the action to a function if it is hot-added). I talked to onestone about this, perhaps we will be able to figure this out in compiz. * The other option would be having a huge mess of keybindings, which, I quite frankly don't want because enough of my keys are disabled already due to the growing number of plugins * Even if we were to have actions in multi-lists, it would still be a huge mess of keybindings, which, as outline, I don't want. * 'Next' and 'Previous' and 'Toggle' make sense because we can loop through a list and toggle on/off the ones we want (even if it is more inefficient). * Something I forgot to mention in the previous message, when having the actions for 'Next' and 'Previous', a small info box will appear on screen with the element movement pattern next to the texture selected. * There is nothing stopping us from adding a few 'Hot Bindings' for items 1-5 in the list, but, this is something I want to avoid. * There is also nothing stopping us from adding a DBUS action to call an item in the list matching a criteria. * Finally, there is nothing stopping us from having a checkbox next to each element and having a 'Toggle Checked' action (much like wizard). For those of you who might not understand, here is how the multi-list might look in CCSM --------------------------------------------------- | Element Type | Texture | | Snow | /path/to/tex1 | | Snow | /path/to/tex2 | | Stars | /path/to/tex3 | | Bubbles | /path/to/tex4 | --------------------------------------------------- -- Sam Spilsbury _______________________________________________ Dev mailing list [email protected] http://lists.compiz-fusion.org/mailman/listinfo/dev
