Hi-
I have been playing with more z-order operations. I wrote the restack extension I posted about a while back, and have been adding features... first arbitrary angle reordering, then radial reorderring, and most recently, I have (in my version) added some more basic z-order functions, such as reverse the selected objects z-order, randomize the z-orders, and shift (rotate?) the z-orders.
All these options are making the single extension UI an ugly mess, as many of them have options that only apply to some of the choices. I am thinking of breaking it into three separate extensions. What is the policy for providing extensions like this? Currently I have it under Effects->Modify Path... but don't like that as it is really doesn't modify the paths, just changes the z-order. It seems more like the Object->Raise, Lower, Top, Bottom functions (though it always moves them to the top after adjusting the z-order).
I am considering registering these as Object->Change Z-order->*** and having XX separate extensions (or can I have XX menu entries in one extension?)
Right now I have: 1: Orthagonal (pick comparison point and 1 of 4 directions) 2: Arbitrary Angle (comparison point and angle slider) 3: Radial (comparison point and direction option-outward or inward) 4: Random (no options) 5: Reverse (no options) 6: Shift (+/- slider either in actual numbers or % of objects in the selection)
Are there guidelines for how to best to do this?
Thanks,
-Rob A>
On Tue, 12 Feb 2008 22:04:50 -0500 "Rob Antonishen" <rob.antonishen@...400...> wrote:
All these options are making the single extension UI an ugly mess, as many of them have options that only apply to some of the choices.
I think the .inx format supports tabs, I can't think which one I saw as an example, but `grep tab *inx` might find it.
In fact, attached it an .inx of mine that uses it, can't remember what it does to the mapping of the parameters though.
Not sure if that really solves your problem.. may depend on whether the script is told which tab is active, if it is you may be able to get something usable using that info. - repeat the params needed by each type of shuffle on each tab - ok from the users end anyway.
Thinking about it maybe a multiple menu item solution is best :-)
Cheers -Terry
On Feb 12, 2008 11:04 PM, Rob Antonishen <rob.antonishen@...400...> wrote:
All these options are making the single extension UI an ugly mess, as many of them have options that only apply to some of the choices. I am thinking of breaking it into three separate extensions. What is the policy for providing extensions like this? Currently I have it under Effects->Modify Path... but don't like that as it is really doesn't modify the paths, just changes the z-order.
Of course! I was just going to write you to not use it for this reason :) Feel free to add another submenu, e.g. "Z-order", for your extensions.
I am considering registering these as Object->Change Z-order->*** and having XX separate extensions (or can I have XX menu entries in one extension?)
No, you'll need to create at least separate .inx files for each one, althouth they can use the same py file with different params. Also for now, all extensions are to be in Effects menu, not Object - we may change that eventually but for now the only ones outside Effects are those in Help menu.
Is there a way to have a "hidden" parameter in an .inx file?
I'd like to have one py file, and pass it a parameter to reflect the inx file calling it so that the .py file can use it to determine which options to use...
For example, for any of the directional restacks, I want to allow the user to specify the anchor point, but for reversing the z-order, the anchor point is irrelevant.
-Rob A>
On Feb 13, 2008 4:25 PM, bulia byak <buliabyak@...400...> wrote:
No, you'll need to create at least separate .inx files for each one, althouth they can use the same py file with different params. Also for now, all extensions are to be in Effects menu, not Object - we may change that eventually but for now the only ones outside Effects are those in Help menu.
--
On Feb 20, 2008 1:42 AM, Rob Antonishen <rob.antonishen@...400...> wrote:
Is there a way to have a "hidden" parameter in an .inx file?
did you try to just add them to the command in <command> tag?
participants (3)
-
bulia byak
-
Rob Antonishen
-
Terry Brown