I would change the storage type of the list item to a class, so the display string and the icon image URL would be seperate items. Then the UI can display as needed. I will have another property for the value. I guess I don't have a problem with an object property that the plugin could use as needed. I am just a little concerned about performance. This entire list object is serialized and deserialized over the channel between HS and the plugin. The more stuff we put in there the slower it will be, and use more memory. A list with 5000 tracks might take forever to pass. So I suggest keeping the data HS stores to a minimum:
* Display String
* Icon URL/Path
* Value as integer
All of the above will need to be passed to the HSTouch client and you will get back the value when something is selected. For multiple selections, SetIOMulti would be called with an array of all items selected (supports that already).
* Display String
* Icon URL/Path
* Value as integer
All of the above will need to be passed to the HSTouch client and you will get back the value when something is selected. For multiple selections, SetIOMulti would be called with an array of all items selected (supports that already).
Originally posted by pcp
View Post
Comment