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
In the f2.0-dev branch we can see research.lua, which has a number of menu_xxx functions. This then goes out of the way to reimplement things like menu search. In general we have lots of menus that are simple one-offs, possibly but not always over a simple dynamic list. This is true even of the inventory, which is a 1d menu masquerading as a 2d one.
We will be introducing layers. Once that's done, we will have a powerful mechanism for redirecting input and building UI abstractions. But powerful doesn't mean simple. What a lot of code wants is up/down/left/right/a few variations on click. If we then add some functions (I think around 3) to allow search to iterate in a relevant order, we can standardize all our menu code. While one would for now still be writing their own position movement code, that's fine: it's still an improvement, and an improvement we can build better things on top of such as completely static menus that call specific functions with specific labels.
The text was updated successfully, but these errors were encountered:
ahicks92
added
the
ui2
Large improvements to the UI and input systems for efficiency of long-term players
label
Oct 31, 2024
In the f2.0-dev branch we can see research.lua, which has a number of menu_xxx functions. This then goes out of the way to reimplement things like menu search. In general we have lots of menus that are simple one-offs, possibly but not always over a simple dynamic list. This is true even of the inventory, which is a 1d menu masquerading as a 2d one.
We will be introducing layers. Once that's done, we will have a powerful mechanism for redirecting input and building UI abstractions. But powerful doesn't mean simple. What a lot of code wants is up/down/left/right/a few variations on click. If we then add some functions (I think around 3) to allow search to iterate in a relevant order, we can standardize all our menu code. While one would for now still be writing their own position movement code, that's fine: it's still an improvement, and an improvement we can build better things on top of such as completely static menus that call specific functions with specific labels.
The text was updated successfully, but these errors were encountered: