I use the entire card when in the IDE and on mobile resize down from the status bar as appropriate. The "effective working screenrect" is the card's working area on mobile. This allows for both the status bar and the keyboard(if visible). So when the keyboard is activated I have the choice of do nothing, shrink the card in the remaining area or if the focused field will be obscured then slide the card up to make is visible.
On Android the "hardware buttons" are just that, physical buttons. Usually Menu(menukey message), home and back(backkey message). On some devices these buttons are soft "hardware buttons" on the bottom of the LCD screen. On these devices you don't have access to those pixels. On other devices the soft "hardware buttons" are part of the status bar and the "mobileHideStatusBar" command will do nothing as you would not be able to exit the app or go to the home screen. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -----Original Message----- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Sannyasin Brahmanathaswami Sent: Monday, May 23, 2016 9:02 PM To: How to use LiveCode Subject: Re: Handling Top Status Bar in App Design Stage Terry, thanks, that pretty much how I thought it would work. I wanted to hide the status bar in some "modules" (card-series) on the same app, but then show them on others as I think users appreciate having that information available… so if the app does not really require every single pixel top to bottom, why not give them the status bar… (my current thinking) Looking at the dictionary I'm seeing only three relevant commands mobileHideStatusbar mobileShowStatusBar iPhoneSetStatusBarStyle (style) Not sure how this plays out on Android if one a) give 22 pixels free space and b) is going to go with one of the full screen modes (my Nexus 5 is out of power at the moment) The dictionary says: "mobileHideStatusBar does not have any effect on any Android devices with "hardware buttons" embedded in the status bar." What exactly are the Android "hardware buttons" I thought those ran at the bottom by default. In the stand alone builder I see the option to set status bar to visible or hidden… so "who" decides where the hardware buttons go.. BR On 5/23/16, 2:23 PM, "use-livecode on behalf of Terry Judd" <use-livecode-boun...@lists.runrev.com on behalf of terry.j...@unimelb.edu.au> wrote: >For iOS I¹ve just taken to leaving the top 22 pixels free of content. >If I want a dark status bar with white text then I position a dark bg >graphic in this space and set the status bar style to Œblack >translucent¹ and if I want black text on a light background I either >set the background of the stack to white and don¹t use a graphic or use >a white or light coloured graphic and then set the status bar style to default. > >Terry... _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
