Android status bar bug

[brotee]

I've compiled the APP with status bar hidden, and it's working well.

when keyboard comes up (status bar comes up too) and i press down key on keyboard to hide the status bar, the screen over the status bar becomes black, and i can't do anything with that, only app restart helps.

i've tried to run mobileHideStatusBar too, still the same.

Attached 3 screens

[jacque]

Do you mean the navigation bar at the bottom? None of the screenshots show the top status bar.

[brotee]

Yep, sorry, navigation bar, when keyboard goes down, spot of navigation bar will be black.

And if i put anything there you can't see on the phone

[jacque]

I think you should report this as a bug at http://quality.livecode.com.
For now, you might be able to work around it if you add this to the script when the keyboard deactivates:

Code: Select all

set the backcolor of this stack to the backcolor of this stack

That forces the engine to redraw the card.

[brotee]

so.. i'll try to explain what's happening

with LC9.01:

sometimes the whole stack goes up with the height of navbar, sometimes not, but the navbar spot remains black. if the stack is moving up, the native input fields goes up too sometimes, sometimes not?!!!

keyboardDeactivated is not firing!!!!! but if i check top of the stack it shows zero

different behavior if i press down arrow on keyboard, or if i press return.

i've tried everything, but couldn't make it work

with LC 9.00 AND 8.1.9:

everything works, except if i CLOSE the keyboard all of the controls jump once. But atleast they go back to the original position, doesn't look well, but atleast it's working.

[jacque]

The scrolling behavior when the whole card moves is a very old bug. It is a side-effect of acceleratedRendering and isn't really supposed to happen. The only fix that I know about is to turn off acceleratedRendering on that card. If the keyboard will cover the field, you can move it in a keyboardActivated handler using the "move" command. Then on keyboardDeactivated, move it back down where it belongs. I had to use this workaround in my current project.

There is a bug report on this and Mark Waddingham suggested we need a command to scroll the card on demand, which would be a great idea. If your field is high enough on the card that the keyboard doesn't cover it, you don't need to do anything except set acceleratedRendering to false. When you open a card that does need it, set acceleratedRendering to true again on preOpenCard.