topic Re: Bug: integer range vs. UI in Libraries & objects

Bug: integer range vs. UI

Sam Karli — Wed, 07 Feb 2018 22:31:42 GMT

Found today.

You can give possible values of an integer parameter with range statement, as well.

values "iBlaBla" range [iMin, iMax]

and when parameter selecting, this will give You the desired result, integer numbers from iMin to iMax

But for ui_infield this will not work, and makes obviously corrupted behavior.
For me, a complex, pictured, ui_infield showed up correctly, I could select stuff, but after clicking it the ui_infield jumped back to the first possible value. Note that on the parameter selector tab I could select all values for the parameter so the parameter side worked.

Tested only in AC18.

Re: Bug: integer range vs. UI

Piotr Dobrowolski — Thu, 08 Feb 2018 22:37:18 GMT

do a loop and use "put" on all the parameters prior values command where do a "get"
it will work in plain old parameters and ui.

Piotr

Re: Bug: integer range vs. UI

Sam Karli — Sat, 10 Feb 2018 20:20:16 GMT

Hi Piotr,
this is what I have done, and worked, so this is a good workaround. (On the other end, it took an hour of me to find the reason for not working, especially that on Parameters list stuff worked well.)