Friendlyskies AoI Forum

Thanks.

It is my first in the sense that it's my first AoI tool-script, that I made from scratch. But that did not come without some prior experiences and some very valuable help.

By documentation, I suppose, you mean a kind of a "user's manual" that shows some typical ways of using each feature? That crossed my mind too -- like explaining the concept of segments and "add one to end". But there are also a couple of other things that could still require attention. For one thing I'm fairly sure that one of the combinations with the object origin set onto the rotation axis will some day turn out to be impossible to solve and  I *think* I have come up with a safer solution to handle that, than what script is using now.

There are also a couple of interesting features, I believe I should have a look at.
- The copied object could be keyframed to follow the base object. (Think about 120 turbineblades keyframed manually...)
- "Include children". This is probably more tricky, but Nik pointed me some directions where to look, so maybe I should have a look.
- Harald suggested that the arrayaxis could be defined by an object. That certainly would be handy, but I don't know how to do that without exploding the dialoxbox (pop up another box maybe?)

Though I'm not sure how much more "professionalism" can be stuffed into a script UI before it's getting too slow to load...

Another thing: I tried to pick words that would best describe each function there, based on, what I have seen used on technical contexts, but if there's something, that seems to be from the wrong dictionary, please let me know. With the vocabulary of a very special field there always is the "fine line" somewhere...

Anyway, I'll keep my hands off it a couple of days now and then see what is to happen..

Thanks, I'll try that ... I managed to pick up an old book of mathematical formulas and found also another way of determining if vectors or lines are parallel. Though the dot product is probably easier as it's already programmed in there. The vectors are already normalized just for this very reason, so no damage done there.

One last point Pete: is this script getting to the point that we should consider converting it into a plugin?

Hehe... I was wondering that myself. It's not like the actual work that it does would be so heavy, it's more just the start-up-time because of the UI. But let's have a look at that project some time later...

Thanks.

I left the "real copies" option out for one thing, because there is no obvious need for the script to make copies of the objects. Such a reson could be for example variation of size. Also the user can quite easily change the instances into copied objects and decide himself on wich ones to perform the operation. I may think of adding the option at some later point though. (If not else, at least to unify the tool with the linear arraytool)

Your second idea sounds like the way to go. Why didn't I think of that?

No doubt, I'll sooner or later, get myself acquainted with the wonderful world of plug-ins, but all in good time. I've got Eclipse on my PC (not much used yet, but I for example managed to perform a small soundprocessing task by Java)... If I'm not mistaken Eclipse should help.....

Last edited by peteihis (September 24, 2008, 9:48 am)

Wow - I totally overlooked this one.
Now that I´m in need of it I found it!

Thanks!!

Do you think it might be worth changing it from a tool script to a scripted object?
That way it would be parametric and maybe animatable.

Greetings
Harald

Edit: No I didn´t overlook that one - but anyway - good to see it´s still "findable".
How about putting it in the script repository?

Last edited by Vidiot (August 28, 2009, 8:10 am)