GitLab

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.

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

build: Strip clap of optional features

See merge request !311

number: Fix keysym for Return

See merge request !310

debian: Add missing commas

See merge request !316

setup: Connect ui to the state manager

See merge request !319

This ensures that the layout type information is accessible to the state manager when new layout information arrive.

The should be thought of as a stopgap measure. A proper solution would be to separate the state properly, and probably turn layout information coming from random places into messages that some object (thread?) collects and displays.

layout: terminal: Replace actions button with period on symbols view

See merge request !317

Commit ab67bd2c took things a bit too
far and completely removed the period button.

layouts: Fix segfault on switching to wide

See merge request !312

font: Use font from style context

See merge request !313