multi value list of appearances
If you know the name of that custom asset library, you can plug that in where I'm specifying '1' in the code below.
Dim oApAssetNames As New List(Of String)
oApAssets = ThisApplication.AssetLibraries.Item(1).AppearanceAssets
'oApAssets = ThisApplication.AssetLibraries.Item("AssetLibName").AppearanceAssets
For Each oApAsset As Asset In oApAssets
oApAssetNames.Add(oApAsset.DisplayName)
Next
Try
MultiValue.List("Appearances") = oApAssetNames
Catch
Dim UPs As UserParameters = ThisDoc.Document.ComponentDefinition.Parameters.UserParameters
UP = UPs.AddByValue("Appearances", "", UnitsTypeEnum.kTextUnits)
MultiValue.List("Appearances") = oApAssetNames
End TryWesley Crihfield
(Not an Autodesk Employee)
This is likely because of the iLogic snippet we are using, and its settings, but could also simply be because we did not actually set a Value to the parameter, after settings its list of available values. This is a factor. Here is a link to the settings for that iLogic snippet. (MultiValue.SetValueOptions and MultiValue.UpdateAfterChange). But as I said, we may simply need to set an actual Value to the parameter, not just its list of values.
Wesley Crihfield
(Not an Autodesk Employee)
Yep. When I add those two extra lines in there:
MultiValue.SetValueOptions(True)
MultiValue.UpdateAfterChange = Truejust before the Try...Catch block, that fixes the issue of the parameter not having a current value after setting the list of values to it. There is also an equivalent/alternative API method that could be used instead of that MultiValue iLogic only snippet. The UserParameter object has an ExpressionList property, which then has a SetExpressionList method that I often use. That has some similar settings too.
Wesley Crihfield
(Not an Autodesk Employee)
Well...those two settings lines are 'preparatory' type settings, which means they are best used 'before' you do something with the other MultiValue.List or MultiValue.SetList type calls. In my last note, I mentioned that I placed them just 'before' the Try...Catch block of code. Once those two settings are established, then when something happens later with a MultiValue call, those settings will dictate certain behavior of it, like setting a value to the parameter after setting its list, and updating the document after setting the list. I'm not sure simply moving those two lines to above the Try...Catch block will meet your needs or not, but it would be the simplest next step to try out.
Wesley Crihfield
(Not an Autodesk Employee)
I suppose we could try adding some extra checks in there to help make it more robust. I believe that it should throw an error if you specify an Index that is out of range, or a name that can't be found, when getting the specific AssetLibrary object, so we could put a Try...Catch around that, but most likely not needed if everything there is stable. We could also check the oApAssets.Count before the loop, then check the oApAssetNames.Count to make sure it is not zero before setting that list to the parameter. I'm not sure what else you may have going on with the 'SUPRESS_PAINT' though.
Wesley Crihfield
(Not an Autodesk Employee)
