Procedure: - Create a new blank composition.- Create an Input Splitter. Set type to Number, and publish the output. - Create a Feedback patch. Set the "Initial [published-output- name]" to 42.- Save, close the composition, and reopen it.At this point, the Feedback patch no longer has an "Initial [published-output-name]" input port --- it's instead called just "[published-output-name]", and its value is zero (not 42). I've confirmed similar behavior when the published output is of type String, Boolean, or Index.
The name change is probably a typo (UI bug, but not of any interesting consequence). The key name stays unchanged ("initial_[port name]"). However, it doesn't seem to save/restore these ports' states, they're always 0/false/"", etc when reloaded (even with inputInitialize set to True).
I can get around this by placing another Input Splitter connected into the Initial Value, but this seems somewhat baroque.
This fixes the issue because the splitter does save/restore input port states correctly, thus working around the Feedback patch's apparent inability to save/restore state correctly.
Is it correct to expect the Initial Value to be preserved?
I would expect it to, personally, otherwise it serves no purpose.Strolling through the plist, it appears as though the patch actually _does_ save state correctly, so perhaps it's a state restoration problem?
-- [ christopher wright ] [email protected] http://kineme.net/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
