issue with ScriptDialog.LoadSettings and radioConrols

Deadline
1

hi
i am using deadline 6.2.0.32
i have notice that using loadSettings on a dialog does not work correctly with radioConrols
what i have observed to be happening is that no matter what the value for the entry in the settings file the control will be selected
so what happens is that the last entry for that radiocontrol in the settings file always ends up selected

so for example if i have the following block in a submission script

scriptDialog.AddRow()
MyTestCtrl1 = scriptDialog.AddRadioControl( "TestCtrl1", "RadioControl", False, "TC1", "TestGroup", 50, -1)
MyTestCtrl1.ValueModified.connect(TestCtrl1Event)
MyTestCtrl2 = scriptDialog.AddRadioControl( "TestCtrl2", "RadioControl", True, "TC2", "TestGroup", 50, -1)
MyTestCtrl2.ValueModified.connect(TestCtrl2Event)
MyTestCtrl3 = scriptDialog.AddRadioControl( "TestCtrl3", "RadioControl", False, "TC3", "TestGroup", 50, -1)
MyTestCtrl3.ValueModified.connect(TestCtrl3Event)
scriptDialog.EndRow()

and later have …

myCtrls = ("TestCtrl1", "TestCtrl2", "TestCtrl3")
scriptDialog.SaveSettings( Path.Combine( GetDeadlineSettingsPath(), TestSettings.ini" ), myCtrls )

this will produce a TestSettings.ini containing the following

TestCtrl1=False
TestCtrl2=True
TestCtrl3=False

now this is all as i expect it the problem is when i try to load these settings with scriptDialog.LoadSettings( Path.Combine( GetDeadlineSettingsPath(), TestSettings.ini" ) , settings )

the behaviour i see is that the last entry (TestCtrl3) is always set as the active radiobutton regardless of the value of the key in the settings file - so no matter what the value of TestCtrl3 (True or False) the control gets set as the active seleciton for the radio button.

can you confirm this is not just happening for me?

cheers
mark

2

I’ve confirmed that this is a bug on our end; turns out we’re not converting the values from strings to a bool properly, which results in the behaviour you’re seeing.

I’ve logged the issue internally, we’ll try to get this fixed for the next release! In the meantime, you could try switching to using a Combo Box with entries for each option instead, to workaround this issue.

Cheers,
Jon