the inspector can be a handy way to reference one script while working on another.
There are times I'm doing this and realize I need to make a quick edit to the script I'm referencing in the inspector, which requires I go open the script, navigate to the line I was looking at, make the change, then return to the script I'm working on. It breaks flow.
Describe the solution you'd like
Consider adding a "Read-only" checkbox above/at the top of the script in the inspector. It would be checked by default. To make a change, simply un-check the "read-only" checkbox and make the change. I can imagine "read-only" re-ticking when the inspector changes focus to a different asset.
Describe alternatives you've considered
It also may be a helpful alternative for the "Open Editor" button to auto-scroll to the same top line that's in view in the inspector, so longer scripts don't require finding the area you were looking at in the inspector.
Is your feature request related to a problem?
the inspector can be a handy way to reference one script while working on another. There are times I'm doing this and realize I need to make a quick edit to the script I'm referencing in the inspector, which requires I go open the script, navigate to the line I was looking at, make the change, then return to the script I'm working on. It breaks flow.
Describe the solution you'd like
Consider adding a "Read-only" checkbox above/at the top of the script in the inspector. It would be checked by default. To make a change, simply un-check the "read-only" checkbox and make the change. I can imagine "read-only" re-ticking when the inspector changes focus to a different asset.
Describe alternatives you've considered
It also may be a helpful alternative for the "Open Editor" button to auto-scroll to the same top line that's in view in the inspector, so longer scripts don't require finding the area you were looking at in the inspector.
Additional context
No response