E: fixed in 0.0.75 - thank you MV :)
Hey there,
I was wondering if anybody else was experiencing this behavior where the swipe to navigate back gesture would register twice within the app, taking you back two steps instead of just one.
I'm not sure exactly when this behaviour was introduced, though it persists with today's .72 alpha release. I was to say it came about in the .6X timeframe.
I've not found this reported on the github, though I just wanted to check that this isn't a system specific issue before submitting. #1399 may be relevant as it refers to swipe input sensitivity but I think that's more of a gesture threshold matter than input registering twice in the app.
My app settings are attached in a photo:
and I have a short clip:
Steps to reproduce:
- Using the provided gesture settings in Jerboa
- From the home feed, tap into a community name
- From the community view, tap into a community post
- Swipe left to navigate back to the community view
- Observe two steps back in response to a single input
Pixel 7, Android 14
This outlines several issues, a key one is outbidding apple for wafer alloc on leading processes. They primarily sell such high margin products that I suppose they can go full send on huge dies with no sweat. Similarly, the 4090's asking price was likely directly related to it's production cost. A chunky boy with a huge l2$.
I like the way Mike Clark frames challenges in semi eng as a balancing act between area, power, freq and performance (IPC); like a chip that's twice as fast but twice the size of its predecessor is not considered progress.
I wish ultra-efficient giga dies were more feasible but it's kind of rough when TSMC has been unmatched for so long. I gather Intel's diverting focus in 18A, and I hope that turns out well for them.
I'm not sure that arm as an ISA (or even RISC) is inherently more efficient than CISC today, particularly when we look at Qualcomm's latest efforts in notebooks, more that Apple have extremely proficient designers and benefit from vertical integration.