listerCOMP lacking binding options

What I really miss with the listerCOMP is an easy way to bind to it with existing parameters.

If you think about it, a lister should easily be able to translate to a menu par, as long as the first item represents “None”.

This way its much easier to use the lister in junction with the existing parameter architecture.

I understand this doesn’t always make sense, for instance if you can select multiple items. But when allowing only a single item it makes a lot of sense to make it play nice with a menu par.

Besides the menu par, it could also be interesting to have a sequence block that is always in sync with the state of the lister.

It is a little bit hacky, but by binding to the menuIndex (instead of the parameter itself), you can actually archive this. You need to use the ( object, "nameOfAttibute" ) pattern to be able to do it though.