Textbox doesn't inherit isVisible from group. Annoying.

Solar2D Daily Builds and Public Releases
#1

I can’t make it work. Textbox is inserted into a group and all object except text box are rendered invisible when I set ‘group.isVisible = false’.
I can make the textbox invisible directly via ‘isVisible = false’ so I am guessing that this is a bug.

Since textbox is not supported in simulator it took me a couple of hours to discover where the problem is. It was extremely annoying.
If the textbox was available in the simulator it would take me probably couple of minutes.
I am very annoyed by this situation. I payed for Corona software and I don’t think my job is to debug it. That is your job, Ansca staff.

I am aware it is almost impossible to create software without any bugs, and I am not saying that you should. What you should do, Ansca staff, is make all of API’s available IN simulator BEFORE publishing SDK.

I feel like I am coding for 2 devices - actual iPhone device & Corona simulator.

A grumpy client :confused: [import]uid: 4294 topic_id: 603 reply_id: 300603[/import]

#2

Yes, having pieces only work in device really make developers have to debug on device. I’ve rather have all functionality accessible from Simulator even if it looks a little different. AGRW [import]uid: 3867 topic_id: 603 reply_id: 1249[/import]

#3

Agreed – the ideal is to be able to debug in the simulator.

In this case, a significant number of developers specifically asked for certain features as rapidly as possible, especially input text, even without simulator counterparts. But in general I would prefer to have things available in the simulator. [import]uid: 3007 topic_id: 603 reply_id: 1338[/import]

#4

evank, how does this sound:
1.) You (by that I mean Ansca) make features available in simulator & on the device. You name this ‘Corona SDK’.
2.) You make any features you like (that developers ask for etc…), and until you test it (on the device AND the simulator) - you name that ‘Corona SDK BETA’.

So who ever wants to use risky advanced features or wants to debug your software - can do so. Others, like me, who wish to use reliable software can get something too.

I know that you have a beta program. I would like to ask you to make a clearer difference between what is actually in BETA and what you release as a finished product. One difference could be - if it works on the device but not on the simulator - its BETA.

Other suggestion could be that you make a priority list. One priority could be: fix bugs that relate to finished product, then fix bugs that relate to BETA.
This way your product would be more stable, your clients more satisfied - and you more rich or whatever your mission is :wink:

I’ll post this in feature requests too. [import]uid: 4294 topic_id: 603 reply_id: 1346[/import]

#5

(Logged as bug #125. Agreed on the “annoying” part.) [import]uid: 3007 topic_id: 603 reply_id: 2001[/import]