Blueprint object references - [merged]

[benloh]

Merges dev-bl/next-gui-sansagent -> dev-next-gui

To simplify references to objects, you can now always refer to the current blueprint by the blueprint name. It is no longer necessary to choose between "agent" and "BlueprintName" depending on context. (Prior to this, the blueprint name could only be used within a when block).

For example, this is now VALID EVERYWHERE:

prop Fish.energyLevel setTo 5
featProp Fish.Physics.scale setTo 1.5
featCall Fish.Costume setCostume 'fish.json' 0
when Fish touches Algae [[
  featCall Fish.Costume setGlow 0.5
]]

...and, this is still valid, but not necessary:

prop agent.energyLevel setTo 5
featProp agent.Physics.scale setTo 1.5
featCall agent.Costume setCostume 'fish.json' 0
when Fish touches Algae [[
  featCall Fish.Costume setGlow 0.5
]]

In addition, "agent" is now considered an advanced symbol in the GUI, so it appears faded:

[benloh]

requested review from @jdanish

[benloh]

added 2 commits

• db3eb04e - next-gui-statefix: ScriptEditor should still stay on blueprint script if the...
• 2c7108e3 - next-gui-statefix: Remove bpname change handler for script_text. Only script_tokens needs it

Compare with previous version

[benloh]

In GitLab by @jdanish on Jul 26, 2022, 04:37

Looks good!! Thanks!

[benloh]

mentioned in commit d32781f803a1505199461fdc5503d960012cc4a3