Brian Yencho

Programmer / Scientist / Occasional Artist

[Brian Yencho @brianyencho]

Lies, Damn Lies, And Semantic Versioning

https://t.co/JsfbweQuOd

[TC Hack @tchacknight]

Some are calling it the fireworks before the 4th of July fireworks. You'll just have to come see for yourself!

The next TC Hack is this Wednesday (7/3). Cruise into your holiday with great company, cold libations, and hot pizza. See you there! #Meetup
https://t.co/D8bH0xMI5I

[TC Hack @tchacknight]

Special TC Hack collab this month! We're teaming up with @TCKotlin to host a watch party of the Kotlin Multiplatform Global Event, which is celebrating KMP transitioning from Beta to Stable!

This Wed night at Smart Factory from 6-8pm. Sign up link in thread. #kotlin #meetup

[Accesibilidad del software @software_a11y]

Talkback Ordering in Android Jetpack Compose. By Lucas Kivi.
https://t.co/qzhFsYzFLj
#a11y #mobile

[Brian Yencho @brianyencho]

@doris4lt @riggaroo OK sounds good. I definitely appreciate your help with this!

[Brian Yencho @brianyencho]

@doris4lt @riggaroo We want to return to the original screen and have it already be in the loading state...we don't want to see the transition from the previous content. But we also then want to smoothly transition from the loading screen to the new content.

[Brian Yencho @brianyencho]

@doris4lt @riggaroo I've had a variety of reasons to conditionally skip transitions over the years, but the most immediate use case I have is to avoid a crossfade between loading and content states. This tends to be when we are temporarily covering the content with a screen that triggers a reload.

[Brian Yencho @brianyencho]

@doris4lt @riggaroo OK I tried this out and it introduces different kinds of artifacts. The gist of what I tried was

contentKey = { if (shouldAnimateChanges) it else targetState }

to force the same key but this basically just removed the initial state and still performed the animation.

[Brian Yencho @brianyencho]

@doris4lt @riggaroo I'll give it a try, thanks!

[Brian Yencho @brianyencho]

@doris4lt @riggaroo I can look into that. But it really depends how that key is used and stored. The issue is not that we want states A and B to always ignore transitions...its that we want state's A and B to *sometimes* ignore transitions based on external factors unrelated to their actual values.

[Brian Yencho @brianyencho]

@doris4lt @riggaroo If we try to use a 0-duration AnimationSpec passed to Crossfade to achieve this, we get a bug where we see the old state for one-frame too long.

[Brian Yencho @brianyencho]

@doris4lt @riggaroo We have some use cases where we are using a Crossfade as normal but also need to occasionally completely skip that animation in order to jump directly to a new state. But we also want that next state to be able to crossfade to the next state if necessary.

[Brian Yencho @brianyencho]

New article about maintaining a good git history : https://t.co/3m4OgUHqf6

[Brian Yencho @brianyencho]

The RxJava Threading Mistake You Are Probably Making

https://t.co/ZPbXMEq9cn

[Guy Griv @guygriv]

Issue #56 of onCreate Digest is out
https://t.co/lJK0gSPbjI
#AndroidDev
@brianyencho @vinaygaba @yenerm @manuelvicnt @VasiliyZukanov @massimocarli @rubicon_dev @fatih_grs @mostafa_elabady @ShabTechno

[Brian Yencho @brianyencho]

Coroutine Misconceptions: Whose Context Is It Anyway?
https://t.co/LsKr0oxYFA

[Livefront @livefront]

It’s a big day today for us @livefront! It’s @NelsPederson’s first day and we’re so excited to have him as part of our team in our new Partnerships role! Welcome to Livefront, Nels!!!

[Mike Bollinger @mikebollinger]

So excited to have @NelsPederson joining us @Livefront!