Needs Updating for RX 10.3
Some of the buttons have changed again.
children
are now buttons
For example:
RX 10.2:
compositeViewBtn = sf.ui.izotope.mainWindow.children.whoseDescription.is('Composite View').first;
RX 10.3
compositeViewBtn = sf.ui.izotope.mainWindow.buttons.whoseDescription.is("Composite View").first;
These applies to multiple main window buttons
- SSoundFlow Bot @soundflowbot
Thanks for posting a question or an issue related to the 'Dialog Editing iZotope' package.
This package is made by @chrscheuer. We're auto-tagging them here so that they will hopefully be able to help you.Please note, that the best way to get help with a script, macro or other content installed from the Store is to select the script you installed, then click the red Need help button, and then click "Get help with this script or macro".
By using this workflow, the developer of the package will get access to more information so they'll be able to help you quicker.
You can read more about how to best get help in this article: bit.ly/sfscripthelp - In reply toMatt_Friedman⬆:Christian Scheuer @chrscheuer2023-01-25 02:05:50.207Z
Hi Matt,
Are you seeing things fail? Please note that as long as you're looking for a button, both pieces of code above would find the same element, so one is not necessarily more correct than the other.
- MIn reply toMatt_Friedman⬆:Matt Friedman @Matt_Friedman
Yes it's failing (silently). I used the Picker to find the script for the buttons that are in RX 10.3. The updated script I got from the picker works in 10.3, while the older code in the current release is not working.
Christian Scheuer @chrscheuer2023-01-26 20:55:44.561Z
Thank you, Matt. I've published a new version now with your fix.
I see now the problem is unfortunately that RX has a bug in how it handles responding to Accessibility requests for one of the elements in its UI. By choosing to limit to searching for buttons, the request completes successfully, but when searching through all children, it appears iZotope RX times out in handling the request, which causes the failure.
Hopefully we can get in touch with iZotope to tell them they're not implementing the Accessibility API correctly, causing these issues.
- SIn reply toMatt_Friedman⬆:SoundFlow Bot @soundflowbot
This issue is now tracked internally by SoundFlow as SF-748