In-Game: `flexpanel_create_node()` element struct ignores `instanceVariables` values of the built-in variables

[tinkerer-red]

What Is The Bug?

Currently a flex panel create will completely reject all build in variables, even if they are reasonably safe setters, like sprite_index, image_blend, mask_index, etc. Bellow is the output log of the sample project, in which i set a bunch of built in variables to see which ones were allowed and which ones were not, attempting to trouble shoot why my dynamically made buttons were not rendering, it was because sprite_index was never actually applied.

::INPUT::
visible == 1
solid == 1
persistent == 1
depth == 123
layer == -123
direction == 123
friction == 123
gravity == 123
gravity_direction == 123
hspeed == 123
vspeed == 123
speed == 123
xstart == 123
ystart == 123
x == 123
y == 123
xprevious == 123
yprevious == 123
sprite_index == ref sprite GMLCompiler_Icon
sprite_width == 123
sprite_height == 123
sprite_xoffset == 123
sprite_yoffset == 123
image_alpha == 0.75
image_angle == 123
image_blend == 255
image_index == 123
image_number == 123
image_speed == 123
image_xscale == 0.12
image_yscale == 0.12
__sprite_index == ref sprite GMLCompiler_Icon

::RESULT::
visible == 1
solid == 0
persistent == 0
depth == 1
layer == ref layer 4
direction == 0
friction == 0
gravity == 0
gravity_direction == 270
hspeed == 0
vspeed == 0
speed == 0
xstart == 0
ystart == 0
x == 683
y == 384
xprevious == 0
yprevious == 0
sprite_index == ref sprite -1
sprite_width == 0
sprite_height == 0
sprite_xoffset == 0
sprite_yoffset == 0
image_alpha == 1
image_angle == 0
image_blend == 16777215
image_index == 0
image_number == 0
image_speed == 1
image_xscale == 1
image_yscale == 1
__sprite_index == ref sprite GMLCompiler_Icon

As you can see every single variable was ignored except for a single non-built in variable called __sprite_index

Expected Change

All variables should be accepted, unless they would break the engine like on_ui_layer, collision_space, alarm, and probably move of the movement and positioning's. How ever in those breaking cases, the runner should not silently refuse, it should either throw an error clearly denoting why this isnt allowed, or it should accept the reasonable ones.

Steps To Reproduce

see included project.

How reliably can you recreate this issue using your steps above?

Always

Which version(s) of GameMaker are you reporting this issue for?

2024.14.3 Monthly

Which platform(s) are you seeing the problem on?

Windows

Sample Package

https://api.gamemaker.io/api/github/downloads/6cf699c4-90c5-40f0-b99c-13b1d444e85b

[jackerley]

This is already fixed in 2024.14.4. You will need to modify your sample project as you are attempting to set instance variables that you are not permitted to set - depth, sprite_width,sprite_xoffset etc but once this is done you will get sprite_index == ref sprite GMLCompiler_Icon coming through on the ::RESULT:: struct

[tinkerer-red]

that works for me i expected many of such to not be definable, or would instantly be overwritten could we get documentation on these for anyone wondering in the future why sprite_width or similar does not work? More specifically any normally writable variables, which arent allowed in the struct? or will these simply throw an error message in the runner?

[gurpreetsinghmatharoo]

sprite_width is read-only. depth may not be writable here probably because of it being controlled by the layer.
Will add to docs.