Tableview Still Broken Since 1073 - Come On Guys...

Solar2D Widgets
#1

Look, the tableview has been broken since build 1073. I am using a tableview with category headers and the first one never shows up. For example say I had names in a tableview and the category header A-Z, when the tableview is shown where “A” would be in the category header(top of tableview) there is nothing, just a category row with no text. If you scroll whatever letter/category header  should be at the top isn’t, just blank text. I swear this has to do with the changes to the row rendering, since the issue arose when you guys started work on that. This has been broken since build 1073 and this is preventing me from upgrading to a more recent build(event the latest Public Release). I can’t release this app with things broken like that. I have submitted a bug like I always do, but I never know the status of the bug or when its fixed. I check the daily builds every day, and download and test just because you guys don’t always put every bug fixed in the changelog.

I also have had another issue with multiline native text boxes not wrapping automatically(broken for a really  really long time). I also filed a bug for this and have had exchanged an email or 2 with Corona Support but then nothing. I have no idea what the status of these 2 show stopping bugs for our app, its frustrating having to tell your boss you have no clue when/if they will be fixed.

With the cost of a Corona License going up almost double I expect to get much better support and attention with bugs that prevent an application from moving forward. I have done everything asked, I reported bugs, even included test code to replicate each bug. You guys can’t keep people in the dark like this, having my app release date and company marketing on hold until who knows because of no communication is NOT cool. I make games with Corona but I also have to make business/utility apps for customers/clients and the attention and support you guys provide for the utility/business apps suck compared to the support you give to game based apps.

I appreciate the hard work you guys put in, but I think things can be handled better. Nothing worse then demoing your companies app at a convention and not being able to tell them a release date because of little bugs that you have no clue if they are being worked on or when they are going to be fixed. Sorry for the rant, but I’m at my wits end with this, I have no clue how to proceed other then to start over and go back to coding in native Objective C and scrap over 6 months of development…

Someone at Corona please contact me so we can talk about this. I love you guys and what you do but we can’t keep going forward like this.

#2

Is there anything in Widgets 2.0 that you *need* or can you continue using widgets 1.0 for now?

I hope I’m wrong, but I suspect work on Widgets inside Corona Labs is going slowly at this point in preparation for their release as open source. At which point you may see a bunch more movement as those of us who use it dive in and try to fix things.

 Jay

#3

Unfortunately I need Widgets 2.0, originally I had used widgets 1.0 but there was too many bugs. Widgets 2.0 was buggy at first and I filed a lot of bugs, for the most part they were taken care of (thanks Danny!). I have 3 apps for clients that can’t get released because of this textbox bug. Since it has been going on for months I lose out. I think that for bugs that hinder you releasing your app or game  Corona should give you a month extension on your license. A simple thing like a multiline textbox that wraps correctly should be a core component and without it utility/business apps can’t be done IMO. Look at the sample code go to Interface and then Native Display Objects, run that project and use the text box. Now imagine this is your app and a main component is entering data, enter some long sentences and watch how the textbox doesn’t wrap like it should. Would you release an app like that? I can’t put my name on things like that and I think those types of bugs should have priority over some of the things I’m seeing in the daily builds. Problem is is most people use Corona for games and because of that their main focus is on games and the rest just falls off the plate. I read countless posts with people complaining about this issue. Corona needs to address it, hire/put a person in place whose sole job is to make sure Corona can be used in business/utility apps. Either that or stop promoting Corona as a solution for games and other types of apps.

BTW one of these apps is a EHR solution that is used by many health providers along the East Coast. You know how embarrassing it is for a simple thing like a textbox to have issues for this long? Having to tell these people I have no clue when that will be fixed and therefore no clue when the app will be released? I’m really at a crossroads here.

#4

Hi @chevol,

I appreciate your patience, and would like to help resolve this. Can you please contact me via e-mail so we can open up a dialogue? I know you’ve been patient and filed various issues about widgets. I just need to refresh and clarify the history and what has or hasn’t been handled up to this point. Email is brent (at) coronalabs (dot) com.

Sincerely,

Brent

#5

