On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Terrific!


I hope you don't mind me asking another question:

In o_player2's create event, I have a struct called CAnimator. I've also added '/// @interface {o_player2}' at the beginning of this event.
In a separate script, there's a struct named AGreatStruct that implements this interface. This struct also contains a variable named 'parent', which is a reference to o_player2.
All methods and constructor within this struct successfully auto-complete CAnimator.properties.
Using 'with(o_player2) { //code }' properly changes the scope to o_player2 without requiring the interface implementation.
However, using 'with(parent) { }' disrupts the scope of the implemented interface, and I'm unable to make 'with()' recognize that the parent is an o_player2 instance.
I've attempted to use 'var theParent : o_player2 = o_player2' and pass it to 'with()', but it made no difference.

Is there a workaround for this issue or a way to modify the behavior of 'with()' in this context?


Note: I've tried some different iterations of this struct, _parent was previous set to parent and run in a method that was in the struct etc, but no difference.



(+1)

Fixed that for the next release as well (well, mostly).

If you have enabled “warn about missing fields”, you’ll get warning about typos when saving, but auto-completion is a bunch dumber since it has to quickly find what you are trying to access - it’s generally not cheap to back-track through the whole file whenever the user presses .