klaus Expert Licensed User Longtime User Oct 31, 2014 #1 How are the different screen sizes managed by iOS ? I have an application with the 'standard' iPhone screen size 320 * 568 / 160 in the Designer. On my iPhone 6 with a screen of 750×1334 it is OK horizontally but vertically it must be adjusted. What about tablets or iPhone 6+ ? Last edited: Nov 13, 2014
How are the different screen sizes managed by iOS ? I have an application with the 'standard' iPhone screen size 320 * 568 / 160 in the Designer. On my iPhone 6 with a screen of 750×1334 it is OK horizontally but vertically it must be adjusted. What about tablets or iPhone 6+ ?
Erel B4X founder Staff member Licensed User Longtime User Nov 2, 2014 #2 The main difference here is that you don't need 'dip' units in iOS. The OS does it for you. All the sizes are already normalized (to a scale of 1.0). You can see the different screen sizes in the abstract designer menu: Developers need to handle it in the same way they do in B4A. Mainly with anchors, auto scale, designer script, variants and code. Currently auto scale and designer script are not supported. However they are high on the list... Upvote 0
The main difference here is that you don't need 'dip' units in iOS. The OS does it for you. All the sizes are already normalized (to a scale of 1.0). You can see the different screen sizes in the abstract designer menu: Developers need to handle it in the same way they do in B4A. Mainly with anchors, auto scale, designer script, variants and code. Currently auto scale and designer script are not supported. However they are high on the list...
Erel B4X founder Staff member Licensed User Longtime User Nov 2, 2014 #3 Note that you can use dip unit in B4i. However it won't do anything. Upvote 0
klaus Expert Licensed User Longtime User Nov 2, 2014 #4 Erel said: Note that you can use dip unit in B4i. Click to expand... That's what I do, by habit . The reason to keep the DipToCurrent function in B4i is only for compatibility with B4A ? Upvote 0
Erel said: Note that you can use dip unit in B4i. Click to expand... That's what I do, by habit . The reason to keep the DipToCurrent function in B4i is only for compatibility with B4A ?
Erel B4X founder Staff member Licensed User Longtime User Nov 2, 2014 #5 klaus said: The reason to keep the DipToCurrent function in B4i is only for compatibility with B4A ? Click to expand... Yes. DipToCurrent is also required for dip units (which are also kept for compatibility only). Upvote 0
klaus said: The reason to keep the DipToCurrent function in B4i is only for compatibility with B4A ? Click to expand... Yes. DipToCurrent is also required for dip units (which are also kept for compatibility only).
klaus Expert Licensed User Longtime User Nov 13, 2014 #6 I'm coming back to this thread because my findings in the first post are no more true since B4i version 1.00 (see this thread). Erel said: Developers need to handle it in the same way they do in B4A. Mainly with anchors, auto scale, designer script, variants and code. Click to expand... If I understand well, these functions are B4i specific (with much more freedom) and not Apple 'standard' (less freedom) ? Upvote 0
I'm coming back to this thread because my findings in the first post are no more true since B4i version 1.00 (see this thread). Erel said: Developers need to handle it in the same way they do in B4A. Mainly with anchors, auto scale, designer script, variants and code. Click to expand... If I understand well, these functions are B4i specific (with much more freedom) and not Apple 'standard' (less freedom) ?
Erel B4X founder Staff member Licensed User Longtime User Nov 13, 2014 #7 The anchors and variants features are implemented as part of B4i designer. Auto scale and designer script are also custom features (not implemented yet). Upvote 0
The anchors and variants features are implemented as part of B4i designer. Auto scale and designer script are also custom features (not implemented yet).
