Gino Valente

I think one way to achieve fine-grained change-detection-like behavior would be to make `Preferences` a `SystemParam` that modifies a resource internally. That way we can send some sort of `PreferenceChange`...

> Have you tried [simpleBoundsCalculation setting](https://github.com/appium/appium-uiautomator2-driver#settings-api) ? Unfortunately, it's still returning only the visible frame.

I found this chunk of code, which I think might be related? https://github.com/appium/appium-uiautomator2-server/blob/e3ce25db6cdbc8032afe39232cc62d58ad2c1bb5/app/src/main/java/io/appium/uiautomator2/core/AxNodeInfoHelper.java#L235-L280

> Yes it is related. As far as I can see https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo only provides a single method for fetching element's bounds: https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo#getBoundsInScreen(android.graphics.Rect) Does this return the full bounds? If it...

Ah okay I see now. Yeah after looking at the documentation and running a few tests, it seems it does not account for any parts of an element that are...

I suppose if we had access to the `UiObject`, we could get this information, right? At least according to these [docs](https://developer.android.com/reference/androidx/test/uiautomator/UiObject#getBounds()) (though, I'm not sure if this just returns the...

Marking this as a good first issue. I think it should be easy enough to implement the UUIDs for all primitive types and maybe a few extras. I feel like...

Hm, this is an interesting one because it's a slightly different data structure. We sorta lose its usefulness (the queue properties) when reflecting, and we can only really get it...

> should the methods on the `TypePath` (possibly `TypeName`) trait(s) take in `&self` so that the `Dynamic*` reflect types work as intended from a reflection standpoint, or is this out-of-scope...

Closing this out as superseded by #7184