Android native field bug/help [Solved]
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
Android native field bug/help [Solved]
Hi all,
So I have 2 cards, card A and B. Card B has 3 android native field and some other labels and graphics. Whenever card A goes to card b, it always shows the 3 android native fields first before lagging and showing the rest. I have already tried using lock and unlock screen, putting the preopencard script into opencard. Wonder is it a bug or something I’m doing wrong. The reason why I’m using android native field is because I’m gonna use the keyboard type number so that the keyboard on screen only allows users to key in number.
Thanks!
So I have 2 cards, card A and B. Card B has 3 android native field and some other labels and graphics. Whenever card A goes to card b, it always shows the 3 android native fields first before lagging and showing the rest. I have already tried using lock and unlock screen, putting the preopencard script into opencard. Wonder is it a bug or something I’m doing wrong. The reason why I’m using android native field is because I’m gonna use the keyboard type number so that the keyboard on screen only allows users to key in number.
Thanks!
Last edited by EddieLee on Fri Mar 05, 2021 6:21 am, edited 1 time in total.
Eddie
-
- VIP Livecode Opensource Backer
- Posts: 9662
- Joined: Wed May 06, 2009 2:28 pm
- Location: New York, NY
Re: Android native field bug/help
Hi.
I do not develop for mobile, but is it possible that native fields are rendered apart from LC controls? In other words, can you hide, under LC script control, native fields? If you can, then something else is going on, because you ought to be able to control their "visible" property.
This is all conjecture.
Craig
I do not develop for mobile, but is it possible that native fields are rendered apart from LC controls? In other words, can you hide, under LC script control, native fields? If you can, then something else is going on, because you ought to be able to control their "visible" property.
This is all conjecture.
Craig
Re: Android native field bug/help
Hi Craig,dunbarx wrote: ↑Mon Mar 01, 2021 6:48 pmHi.
I do not develop for mobile, but is it possible that native fields are rendered apart from LC controls? In other words, can you hide, under LC script control, native fields? If you can, then something else is going on, because you ought to be able to control their "visible" property.
This is all conjecture.
Craig
So would I need to hide the native fields first and then show them when I enter the card?
Thanks!
Eddie
Re: Android native field bug/help
as a failure behavior...could it be related ?
Don't try to draw a Data Grid on a card that Is not open
When a Data Grid renders it dynamically creates fields and accesses certain properties. Some of these properties can not be properly reported by the Revolution engine unless the field is on an open card.
Code: Select all
https://lessons.livecode.com/m/datagrid/l/7340-what-sorts-of-things-should-i-not-do-in-order-to-avoid-needless-suffering
When a Data Grid renders it dynamically creates fields and accesses certain properties. Some of these properties can not be properly reported by the Revolution engine unless the field is on an open card.
Re: Android native field bug/help
Hi,liveme wrote: ↑Tue Mar 02, 2021 2:38 amas a failure behavior...could it be related ?Don't try to draw a Data Grid on a card that Is not openCode: Select all
https://lessons.livecode.com/m/datagrid/l/7340-what-sorts-of-things-should-i-not-do-in-order-to-avoid-needless-suffering
When a Data Grid renders it dynamically creates fields and accesses certain properties. Some of these properties can not be properly reported by the Revolution engine unless the field is on an open card.
I’m not really using a datagrid but more of a android native button/field.
Thanks!
Eddie
-
- VIP Livecode Opensource Backer
- Posts: 7235
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: Android native field bug/help
I had a similar issue with odd redraws when changing cards. Try the latest rc version of LC and see if the problem persists. There were some fixes in that release that may help.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: Android native field bug/help
HI Jacque,
I have solved the issue, because there was some scripts in my preopencard handler which is getting data from my database which causes the app to lag a bit therefore, the android native field has shown first before the scripts are done. Does this counts as a bug?
Thanks !
Eddie
-
- VIP Livecode Opensource Backer
- Posts: 7235
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: Android native field bug/help
I don't think it's a bug. PreOpenCard doesn't continue the handler until each command completes.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: Android native field bug/help
so eddie, did you just add a small delay untill data was fully loaded to... "solve" that ?which is getting data from my database which causes the app to lag a bit therefore
Re: Android native field bug/help
Hi All,
I just moved the extracting data from the database script down to opencard handler and it solved my issue.
Thanks !
I just moved the extracting data from the database script down to opencard handler and it solved my issue.
Thanks !
Eddie