• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Fixed Page Size & screen dimensions
#1
A while ago we had a lengthy discussion about 'Fixed Page Size', 'Auto Size Font' and the like: https://www.zubersoft.com/mobilesheets/f...12378.html
Now, after a number of iterations and fixes I finally decided to move my library from my HP Detachable to my Boox Tab Ultra C. This requires setting the fixed page size values and adapting font settings for every ChordPro file (and there are many). In my notes from the mentioned discussion I find, that the screen size that MobileSheets uses is not exactly the size that is specified for the device. At that time (MobileSheets 3.9.7) clicking "Set to Screen" filled width and height with the effective dimensions. Now (MobileSheets 3.9.17) "Set to Screen" resets width and height to -1 / -1. Everything seems to work, but I would like to know a way to find out these effective dimensions. 
In fact it makes a difference: According to the specs the Detachable's screen is 800 x 1280, the Boox's is 1860 x 2480. In my old notes I find effective dimensions are 800 x 1208 for the Detachable, 1860 x 2354 for the Boox (both in portrat orientation). I want to specify a fixed page size that matches the 4:3 ratio of the Boox using the 800 pixel width of the Detachable.
The difference is significant:
2354 / 1860 x 800 = 1012,47
2480 / 1860 x 800 = 1066
When I set fixed page size to 800 x 1012 the rendered image fits perfectly, with 800 x 1066 the image is a bit too high, resulting in small black margins left and right.
For now I know what I need, but how can I check if my notes are still correct? Or find out correct dimensions for possible other devices?
I won't mind calculating something or look into the database with an SQLite tool, just need some hints what to do.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#2
Tapping "Set to Screen" sets the width and height to -1 for you? That's so strange. I will run some tests today on my BOOX Tab X to see if I can find a way to reproduce that. The width and height that are reported take into account screen decorations/bars, such as the navigation bar at the bottom of the screen or the status bar at the top of the screen (if it is visible). MobileSheets is just using the value that the SDK is returning for the application window size instead of using the raw dimensions of the tablet (as rendering to the raw dimensions could lead to the full screen not being utilized due to those decorations/bars). The information about the width/height isn't saved in the database anywhere. 

Mike
Reply
#3
Tapping "Set to Screen" sets the width and height to -1 - this happens only on Windows, MobileSheets version is 3.9.17
On the Boox it sets 1860 x 2354 as before, on my Huawei MediaPad T5, nominal resolution 1200 x 1920, it says 1200 x 1692, my previous notes say 1200 x 1852. What influences that difference?
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#4
I try to investigate the influence of various display settings to find my favourite fixed page size and I'm a bit confused.
These settings seem to influence the result of clicking "Set to screen" on the Boox, but not all are independent:
Show Next Song Indicator
Always Show the Title Bar
Hide the Navigation Bar
Fullscreen Mode
Hide Window Decor
Dim the Navigation Bar

Can it be correct that "Show Next Song Indicator"has no influence?
Could you please help me understand what happens
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#5
It looks like I modified the code to try to provide the exact amount of rendering space available for the score, which does get offset by things like the title bar and the next song indicator. I may change this to instead just try to use the size of the application window even if it means the score may get reduced in height by things like the title bar or the next up song bar. Just be aware that the application window size will be impacted by the presence of the navigation bar and the status bar, as mentioned, so make sure those are hidden if you don't want those to impact the size that is calculated.

Mike
Reply




Users browsing this thread:
3 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2025 MyBB Group.