Hi Ditto,

> I tried the sequence, and it all worked well for moving
> the objects, but history breaks when I edit the first curve.
> The mirrored curve updates, but not the scaled. I guess
> this is correct behavior, or did I something wrong?

Did you turn on history updates for the scaled curve? By default scaled objects do not have history updates turned on for them, so you have to turn it on by selecting the scaled result and running the Edit > History command and turning on "enable update".

Then with history updating enabled on that object, it should update when you edit the first curve, as long as you didn't do any other operations on it like try to move the scaled curve around.


The kind of tricky part about the history chain is that all the objects involved in the chain need to be currently present in the model for them to be updated. Moving an object is basically like deleting the current version of an object and replacing it with a different transformed version. That will work to edit the objects at the very start of the chain, to trigger an update but it won't work if you move some piece in the middle of the chain.


By the way, Flow is definitely high on the target list for v3...

- Michael

hi michael

is there a way to determine, whether a curve/object has "a history"?..right now, i can't spot any visual feedback or indicator. even if i call the history command, both buttons do look the same..

thank you,
marco

Hi Marco, there isn't anything in the UI to show it right now - in the future I definitely want to have something that would both show it and allow you to edit it like change parameters and stuff like that, but it's a pretty big area of work.

I think it could be possible to make a script that could be assigned to a keyboard shortcut that would pop up a message if the selected object had history data attached to it, would that be of any help right now?

Basically the history data is a chunk of text that stores the name of the command that was used to create the object and also a list of all the parameters that were used.

So that data will usually be present, even for stuff where there is not a way to edit it to update it currently.

- Michael

hi michael

ah, i see..

..an array must be something different than, because i can't get it to work with history. maybe(in future releases) there could be an option (pretty much alike the "make copies" button) to predefine the history-status of the "offsprings".

thanks,
marco

p.s. is it possible to embed iframes into a post?..

Hi Marco,

> ..an array must be something different than, because
> i can't get it to work with history. maybe(in future releases)

Yeah the history data is stripped on the output of Array, because there were some circumstances where having the data attached to each array output was increasing the size of files by quite a bit when arraying a large number of simple objects.

In the future I'd like to make that better - it may be better to store history data in some kind of centralized log of actions, rather than having attached data on every output object.

> there could be an option (pretty much alike the "make copies"
> button) to predefine the history-status of the "offsprings".

Yeah I've been thinking that there could be a setting in moi.ini where you could list commands that you wanted to have history updates turned on by default for.


> p.s. is it possible to embed iframes into a post?..

No, I think that the forum software strips those out since they are a potential security hazard.

- Michael