Hi all -
I’ve gone and coded myself into a corner and would appreciate any advice you might be able to offer.
The good news is that my application is working perfectly.
Now, I just want to make a little improvement.
Here’s the deal:
My app contains many screens that each have multiple text entry boxes. On each screen, I’ve grouped these entry boxes together and then create a native scroller so that the user can flick through the various options on the page. Like I said – all is working well.
But here’s the problem:
When I first created my app, I (stupidly) didn’t consider using native text entry fields. Instead, I simply used Livecode’s standard text entry fields.
So now, I’d like to “upgrade” my app to utilize true native text entry fields. I know how to create the fields, but I am unsure how I “place” them into the existing group so that they scroll with the scroller I’ve already created.
Is there an easy way to do this? I’d be ever so grateful for any advice you might have.
Peace.
Joel
Adding Native Text Fields to Existing Group
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- Posts: 135
- Joined: Thu Sep 13, 2012 10:25 pm
Re: Adding Native Text Fields to Existing Group
Hi Joel,
I dont think this is possible at all!
1. Native controls are rendered as overlays and thus cannot be part of e.g. a Livecode GROUP.
2. You cannot "stack" two native controls (input field & "scroller").
Best
Klaus
I dont think this is possible at all!
1. Native controls are rendered as overlays and thus cannot be part of e.g. a Livecode GROUP.
2. You cannot "stack" two native controls (input field & "scroller").
Best
Klaus
-
- Posts: 135
- Joined: Thu Sep 13, 2012 10:25 pm
Re: Adding Native Text Fields to Existing Group
Thanks, Klaus.
Can you think of any workarounds? I'm rather stumped.
Joel
Can you think of any workarounds? I'm rather stumped.
Joel
Re: Adding Native Text Fields to Existing Group
Hi Joel,
sorry, no idea for a workaround.
I could successfully avoid mobile development so far...
Best
Klaus
sorry, no idea for a workaround.
I could successfully avoid mobile development so far...

Best
Klaus