combo control

Deadline
1

Hello guys, I am migrating a script from Deadline 5 to Deadline 6.1 and I am having an issue with a combo box. I have looked through the docs, but could not find the help I was looking for. I was hoping to find a list of controls that are used with some definition, but most of the examples are in very basic scripts that do not always provide an in depth explanation or an extended/advanced use. (Which would be great) :wink:

I have a combo box which I need to populate with keys from a dictionary. In Deadline 5, it is written like this:

blobList = { “blob 1”: “C:\desktop\blob1.exe”, “blob 2”: "C:\desktop\blob2.exe, “blob 3”: “C:\desktop\blob3.exe” }
theVersion = “2.1.0”

scriptDialog.AddRow()
theArray = blobList.keys()
theArray.sort()
theString = ‘,’.join( str( i ) for i in theArray )
theCmndCode = StringUtils.FromCommaSeparatedString( theString, False )
Command = scriptDialog.AddComboControl( "blobList ", “ComboControl”, theVersion, ( theCmndCode ), 150, -1 )
Command.ValueModified += CommandChanged
scriptDialog.SetEnabled( “theList”, False )
scriptDialog.EndRow()

but in Deadline 6 when I have changed the code in line with what is available in the documentation, it does not work

blobList = { “blob 1”: “C:\desktop\blob1.exe”, “blob 2”: "C:\desktop\blob2.exe, “blob 3”: “C:\desktop\blob3.exe” }
theVersion = “2.1.0”

scriptDialog.AddRow()
theArray = blobList.keys()
theArray.sort()
theString = ‘,’.join( str( i ) for i in theArray )
theCmndCode = StringUtils.FromCommaSeparatedString( theString, False )
Command = scriptDialog.AddComboControl( "blobList ", “ComboControl”, theVersion, ( theCmndCode ), 150, -1 )
Command.ValueModified.connect( CommandChanged )
scriptDialog.SetEnabled( “theList”, False )
scriptDialog.EndRow()

The example script only shows putting a string list in as the items for the drop down (comboControl) but our code does create an array of the dictionary keys, which should work. examplescript snippet:

scriptDialog.AddComboControl( “ComboBox”, “ComboControl”, “2008”, ( “2007”, “2008”, “2009”, “2010”, “2011” ), dialogWidth - labelWidth - 24 - 200, -1 )

Any pointers welcome.

Also, if I have missed something in the docs, please point me towards it. Its going to be one of those fundamental things I have overlooked in the script. :mrgreen:

many thanks.

2

so it seems that there is some issue with the StringUtils.FromCommaSeparatedString part so I instead of this:
PhatCode = StringUtils.FromCommaSeparatedString( PhatString, False)

I used this:
PhatCode = PhatString.split(",")

and it worked fine.

I have been told there is updated documentation coming, but not till Deadline 7. I hope that is incorrect as it can be a little cumbersome writing code using the current documentation and example scripts.

3

We can see what is possible for documentation before 7, but I am told it will be a big task to do and there may be even more changes coming in 7.

4

I am unsure what is meant by that, it does not seem to be helpful. Unless I have missed the point of what you are saying. I just feel that the documentation should be up to standard and accurate. It should not matter that its a big task, the documentation MUST represent the version studios are working with. Omissions and missing information is no help at all. It is not enough to be told that the documentation for a current release is on the way as by the time it gets here, Deadline 7 will be available and its not known if we will go straight to that version.

While it is clear that a lot of development work is being spearheaded by the team, the end user will not always be aware of the changes required and having to second guess documentation is not progressive and slows down migration.

As with all the previous scripts I have changed, I guess I will have to rely on the forum, but, with only a small percentage of responses being valid, TDs have to keep plugging away until its working.
The webinar vids are good to watch, but again, offer little in the way of education in being able to update scripts. At the time of the webinar, the issue of documentation was raised, but nothing seems to have been moved forward much.

I am sure as well, that the team are working on this and I hope that updates will be forthcoming in the shortest time possible

5

Hello,

I totally agree with you, we need to have better documentation for all level of user, in order t make the programming lives of our customers easier. I am going to keep pushing this higher in order to make every effort to facilitate the improvement of our documentation. Thank you for explaining your viewpoint so well.

6

Is there any update on the documentation as I am still confused by a lot of the information, (and lack of in depth examples) and having to jump between pages for information that does not fully support user level interaction. I keep getting linked to Deadline 5 documentation when I am looking for deadline 6 information and periodically when looking at deadline 6 pages, it is referring to deadline 5. I originally posted back in June and there does not appear to be any movement on this and as Deadline 7 is approaching, can we expect a better set of documentation across the board, not just for the new release?

I do not feel that a script UI example is enough when a real scenario is what would help new users understand how to make it work beyond just being able to create a ui that has no ability.

Regards

7

Deadline 7 will be moving to a completely new documentation site which is in progress. this will make it easier to maintain, update and should [we hope] greatly improve client access.

cb