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
Feature overview
Name: Gui element returning an array
TL;DR: The gui module should allow for the return of an array of elements which will be looped over for styling,
Details
Allow for the return of an array, each value in the array should be a valid element, and checked to be valid, before being passed to the style callback. This array can then be returned to the caller, the caller should expect a table based on the element factory called.
Possible methods
Test for a table return type, then iterate over it with ipairs.
Additional context
Idea from #190 when returning an array was expected to be supported.
The text was updated successfully, but these errors were encountered:
Current opinion is that this should not be implimented because it encourages the creation of sibling frames/flows which should be separated into new functions. It also encourages creating elements in a loop without calling an element definition and complicates the logic and readability. There is one case where this could be useful which is when elements are added to a table and need to be accessed by the caller; however in this case it is better practice to name the elements, return the first common ancestor, then access them by name.
Feature overview
Name: Gui element returning an array
TL;DR: The gui module should allow for the return of an array of elements which will be looped over for styling,
Details
Allow for the return of an array, each value in the array should be a valid element, and checked to be valid, before being passed to the style callback. This array can then be returned to the caller, the caller should expect a table based on the element factory called.
Possible methods
Test for a table return type, then iterate over it with ipairs.
Additional context
Idea from #190 when returning an array was expected to be supported.
The text was updated successfully, but these errors were encountered: