-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split out device settings such as width, height #7
Comments
@yschimke It is definitely sth I want to do, but the “device” preview value is the hardest to map due to the string parsing, and all its options, so to speak. I’ll likely support other preview info values first, before diving into this, or initially provide support for preview predefined devices that are already available in Paparazzi & Roborazzi, which should be straightforward. |
I ended up applying the qualifiers and then querying them via InstrumentationRegistry. Perhaps that avoids parsing config files? |
Yep, it's similar issue. If 6 is done, I don't need this. Actually for file naming, but can achieve in other ways. |
Interesting. Could you share a code snippet? That would help 😊 |
closed PR here https://github.com/android/wear-os-samples/pull/1126/files#diff-4b70e4b273d07b2d520241a25769c3b3b36ecb00b427e43e5027bcbc90b9c363 A few relevant things I needed to do for my case Apply a device clip
Grab the device string and then apply via known values, because of this issue
Apply and then grab the size and font scale for the filename
|
Previews are like
|
FYI 0.1.2 includes some improvements in that component |
Because in AndroidComposablePreviewInfoMapper
device="id:wearos_large_round" implies a bunch of other settings, which aren't currently applied.
Seems preferable for the library to handle this, rather than each app adopting.
The text was updated successfully, but these errors were encountered: