Download File

### Additions - Multiple tabs can now be selected simultaneously in a single OwoItemGroup (this behavior can be disabled for each group individually if not desired) - The new `panelWithInset(...)` surface allows building interfaces in the style of the Social Interactions screen - Sizing with different methods (for instance, content and fixed sizing) can now be animated between (there are no immediate API changes as a result of this, merely one less runtime warning and a new feature) - The base point (for layout calculations) and visual position (for rendering and interaction) of an owo-ui cmponent are now two separate concepts (this again comes without any breaking API changes, merely two new methods that should be called in the appropriate places) - Items can now automatically have their usage statistic tracked by owo through setting `OwoItemSettings#trackUsageStat()` - [Experimental] Screens can now implement the `DisposableScreen` interface if they need to be notified when the player actually closes all screens (that is, returns to the game) instead of immediately when navigating to a different screen (which might then later navigate back to the first screen) ### Changes - Methods on owo-ui components which accept a collection of components now use upper-bounded generics instead of an explicit type to allow more specific collections at the call site - `Sizing.fill()` can now be called with zero arguments to indicate 100% fill - `UIParsing.registerFactory(...)` can *and should* now be called with an indentifier instead of a plain string for the element name - `ParentComponent#childById(...)` is no longer @Nullable, as it is generally expected to return a component in its most common use-case (querying the constituents of a UI model) ### Fixes - Trimmed armor in an ItemComponent now renders properly (#152, Zailer43) - Explicitly positioned owo-ui components are no longer inflated twice for each single layout pass