native.newTextBox not working in simulator Build 1256

Other
#1

So My program is as follows: … tried on builds 1249 and 1256

textArea = native.newTextBox(10, 10, 200, 200 ) textArea.isEditable = true  

The simulator will not accept input. Get no indication that the cursor is in the Text Box.

Doing the same thing with:

textArea = native.newTextField(10, 10, 200, 200 ) textArea.isEditable = true  

Everything is fine.

Please fix the simulator or help me understand the errors of my ways.

Cheers,

Marc

#2

Hi Marc,

I just tested an app using these functions, built with #1256. The cursor appears for me. Do you have the “userInput” event listener written yet? When the text field first comes up, it won’t have a blinking cursor, but it will after you click inside it. At least that’s what is occurring with my implementation… although I may have written it slightly different than other developers.

Best regards,

Brent

#3

No listener my entire program is:

textArea = native.newTextBox(10, 10, 200, 200 )
textArea.isEditable = true

I did of course try clicking in the box … nothing … typing nothing … just a white box.  As i mention the newTextField works just fine.

My simulator is running on a new mac powerbook running mavericks.

#4

Hi Marc,

Is this only happening in the Simulator, or also on the device? i.e., is it a build issue too, or Simulator only?

Thanks,
Brent

#5

Seems to be simulator only … or at least not android … did not test iOS.

Be important for it to work as testing in the simulator is … well rather important.

#6

Hi Marc,

If possible, could you try public build #1202 to test this on? That would narrow down if it’s a Mavericks issue (which is what I’m suspecting it is, since my test works fine with OS X 10.8.x).

Brent

#7

Brent,

1202 yields the same result.  Still no joy.

Hope this helps.

Cheers

#8

Any update on this Brent?

#9

Hi Marc,

Not quite yet, we’re still checking into it. And as you stated in another post, there are a handful of Mavericks issues (or so it seems), not just for Corona but across the software-sphere. :frowning:

Thanks for your patience,

Brent

#10

This one is killing me … no way to test in the simulator without getting this to work … guess this is what i get for buying a new macbook and ending up with Mavericks … it is fast though :slight_smile:

ETA on fix for this?

#11

Hi Marc,

We have managed to replicate the issue on our side, and it’s Mavericks-related. I don’t have an ETA on its fix yet, but its known by the engineers and in the queue.

Sincerely,

Brent

#12

Hi Marc,

I just tested an app using these functions, built with #1256. The cursor appears for me. Do you have the “userInput” event listener written yet? When the text field first comes up, it won’t have a blinking cursor, but it will after you click inside it. At least that’s what is occurring with my implementation… although I may have written it slightly different than other developers.

Best regards,

Brent

#13

No listener my entire program is:

textArea = native.newTextBox(10, 10, 200, 200 )
textArea.isEditable = true

I did of course try clicking in the box … nothing … typing nothing … just a white box.  As i mention the newTextField works just fine.

My simulator is running on a new mac powerbook running mavericks.

#14

Hi Marc,

Is this only happening in the Simulator, or also on the device? i.e., is it a build issue too, or Simulator only?

Thanks,
Brent

#15

Seems to be simulator only … or at least not android … did not test iOS.

Be important for it to work as testing in the simulator is … well rather important.

#16

Hi Marc,

If possible, could you try public build #1202 to test this on? That would narrow down if it’s a Mavericks issue (which is what I’m suspecting it is, since my test works fine with OS X 10.8.x).

Brent

#17

Brent,

1202 yields the same result.  Still no joy.

Hope this helps.

Cheers

#18

Any update on this Brent?

#19

Hi Marc,

Not quite yet, we’re still checking into it. And as you stated in another post, there are a handful of Mavericks issues (or so it seems), not just for Corona but across the software-sphere. :frowning:

Thanks for your patience,

Brent

#20

This one is killing me … no way to test in the simulator without getting this to work … guess this is what i get for buying a new macbook and ending up with Mavericks … it is fast though :slight_smile:

ETA on fix for this?