Status Update
No update yet.
Comments
we...@gmail.com
I don't think the average developer understands the distinction between method references and method definitions in this context (inside a DEX file). I know I don't.
@jvg, can you elaborate?
jl...@google.com
jl...@google.com
people who are looking at the bytecode in the dex to optimize their app through shrinking hopefully will learn the difference as string tables for method references between various dex files can account for quite a bit of disk space. but more importantly a definition is something you can analyze its code for where a reference you can't so the UI can be confusing without seeing the difference
jl...@google.com
How about something like this?
I think having defined members be directly under the class node while references are nested in a group makes more sense.
Also note that the method refs have a
an...@google.com
sounds reasonable to me, thanks
an...@google.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 4
- Android Gradle Plugin 8.8.0-alpha04
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
Description
This user's comment sums it up pretty nicely:https://twitter.com/webnakama/status/1643254547442462721
Essentially:
Probably we should have two counts displayed: (1) the number of times the particular widget recomposed (2) the number of recompositions which occurred within the children of a widget. This will allow users to notice and expand the parent nodes when they see large numbers.