GitLab

settings: Handle empty settings

See merge request !333

Variant: Use proper pointer conversion between C and Rust

See merge request !334

layout: Improve press handling

See merge request !330

Release 1.9.0

See merge request !328

Makes it more similar to release handling, removes some redundant checks.

This makes it easier to integrate modifiers in the future.

Highlights:

- Fixed glib critical when switching layouts
- Fixed minor memory leaks when switching layouts
- Whenever the client supports it, text is sent as text instread of key presses
- New Polish language layout
- Fixed greek layout
- Better key locking
- Less leaks
- Tweaks in terminal layout
- Better emoji layout

Emoji: More choices

See merge request !324

text input: Disable erasing

See merge request !332

Erasing with zwp_text_input_v3 version 1 requires bytes, and bytes require get_surrounding_text. That, however, is optional. That's a mistake in protocol design.

Easiest to drop this until the mess is solved on the protocol side.

layouts: terminal: Use altline outline for dot key

See merge request !331

This prevents the buttons from jumping around when switching between views.

Center views relative to layout space

See merge request !326

terminal: Make */ easier to reach

See merge request !325

They exchanged positions with @%

layout: Improve scoping of locked variable

See merge request !329

Better accents in PL

See merge request !323

Update translations & greek

See merge request !315

Turn locking stateless

See merge request !322

Allocation problems

See merge request !327

Submit and delete strings via text_input

See merge request !304

gio::Settings::set_value takes over ownership of the Variant sometimes, but in other cases it doesn't. To prevent this being a problem, the custom Variant is made of the type that will never have its ownership taken.

This is not necessarily consistent with what gtk-rs authors intended.

In practice, the ownership is shared by refcounting, and after the Rust reference is dropped, one taken by Settings survives.

Locking is not determined by button state any more, but rather based on the view active at the moment. If pressing/locking a key results in the current view being active, the key is active. If locking a key results in the current view, the unlock view is activated.

Release 1.8.1

See merge request !321

layouts: Add Polish layouts

See merge request !318

- Landscape layout doesn't crash
- CSS font is actually taken into account
- Failed start due to dbus is now communicated
- Better log messages
- Fixed Enter in numbers layout
- More consistent terminal layout
- Proper font sizes in terminal layout

Update docs and CI builds

See merge request !320