Niklas Fiekas

Generally I agree that having `LV_EM(...)` would be awesome. For this use case it might be awkward to use. I think line height is not nescessarily 1 em, and there's...

Yes, still very much interested. It's tricky, though ... I don't think `LV_EM(...)` should automatically include line spacing. That would be unexpected, because: * It differs from the usual meaning...

How about these steps? 1. Let label respect max height. 2. Introduce new units LV_EM (and maybe LV_LH). 3. Introduce line height style property that behaves like line-height in CSS....

The 10 into 1:1:1 example was working even before. That's because each iteration of the loop only looks at the remaining `grow_max_size` and `grow_value_sum`. `grow_max_size` | `grow_value` | `grow_value_sum` |...

Rebased to fix conflicts again.

Added a lint to find mismatches in punctuation (ddd4ab74990cb3e010066458a559ec082146201a). We can exclude more languages or downgrade to notice, if it's too noisy.

Hi, the binary FEN format would be a welcome addition. I think it strikes a great balance between simplicity, size and performance, and Stockfish developers are already using it as...

Implemented the former via `PackedSetup`.

Ah, looks like it's pretty mixed indeed. prop | pointer lifetime --- | --- label_text | owned dropdown_text | **widget** dropdown_options | owned dropdown_symbol | **widget** roller_options | owned textarea_text...

Thanks for drafting this. Seeing it, and thinking about nested variations, there's no `variation_varation_san()`, `variation_variation_varation_san()`, ..., so the distinction between `san()` and `variation_san()` feels a bit arbitrary. Or in other...