Equilibrier
commented
2 years ago A list should be made with multiple situations and how these are handled in the present, as many of them are still managed well. From that list on, we can work on to isolate the code and the mistakes, analyze the programatic model (if any..??!!) and see if the model has to be changed/defined or the changes can consist just by bug-fixes on the current implementation&model.
It's pretty confusing, one single example: sometimes, when you created a group of simple elements + other components, when you are pressing the create-component (from group) button, it creates a component with only the non-component sub-elements, and discarding the other elements. Also, it seems components can reside in the canvas (outside any screen) but also as an instance, so as type and as instance, and you do not know which is the case, and I think things can go wrong because of this status. Components should reside in the canvas only, and inside the screens, only instances should reside, and creating a component from some element which is on the screen, should create the type in the canvas, and also create an instance (instead of the type (model)) on the screen also, all of these automatically...
Other examples can continue, something must be done to get things more clear, more stable and more intuitive.