Releases: rafern/lazy-widgets
Releases · rafern/lazy-widgets
0.9.7: Expose more Slider properties
Changes
- Make more Slider fields protected instead of private to make sub-classes more powerful. Affected fields:
minValue
,maxValue
,snapIncrement
,keyboardFocused
,dragBounds
Fixes
- Fix unnecessary allocation when changing
dragBounds
value in Slider
0.9.6: Expose some Slider properties
Changes
- Make some Slider fields protected instead of private to make sub-classes more powerful. Affected fields:
offsetX
,offsetY
,actualWidth
,actualHeight
0.9.5: Hotfix
Fixes
- Fixed bad handling of images that are waiting to be loaded in Icon widgets
0.9.4: Hotfix
Fixes
- Fixed DOMRoot deactivation
- You no longer need to update the DOMRoot if it's deactivated for it to disappear
0.9.3: Hotfix
Fixes
- Fix crash when Icon's image has 0 width or height, caused by NaN values
0.9.2: Hotfix
Fixes
- Fixed dimension resolution for Icon widgets with Contain IconFit
- For example, if you have an Icon with a 128x128 image and a Contain IconFit, but the Icon has a maximum height of 32, the Icon will now resolve its ideal dimensions to 32x32 instead of 128x32
0.9.1: Typing fix
Fixes
- Fixed type of IconButton image argument (was
HTMLImageElement
, now isHTMLImageElement | HTMLVideoElement | string
)
0.9.0: Improved input system, specifically for mobile
Changes
- Revamp TextInputHandler system. Now supports:
- Input as you type (you don't need to submit changes for them to show up anymore)
- Synchronised text selection (whatever you select in the virtual keyboard is selected in the UI and vice-versa)
- Remove DefaultTextInputHandler. Replaced with SystemTextInputHandler:
- Provides a way to seamlessly use the system's virtual keyboard. Especially useful for mobile
- Can also be used in WebXR, however, it doesn't support initial text and text selections, so it's not recommended (tested on the Oculus Quest 2)
Fixes
- TextInput double/triple click now supported on mobile
touchAction
is now set dynamically, which means that you can now scroll the page on mobile if the pointer events were not capturedPointerWheelEvent.fromDrag
is not always false anymore; it will be true on mobile now- Fixed bad scroll prevention logic in ScrollableViewportWidget
- ScrollableViewportWidget scroll prevention is now done even when on mobile
- PointerDriver no longer incorrectly believes that an event was captured
0.8.11: Hotfix
Fixes
- Fix bug introduced in last version where text would be in the wrong place
0.8.10: Text alignment fix
Fixes
- Fixed non-wrapped text not respecting text alignment
- If you, for example, centered text that has wrapping enabled, it would work, but if it had wrapping disabled, it would not work