Another iOS native control instantiation question

Graham Samuel livfoss at mac.com
Tue Apr 10 09:37:46 EDT 2012


Hi

Can someone confirm that if one moves from card to card in an iOS app, any native controls (such as text input) need to be instantiated as the card is opened, and destroyed when another card is shown? This is very unlike the behaviour of LC on other platforms, where a field remains a field whether it's shown or not, that I feel I may have missed a trick here.

Suppose for example one of my cards is dedicated to input of several small and essentially unrelated data items, with a lot of little one-line fields which the user has to fill in. When the user decides to invoke this feature of the app, the 'input' card appears. At this point, if it's as described (a lot of little essentially identical fields), then presumably I just have to create one single-line input control which will appear each time one of my fields get the focus, and script the handling of each input text accordingly: and when the user steers away from this card I should destroy the control.

Is this right, and what would happen if I didn't do the destroy? I ask here because I'm getting overwhelmed by the need to experiment for almost every aspect of the behaviour of my iOS device and I'm frankly keen to learn from others' experience.

TIA

Graham




More information about the use-livecode mailing list