BiasAlignment does not directly expose bias but probably should [328088992]

Fixed

Bug

Status Update

No update yet.

Description

go...@jakewharton.com

created issue #1

Mar 4, 2024 07:33PM

Given a `BiasAlignment`, `BiasAlignment.Horizontal`, or `BiasAlignment.Vertical` I cannot directly extract the float bias values. I can do it with the `data class`-generated `copy` function, but that is very annoying. This would help partially solve

issue 328086355

as I could compose `BiasAlignment.Vertical` and `BiasAlignment.Horizontal` into a `BiasAlignment` which I then supply to something wanting an `Alignment` (but it does not solve that issue in the general case, hence why I filed it separately.

The bias float value already comes in via the constructor and is exposed via `copy` and `component1()`/`component2()`, so why not make the named properties available directly, too?

Compose foundation 1.6.2

Comments

go...@jakewharton.com <go...@jakewharton.com> #2Mar 6, 2024 03:22AM

possible dup b/178240897

le...@google.com <le...@google.com> Mar 8, 2024 01:48PM

Reassigned to uo...@google.com.

go...@jakewharton.com <go...@jakewharton.com> #3Mar 8, 2024 02:34PM

Comment has been deleted.

Message last modified on Mar 8, 2024 02:34PM

ap...@google.com <ap...@google.com> #4Mar 8, 2024 03:44PM

Thanks.

Can you please elaborate on the first sentence?

I see this is because we just cannot really drag handle behind the screen (because the "pointer" of the handle is where we select the text, so the handle need to be out of the screen to select the last letter).

I did not understand dragging the handle behind the screen.

uo...@google.com <uo...@google.com> Apr 2, 2024 02:47AM

Marked as fixed.

Issue 328088992