When moving components around of a screen type it now is saved immediately. Please change it how it was in the older versions where an active “Save” was required to confirm your changes.
When you now move a component and the result if the placement has an unintended result, your screen type is now ruined. Since the order of how you move component can be quite important to not completely mess up the already setup specification in width/height, a mistake can happen quite easily.
New
Make Screentype (design) changes require an active "Save" action
- Superhero
Hi Mark!
What about, instead of bringing back the save button, we introduce an undo (and redo) button? That way if a mistake happens you can simply undo it, while still keeping the advantages of autosave. For example, when you switch to the action bar tab to change something, you don't lose all your progress.
Fun fact: this kind of already works! The modeler we use has an undo function built in, so you can already use Ctrl+Z (undo) and Ctrl+Y (redo). That said, it's quite hidden right now, so we should definitely add it in the UI itself. Two catches though: it forgets your history when you switch tabs (like in the action bar example), and it does not undo deletion of a screen component.
- Superhero
Hi Joshua,
the CTRL + Z / CTRL + Y is quite a pleasant surprise. That would work. I can accept the limitation that one should not have swapped tabs, which is kinda similar to how it used to work.
My issue is mainly when dragging and it morphs into a completely annoying state, that you would like to undo. So the hotkey is a valid solution.
I would say you can close the idea then. Your suggestion for making the actions more visible is a regular improvement overall that might not need to be limited to this idea alone. Thanks a lot.
My issue is mainly when dragging and it morphs into a completely annoying state, that you would like to undo. So the hotkey is a valid solution.
Of course, this shouldn't happen in the first place (undo button or not). We're already aware of a bug where dragging a tab container into itself wipes out the entire container (which, with this new knowledge, you can fortunately undo). If you run into any other bugs with the screen type modeler, let us know!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.