Status Update
No update yet.
Comments
da...@google.com
possible dup
da...@google.com
coming back to this issue. 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).
That being said, if being super careful I'm able to select the whole first word even with no padding (sometimes takes a few attempts).
Siyamed, how do you deal with this in the platform text? Frankly, I expect no text to be at the very edge of the screen in the real apps, and since it's possible to select by just raising the selection handle higher (positionning at the line above seelcted the whole line) idk how big the problem is.
Anyway, reassigning to Siyamed to investigate the selection in the platform for clues or ask someone from the text team to do it.
da...@google.com
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.
ap...@google.com
In the Gmail app for example (see image) the selection handle will get clipped to accommodate the selection, which is unlike what is happening here (see second image).
ap...@google.com
Can you please elaborate on the first sentence?
to Siyamed: Sure. This is basically what exploringbinary showed in their screenshots. the start handle selects the text based on its top right corner (where the sharp pointer edge is), so in order to select the text near the edge of the screen we have to essentially drag the handle out of screen bounds, so it's top right corner is at 0 x axis. I recommend to explore how we handle this case in the platform.
re screenshots: interestingly enough, your screenshots have a margin for a gmail, that's why it's possible. I assume we can clip the handle as well, but it won't help to solve the
da...@google.com
na...@google.com
got it thanks.
Description
API checks and Java ecosystem recommends SQLiteConnection and SQLiteStatement to implement Closeable / AutoCloseable but there is no KMP common Closeable interface. Other art work has defined a expect Closeable in commonMain and have actual typealias to Java's interface and implemented utility function in native.
It would be also nice if we can add finalizers to close things and warn about leaks. JVM and Android has finalizer APIs (https://docs.oracle.com/javase/9/docs/api/java/lang/ref/Cleaner.html ) along with the soon-to-be-deprecated https://kotlinlang.org/docs/java-interop.html#finalize ) and in iOS there is https://kotlinlang.org/docs/native-ios-integration.html#deinitializers ). But I don't think there is anything available for native...
finalize()(deinit(