Your guess is right OderWat, they are not in "yourGroup", that's why you cannot remove them

If you insert a text field in a group, and set the x coordinate of the group to 320, the text field should not show up on the screen, yet it does...

I also noticed that whenever i tap on the field to type, on the Organizer console i get the message:
Mobile Safari warning, Safari got memory level warning, killing all documents except active...
There are no other elements, other than the text field, to consume memory

@OderWat,

Can you provide some sample code showing the problem where the textField is not removed from the group?
I'm playing with a fix but can't find a test case under Beta 6 where the native.textField is not removed.

Thanks,
Tom

Hi Gilbert,

Thanks for the code. The problem is this code works in Beta 4, 5, and 6. If I click on the "Remove TextField" button, the textField disappears (as it should).

This code does have a problem because there is no listener for the textField and therefore no way to dismiss the keyboard (which hides the buttons).

I added this code to remove the keyboard after pressing Return.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

local function fieldHandler( event )
 
        if ( "began" == event.phase ) then
                -- This is the "keyboard has appeared" event
                -- In some cases you may want to adjust the interface when the keyboard appears.
        
        elseif ( "ended" == event.phase ) then
                -- This event is called when the user stops editing a field: for example, when they touch a different field
        
        elseif ( "submitted" == event.phase ) then
                -- This event occurs when the user presses the "return" key (if available) on the onscreen keyboard
                
                -- Hide keyboard
                native.setKeyboardFocus( nil )
        end
 
end

I added the listener to the text field.

1

myTextField = native.newTextField( 0, 0, display.contentWidth*.6, 25, fieldHandler)

Tom,

this doesn't work in Beta 5
the text field is not removed

and if you replace myTextField.isVisible = not myTextField.isVisible
with myGroup.x=100, the text field doesn't move even though it belongs to myGroup.

you can hide it by using
myTextField.isVisible=false or
myTextField.x=500

but it cannot be removed, and it behaves as if it doesn't actually belong to the group.
the way it is right now, there's no meaning into inserting a native text field in a group.

@tetu,

The fix will allow you to remove native.textField/textBox from the screen with object:selfRemove().

The Corona documentation states that the native objects do not obey the Corona display object hierarchy nor do they inherit display group properties (i.e. isVisible, x, y, and alpha). You still need to set the properties on the native objects directly. That part hasn't changed.

When objects (native or otherwise) are created, they are part of the current stage, which is a group. Since the native objects don't inherit any of the group properties, it doesn't make sense to add them to another group. Generally they would be displayed temporary (i.e. to input some text) and then dismissed.

-Tom