on load no global variable exist
element with visibility set to "get_var '$myvar' " were previously not showing
now since b5269 and in 5281
these elements will show
the opposite
element with visibility set to "not get_var '$myvar' " were previously showing
now since b5269 and in 5281
these elements won't show anymore
if the variable exists hopefully everything is still the same as needed
it look like the get_var verb change its working mode
Many skins now initially show wrongly and buttons / elements / textzone have to use a function affecting the variable in a way to reflect actual real status
how to update such thing ?
element with visibility set to "get_var '$myvar' " were previously not showing
now since b5269 and in 5281
these elements will show
the opposite
element with visibility set to "not get_var '$myvar' " were previously showing
now since b5269 and in 5281
these elements won't show anymore
if the variable exists hopefully everything is still the same as needed
it look like the get_var verb change its working mode
Many skins now initially show wrongly and buttons / elements / textzone have to use a function affecting the variable in a way to reflect actual real status
how to update such thing ?
Posté Mon 16 Sep 19 @ 5:32 pm
Not only get_var was altered, in b5281
affect the value of a slider to a variable does not seems to work anymore the same way
i.e. action="set '$myvar'" was working fine now does not
this affect some skins, some pads, and other scripts
i.e. in pad : pressure="set '$myvar'" does set $myvar to 1 and slider is fixed to 100%
whenever pad_pressure_switch is set to on or off
was previously affecting the value of the slider to the variable and the slider was updated
affect the value of a slider to a variable does not seems to work anymore the same way
i.e. action="set '$myvar'" was working fine now does not
this affect some skins, some pads, and other scripts
i.e. in pad : pressure="set '$myvar'" does set $myvar to 1 and slider is fixed to 100%
whenever pad_pressure_switch is set to on or off
was previously affecting the value of the slider to the variable and the slider was updated
Posté Tue 17 Sep 19 @ 5:06 am
Tried on custom button and custom slider, but behaviour still seems the same.
Which skin are you seeing this problem with?
Which skin are you seeing this problem with?
Posté Thu 19 Sep 19 @ 1:03 pm
I tried on custom button and custom slider, behaviour still seems have change
Which skin ? mine ^^ default skin with extent working for years,
Which pad page ? Mine and some Locodog's ones
the best way to figureout what went wrong :
custom slider : set testvar
was working well, slider was following variable value
now variable is affected as wanted and slider is stuck to 100%
Which skin ? mine ^^ default skin with extent working for years,
Which pad page ? Mine and some Locodog's ones
the best way to figureout what went wrong :
custom slider : set testvar
was working well, slider was following variable value
now variable is affected as wanted and slider is stuck to 100%
Posté Thu 19 Sep 19 @ 2:22 pm
Problem with set found, will be fixed soon.
Posté Thu 19 Sep 19 @ 2:38 pm
thanks !!
Posté Thu 19 Sep 19 @ 2:43 pm
I did not find a difference in behavior with get_var though
Posté Thu 19 Sep 19 @ 2:43 pm
yes there is, look like it is related
when tested variable does not already exist yet get_var actually does not return 0 anymore but not 1 and no text
i.e. local variable used for visibility in a skin with a toggle button
it looks to me like - maybe- it returns a pointer to null / empty string and would maybe return 'nan' or other string instead of the old 0
this one is not critical and force to cleaner script
worked around all of these by a simple comparison with the value it would take
when tested variable does not already exist yet get_var actually does not return 0 anymore but not 1 and no text
i.e. local variable used for visibility in a skin with a toggle button
it looks to me like - maybe- it returns a pointer to null / empty string and would maybe return 'nan' or other string instead of the old 0
this one is not critical and force to cleaner script
worked around all of these by a simple comparison with the value it would take
Posté Thu 19 Sep 19 @ 3:01 pm
still present in VDJ2020 b5308 :(
Posté Tue 24 Sep 19 @ 1:42 am
more info about set and get_var problem - with b5803 - b5281 was acting differently
for a custom slider :
"set testvar" goes on not working anymore, slider visual does not get updated
"set testvar && get_var testvar" fixes it in 32bit version
but this does not work with 64bit version
"set testvar & param_cast" - or any other "& param_equal" like - will fix it for 64bit version
but this do not work with b5308 32bit version
mixed version
"set testvar && get_var testvar && param_cast float"
seems to work in both b5803 32bits & 64bit versions for now
for a custom slider :
"set testvar" goes on not working anymore, slider visual does not get updated
"set testvar && get_var testvar" fixes it in 32bit version
but this does not work with 64bit version
"set testvar & param_cast" - or any other "& param_equal" like - will fix it for 64bit version
but this do not work with b5308 32bit version
mixed version
"set testvar && get_var testvar && param_cast float"
seems to work in both b5803 32bits & 64bit versions for now
Posté Sat 28 Sep 19 @ 2:47 am
Thanks, fixed in b5350
it's somehow working back again
There is still an issue with mouse roller which sets the variable to +/-0.03125 instead of acting relative as for any slider
it's somehow working back again
There is still an issue with mouse roller which sets the variable to +/-0.03125 instead of acting relative as for any slider
Posté Wed 16 Oct 19 @ 7:26 am
Ah yes will fix relative values too
Posté Wed 16 Oct 19 @ 8:11 am
Fine, with the fix "set not receiving relative values" now set receives the relative value
result can be 0..100% in absolute
but still not stay in range 0%..100% when relative
result can be 0..100% in absolute
but still not stay in range 0%..100% when relative
Posté Wed 06 Nov 19 @ 12:30 pm
What script did you use exactly?
Posté Wed 06 Nov 19 @ 2:27 pm