-
Notifications
You must be signed in to change notification settings - Fork 807
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
Multimeter: Layout looks weird on tablet devices #2118
Labels
Comments
My device: Device: Lenovo Yoga Smart Tab |
Hey I would like to solve this issue and try my best |
5 tasks
riturajjain2000
added a commit
to riturajjain2000/pslab-android
that referenced
this issue
Oct 5, 2020
Added Tablet layput for multimeter , unlocked landscape mode for some activities and fixed landscape mode of Splash Screen
riturajjain2000
added a commit
to riturajjain2000/pslab-android
that referenced
this issue
Oct 5, 2020
Added Tablet layput for multimeter , unlocked landscape mode for some activities and fixed landscape mode of Splash Screen
CloudyPadmal
pushed a commit
that referenced
this issue
Oct 12, 2020
* This commit Fixes #2119 #2118 Added Tablet layput for multimeter , unlocked landscape mode for some activities and fixed landscape mode of Splash Screen * This commit Fixes #2119 #2118 Added Tablet layput for multimeter , unlocked landscape mode for some activities and fixed landscape mode of Splash Screen * Made Changes as asked Now the Multimeter , Wavegenerator and Powersource Activities will remain only in portrait mode in normal sized phones and will have both portrait and landscape modes in Tablets
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual Behaviour
The multimeter looks weird on tablet devices, the measured value is partly hidden.
Expected Behaviour
The layout should look more pleasing (larger knob or a margin around the whole multimeter) and the value should be completely visible.
Steps to reproduce it
Screenshots of the issue
Would you like to work on the issue?
Maybe..
The text was updated successfully, but these errors were encountered: