You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
raygui was redesigned on v4.0 to always return an int as "control result value" while keeping the control required variables as function parameters, usually passed by reference.
Despite the redesign, there was no rule defining/unifying that "control result value" that should be returned by every control. Here some possible ideas (ref: #371):
Every control has to be carefully analized to see what are the possible internal states that could be returned. It would be nice to unify the possible return values but also allow per-control custom return values.
Note that some controls already return specific results, reviewing this functionality could be a breaking change:
GuiButton(): Returns 1 when clicked --> RESULT_CLICKED?
GuiTextBox(): Returns true when edited, used to change editMode
...
The text was updated successfully, but these errors were encountered:
raygui was redesigned on v4.0 to always return an
int
as "control result value" while keeping the control required variables as function parameters, usually passed by reference.Despite the redesign, there was no rule defining/unifying that "control result value" that should be returned by every control. Here some possible ideas (ref: #371):
Every control has to be carefully analized to see what are the possible internal states that could be returned. It would be nice to unify the possible return values but also allow per-control custom return values.
Note that some controls already return specific results, reviewing this functionality could be a breaking change:
GuiButton()
: Returns1
when clicked -->RESULT_CLICKED
?GuiTextBox()
: Returnstrue
when edited, used to changeeditMode
The text was updated successfully, but these errors were encountered: