[HEIHUAa]

No description provided.

[HEIHUAa]

I actually wrote this fix a few days ago, but forgot to post it.

[Jamextreme140]

Thanks for the fix, however the refactored safe navigation feature was reverted to prevent breaking scripts that assign values while using safe navigation.

The refactored featured will be used for the next version

[HEIHUAa]

Wait, did they actually cancel the changes today?

[HEIHUAa]

Thanks for the fix, however the refactored safe navigation feature was reverted to prevent breaking scripts that assign values while using safe navigation.

The refactored featured will be used for the next version

Okay

[Jamextreme140]

Wait, did they actually cancel the changes today?

Yeah, turns out many users had many errors on latest builds, specifically doing things like this: Framerate.instance?.visible = false;

I'm looking for keep it working since latest Haxe 5 preview allows you to assign values while using safe navigation

[HEIHUAa]

Wait, did they actually cancel the changes today?

Yeah, turns out many users had many errors on latest builds, specifically doing things like this: Framerate.instance?.visible = false;

I'm looking for keep it working since latest Haxe 5 preview allows you to assign values while using safe navigation

My fix actually covers the whole set of logic. Theoretically, this has been fixed as well. After checking, it just reduces the processing in this part.