Tags
Creators
Details
0.12.1+1.20.3
Compatibility
Changes
Additions
A new sizing method joins the owo-ui framework - Sizing.expand. It works mostly the same as Sizing.fill (and indeed identically in a few cases) with the important difference that it applies after all other sizing types and only takes into account the space that remains after all other components have been inflated according to their sizing.
Along with this, the new Components.spacer can be used to, for example, easily push two components to opposite ends of their parent
Changes
- The
OverlayContainerno longer closes itself when its child is clicked inbounds but doesn't consume the event. Further, it prevents the screen from closing when ESC is pressed and instead only closes itself and it consumes all scroll events to avoid scrolling through the overlay(#199) - owo-ui component trees inside one of the screen implementations provided by owo (
BaseOwoScreenandBaseOwoHandledScreen) can now process and consume ESC keypresses
Fixes
- Only the most specific tooltip at a given mouse pointer location is now rendered by an owo-ui tree, fixing overlapping tooltips in the config screen (#95) and preventing tooltips from showing on components that are hidden by an overlay (like a color picker)
EntityComponent.RenderablePlayerEntitynow correctly loads skins againBaseComponent.hoveredis now only set totruewhen the component is not obscured by another one (#199)- When moving around the handles of a color picker, which one is affected no longer depends on the cursor position but only on which one was clicked
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| owo-lib-0.12.1+1.20.3-sources.jar | Unknown | 438.27 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ccKDOlHs:9NFjhCIH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ccKDOlHs:9NFjhCIH"
}

