Replies: 2 comments 1 reply
-
Hey there, thanks for this discussion board. That interface is not as easy to understand as you hoped it will be. On 2.3.0 it was WAY easier to understand: add a binding on the left, name it, then choose the trigger and the wanted actions on the right. That was perfect (at least for me). The only change this needs is the ability to group bindings in nameable folders so you don't have to scroll that much if you add a new one - and you could have a better oversight what's configured where. Now on 3.0.0 things start getting overcomplicated. On 2.3.0 all depends on the given binding, now you divided binding, message and action to different fields. I can't imagine a situation where i would say "oh, ok, lets switch that action to another binding" or "i wish, i could give that assignment a name". But ok, i think after a while we can handle that. But now for my recommendations/ideas:
Beside that i have some technical issues, i'll adress them on another post. Finally: thank you for your great plugin, i really appreciate your work and your try to improve it further! |
Beta Was this translation helpful? Give feedback.
-
This discussion is being closed due to the implementation of the issue in question in version 3.0.0. Thanks for your help! |
Beta Was this translation helpful? Give feedback.
-
Please post here about any ideas or recommendations concerning the new user interface for the upcoming 3.0.0 release. Try to answer questions like:
Disclaimer: Not all suggestions will be included. But I would like to know what the users of the plugin want it to look like, so don't be afraid to voice your opinion.
Beta Was this translation helpful? Give feedback.
All reactions