João Pedro Braz

Not sure *why* but the issue seems to be with using `BrFileSelector>>#matchParent`, instead of `vExact` and `hExact`. That can be noted on the fact that this only happens with the...

Hi! @girba That just happened to me, here's a screenshot of Monitor:  When that happens alt-tabbing away from Glamorous Toolkit seems to fix it. Hope it helps!

The most recent PR (https://github.com/inxilpro/IntellijAlpine/pull/46) should fix that, while it's not merged you can refer to https://github.com/joao-pedro-braz/IntellijAlpine/releases/tag/v0.6.1 for an unsigned release.

Instead of _necessarily_ dealing with arrays, I think we could defer to only allocating one if the "spread" syntax is used, like: ```gdscript var [a_cool_variable, ...everything_else] = a_multiple_returning_function() ``` In...

@SlugFiller I guess there's two facets to this proposal: - De-structuring containers (Initially, Arrays) into variables - Having a heterogeneous type-safe container of elements Doing both simultaneously would indeed require...

I guess we could be conservative here and just add the de-structuring "operator" for Arrays, but since typed Arrays are homogeneously typed, the user would probably have to de-structure into...

I think we can make this work in a really nice way by implementing it in two "phases": 1. First one, we add the de-structuring syntax for arrays: - We...

@vnen Since this is on the roadmap, could you chime in?

Having the same issue, seems caused by a failure to compile the async function that validates the field

This might be closed if the discussion over at: https://github.com/godotengine/godot-proposals/issues/162 gets resolved.