Infeasible
Status Update
Comments
ve...@google.com <ve...@google.com>
ve...@google.com <ve...@google.com> #2
Thank you for your patience, we have rolled back a change in the Google 3D Tiles API service. Could you check on your end if this fixes your issue?
ni...@gmail.com <ni...@gmail.com> #3
Thank you for your prompt response and for rolling back the recent change
in the *Google 3D Tiles API service*. I have tested it on my end, and I can
confirm that the issue is now resolved.
I truly appreciate your quick action in addressing this matter. Your
support is invaluable, and I'm grateful for the efficiency and dedication
of your team.
Thanks again for your help!
*Best regards,Mohammad*
On Fri, Feb 14, 2025 at 7:17 AM <buganizer-system@google.com> wrote:
in the *Google 3D Tiles API service*. I have tested it on my end, and I can
confirm that the issue is now resolved.
I truly appreciate your quick action in addressing this matter. Your
support is invaluable, and I'm grateful for the efficiency and dedication
of your team.
Thanks again for your help!
*Best regards,Mohammad*
On Fri, Feb 14, 2025 at 7:17 AM <buganizer-system@google.com> wrote:
vi...@google.com <vi...@google.com> #4
Thank you for the confirmation.
Note however that we plan to restart the rollout soon. IIUC the version 2.7.13 of Blosm was released with a fix: could you confirm with the developer that this version of the plugin would continue working if we were to restart the rollout now?
g4...@gmail.com <g4...@gmail.com> #5
Same for me, I think View class is unreadable without obfuscation (even Github can't show the sources: "(Sorry about that, but we can’t show files that are this big right now.)" https://github.com/aosp-mirror/platform_frameworks_base/blob/master/core/java/android/view/View.java ).
AOSP team, please refactor this class.
AOSP team, please refactor this class.
ad...@google.com <ad...@google.com>
te...@google.com <te...@google.com> #6
Thanks for the feedback. Due to other priority features, we’re not currently able to support your request. Please feel free to re-open the issue in the future if desired.
Description
Download the file
- Correct behavior:
I think View.java must be an interface with only one method - draw().
Come on guys, 27k loc - it is too difficult to read, there is so huge scope, that my brain can't fully absorb it, and every time when I develope some custom view I use google search to do what needs to be done, because all code base from View.java is also coming to my view because of inheritance.