When you add a property to a class you are given the option to set it’s scope to Public, Private or Protected.
Why can’t that there be another pull down to set it to be computed or static?
I know that you can right click on it later and convert it to a computed property but… Just thought this would be more convenient.
I would file a feature request in FB. I’d give this some points.
Why not just add it as a computed property in the first place?
I am ok with that if the default is static. But what will happen to those 40 lines of get/set methods when you switch from computed to static for accident, and the Default static value when switching to computed, just remove ? And when switching back, restart the values blank again?
That’s what + Z is for.
If you notice in time. 
Some could prefer something like “keep those values hidden behind the scene e recall them as necessary”.
[quote=191787:@Rick Araujo]
Some could prefer something like “keep those values hidden behind the scene e recall them as necessary”.[/quote]
Which leads to “why the heck does the IDE use so much memory?”
Keeping the history record for all those Undos in memory plus all the project contents?
Nothings free 