I also am experiencing TableView problems with the category overlaying at the top. I tried today’s build (2013.1089) and the same happens.  I have to reinstall build 2013.1072 which works, so something changed but not sure with which build.

Sometimes it initially displays ok then when moved the top category shifts into the middle (approx) of the row.

@Brent - Can you please keep the dialog going here and not where others can’t contribute to the symptoms and status?

#6

Generally speaking, it’s a real problem having features working nice on one build not working on a newer release, and it happens very (too) often. At my side, same code building a tableView is OK with DB 1088 but not with 1092… depending on number of elements in tableView.

The problem is that coming back is not allways possible. If a bug is solved in build N+1 and a new bug appears in this build or later, going back to build N is not very helphful.

Some testing at your side before releasing a new build would be nice,I understand it’s not easy but we have to rely on serious langage, not on unstable things.

#7

I believe that the category issue has been fixed in build 2013.1093.

I had the same issue, and after some investigation I found that the culprit was row.isCategory could sometimes return nil instead of a true value. I got around the issue by handling the nil return value in my event handler.

#8

Is there anything in Widgets 2.0 that you *need* or can you continue using widgets 1.0 for now?

I hope I’m wrong, but I suspect work on Widgets inside Corona Labs is going slowly at this point in preparation for their release as open source. At which point you may see a bunch more movement as those of us who use it dive in and try to fix things.

 Jay

#9

Unfortunately I need Widgets 2.0, originally I had used widgets 1.0 but there was too many bugs. Widgets 2.0 was buggy at first and I filed a lot of bugs, for the most part they were taken care of (thanks Danny!). I have 3 apps for clients that can’t get released because of this textbox bug. Since it has been going on for months I lose out. I think that for bugs that hinder you releasing your app or game  Corona should give you a month extension on your license. A simple thing like a multiline textbox that wraps correctly should be a core component and without it utility/business apps can’t be done IMO. Look at the sample code go to Interface and then Native Display Objects, run that project and use the text box. Now imagine this is your app and a main component is entering data, enter some long sentences and watch how the textbox doesn’t wrap like it should. Would you release an app like that? I can’t put my name on things like that and I think those types of bugs should have priority over some of the things I’m seeing in the daily builds. Problem is is most people use Corona for games and because of that their main focus is on games and the rest just falls off the plate. I read countless posts with people complaining about this issue. Corona needs to address it, hire/put a person in place whose sole job is to make sure Corona can be used in business/utility apps. Either that or stop promoting Corona as a solution for games and other types of apps.

BTW one of these apps is a EHR solution that is used by many health providers along the East Coast. You know how embarrassing it is for a simple thing like a textbox to have issues for this long? Having to tell these people I have no clue when that will be fixed and therefore no clue when the app will be released? I’m really at a crossroads here.

#10

Hi @chevol,

I appreciate your patience, and would like to help resolve this. Can you please contact me via e-mail so we can open up a dialogue? I know you’ve been patient and filed various issues about widgets. I just need to refresh and clarify the history and what has or hasn’t been handled up to this point. Email is brent (at) coronalabs (dot) com.

Sincerely,

Brent

#11

I also am experiencing TableView problems with the category overlaying at the top. I tried today’s build (2013.1089) and the same happens.  I have to reinstall build 2013.1072 which works, so something changed but not sure with which build.

Sometimes it initially displays ok then when moved the top category shifts into the middle (approx) of the row.

@Brent - Can you please keep the dialog going here and not where others can’t contribute to the symptoms and status?

#12

Generally speaking, it’s a real problem having features working nice on one build not working on a newer release, and it happens very (too) often. At my side, same code building a tableView is OK with DB 1088 but not with 1092… depending on number of elements in tableView.

The problem is that coming back is not allways possible. If a bug is solved in build N+1 and a new bug appears in this build or later, going back to build N is not very helphful.

Some testing at your side before releasing a new build would be nice,I understand it’s not easy but we have to rely on serious langage, not on unstable things.

#13

I believe that the category issue has been fixed in build 2013.1093.

I had the same issue, and after some investigation I found that the culprit was row.isCategory could sometimes return nil instead of a true value. I got around the issue by handling the nil return value in my event handler.