Correct. However I am not talking about choosing it from the dropdown initially.The task of changing the patch instrument from another bank can only be done with a bank select message, followed by a prog change when it comes to working with the a-fluidsynth plugin.
True though, what you said about the “patch selector”, I can choose the distant patch instrument from there… but that’s called cheating because it is the plugin window that always wins for the details as is in the majority of cases.
… you’re wrong on the pulldown back on the a-fluidsynth interface however – it cannot be updated to reflect the current patch bank as that’s what the pulldown is supposed to represent.
–> A field item that has been set indirectly by sound bank+prog change messages need to reflect a new combo pulldown list for that newly “set” item.
–> That item is a member(patch instrument name) of a sound bank that needs to be reflected into its appropriate combo-pulldown list.
^ And the a-fluidsynth plugin fails to do just that.
No user interface on any operating system has a bug like this —> When the user clicks on that newly set item, the combo list does not reveal it as a member.
^ this is aweful and is rather quite user-suicidal.
It basically is like telling the user if they have a form with two name fields for first-name and last-name, that you need to open another Window because Window#1 cannot let you type one of the name fields. This is exactly what it’s doing.
This is not an aesthetic issue and it rather concerns function-purpose.
Never mind about the patch-selector, I already know about that… but thanks for reminding me about it…
please reconsider this from the perspective of the user…