I could reproduce the bug, just wrote a sample script. It's because of how JSDoc comments are handled.
This works, bug not present: cursor is before foo1 of static foo1 = function() {
This doesn't work, bug present: cursor is before foo1 of /// @func foo1()
Conclusion: When you use the real name of the static method variable in the JSDoc comment func the bug is present.
I'm sorry, I think we had talked past each other. I think you where talking about placing the text cursor somewhere in the code by yourself. But I where talking about how the outline view places the cursor in your code after selecting the function.
So you mean the outline view has two different functions where to place the cursor?
Then all this makes sense now! Also this underline works now. In the second picture which I posted, foo1() is now underlined instead to foo().
Thank you for the work!
Okay, so that’s a different thing - when navigating to a sub-region, GMEdit searches for the first mention of that name after the parent (in this case, function Test), and adding /// @func name also does make for a mention of the name, so it goes there instead. I’ll need to implement a slightly more complex solution for this.
On a side note, neither GMEdit nor GMS2.3 currently give any meaning to /// @func inside constructors. GMEdit will automatically pick up named arguments from functions static foo = function(a, b) for contextual completion, so sticking to that may suffice.
Upon some testing I regret to inform that in GMS2.3 IDE /// @func has no “context”, meaning that redefining the same function in different constructors will have them fight over what which version will be shown in auto-completion. @param may be more conventional for purposes of documentation generator.
