On May 2, 2014, at 11:41 AM, Paul Miller <stelefx@gmail.com> wrote:
I'm using the new Buttons in FxPlug3, and one of my buttons ends up causing several parameter values to change. But the sequence of parameter update events is weird, and causes a different control to not function properly.
Say I have this:
[BUTTON] Slider 1 Slider 2 Slider 3
CheckBox [OFF] Slider 4 [Disabled]
When CheckBox is turned on I enable Slider 4, and disable it when CheckBox is turned off. Okay fine.
Now, I click BUTTON which causes Slider 1-3 to have new values stored in them. This is working.
Right after this, I click CheckBox, but instead of getting a user-changed-parameter message on the CheckBox, I get user-changed-parameter messages on Sliders 1-3.
So now CheckBox is ON but Slider 4 is still disabled, because I never got the changed message. If I now click CheckBox, then I get the proper message, and because CheckBox is now off again I disable Slider 4 (which is already disabled). At this point turning CheckBox on causes the proper update to come in.
Any ideas?
Paul, That definitely sounds wrong! Is this in FCPX, Motion, or both? Please file a bug on it. One possible solution would be to always check the status of the checkbox at the end of -parameterChanged: and enable/disable Slider 4 as necessary, regardless of which parameter changed. It’s kind of a sledgehammer approach, but might solve the issue until we can get a proper fix into the app. Darrin _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com