Community
Participate
Working Groups
Created attachment 223873 [details] Simple example. During the time I have run different modelling, M2M and M2T tests using Papyrus I have suffered from mouse-elbow several times. There are way too many mouse-clicks to build models in Papyrus, compared with other more user-friendly modelling tools. The absolute minimum it takes to add one operation with one parameter of some type is 11 mouse-clicks, and to actually see the operation with its parameter in the diagram it takes an additional 5 mouse-clicks = 16 clicks. Then there is an additional absolute minimum number of 6 mouse-clicks to give the operation and its parameter a name, and an additional 6 mouse-clicks to define the parameter as a return parameter. Right here we are upto a minimum of 28 mouse-clicks for this simple modelling thing. :( ...then there is the additional X number of mouse-clicks to find all the menues and the additional Y number of mouse-clicks to learn how to do it. Some Papyrus engineering effort to make the UI more user-friendly is needed. (needed for senior engineers building Papyrus models)
Papyrus will be improved to reduce this point. I close the task which is not enough precise to be solve in its generality. However, do not hesitate to open new one on this subject with detailled suggestion you think might improve Papyrus to be more user-friendly according to you. Thanks.
A clafification in what way "Papyrus will be improved" regarding this user experience would be nice, and some preliminary roadmap.
I have indicated this bug as requested to be reopened in our internal backlog. I cannot reopen this one myself.
As Sebastien said, this bug is too generic to be reopened. We can't decide at which point is should be considered fixed. However, more specific sub-tasks could be added so that we could reopen this bug (And close it when all subtasks are fixed). Or it could be renamed to focus on Operations/Parameters creation, then reopened.
I will begin focusing on mouse-clickings soon. Then I can provide additional examples, besides parameters.
Depends on Bug 318606.
Reopened for sub-tasks