Can we PLEASE be able to LOCK Globals

@dan Can we please urgently get some means of locking down globals so that you don’t accidentally keep destroying all the work you have done over the last few hours because you inadvertently moved a component within a global?

This has happened to me three times today, and no UNDO does not help it makes it a lot worse by causing even more content to be lost. This is becoming increasingly frustrating and I have been dealing with it for a long time. I hate to think what is going to happen with new users.

Either there has to be a way to LOCK a component from being, accidentally moved, or when a user moves a component within a global they are given a warning that they might lose all the data as the component might be reset.

I’d be happy to start with a “positional lock” so a component cannot be moved, but its contents can still be edited if needed.

I firmly believe that something has to be done about this before a 1.00 release.

Globals are so amazing, but you have to be incredibly careful what you are doing otherwise you can easily destroy hours if not days worth of work.

3 Likes

Yep, I know how that is, I’ve done it myself more than a few times :grimacing:

Globals are such a powerful feature, and they can do so much, but I agree, it’s high-time we put in some guardrails!

1 Like

@dan As far as I’m concerned I could not do half the stuff I’m doing without Globals, they are literally one of the crown jewels of Elements. But they can be extremely frustrating and I worry about the impact that will have on new users, where they might not be able to realize the full potential.

I have had a lot of experience with them now but I still get caught out by them on an almost daily basis, where something accidently happens and a bunch of data goes missing. Or the most common error, forgetting to override a property and changing all of the globals.

I have given it a lot of thought trying to figure out how to make them safer and for now the ability lock certain properties seems to be the most flexible approach. It is also one I’m intmately familiar with as I use it on a daily basis in my graphics software for the same reasons. I understand that something like this might not be trivial to implement or add UI complexity, but in the long run it should make the software more usable.