Can I publish to App store on back -level Corona SDK etc?

Solar2D General Questions/Discussion
#21

Welcome back! Great to hear that you have completed your app and sorry to hear that now you have to make it work in the current release levels. 

Since 2189 there has been some widget fixes released in the Daily builds but I don’t know if these would have resolved the issues you are seeing with graphics version 1 compatibility set to on. I think your best bet is to remain on 2189 and move your app to G2 style calls so you can do away with the compatibility mode. I think that change will greatly enhance performance and reduce the bugs that you are encountering. I am sorry to give you the bitter pill but thats how I see it coming your way. 

Fret not, there are some great libraries published by our fellow devs to support the old style position references and old style color calls in the new G2 world. Just look at the code exchange and you will see these. Using some 3rd party libs like this you can actually keep the changes in your code to a minimum and give 2189 with G2 mode a go. 

Hope this helps. Best of luck! 

#22

  1. It’s really hard to say if a daily build would fix your problems or not. The best thing to do would be to try making a smaller test project, build a table view, and see if performance/functionality differs. There may be other, undetected problems in your code and that’s the safest way to check. (Or as ksan says, try porting to G2.0)

  2. All of the setReferencePoint warnings should theoretically go away if you have compatibility mode on, I’d assume - they are deprecated but should be ok in compatibility mode. (Haven’t tested if that happens though)

  3. Your memory counts look fine. I mean, 1MB memory, less than 1MB texture memory is incredibly small…

#23

See the following thread : 

http://forums.coronalabs.com/topic/45794-tableview-positions-itself-wrong-in-10-compatibility-mode/#entry245356

I think this is confirmation that the issues you encountered in 2189 are still there in the most recent dailies. 

#24

Thanks ksan & richard9, yes this is what I had suspected, move off compatibility mode. Not sure that the daily builds will help fully yet.

As the kids on the back sit may say “are we there yet?”

I did find a bug in my code that caused most of the response time problem from all the warning messages, messages I did not get in back level and now the speed is much more acceptable.  Setreference with a nil object… 

I still have problems in scrolling and deletAll, this is changing the position of the first entry. After the deletall the insert first row shows up  in the middle of the table. I have seen this comment in the forum somewhere. I will search back through what you guys have been feeding back.

Thanks again

#25

Yes, your right again ksan, your link identifies the problem I am seeing with the Tableview

your ref http://forums.coronalabs.com/topic/45794-tableview-positions-itself-wrong-in-10-compatibility-mode/#entry245356

So this really says I drop compatibility mode and re-code what ever is needed, but will also use your recommended code-exchange libraries for setcolour and setreference initially to speed up the migration-change; later, if memory too large re-code those.

Ref Memory richard9… I spent a lot of time studying the usage and hints and tips to ensure I removed any memory variable/table/scenes whenever they are not in use. Even I was pleasantly surprised as there must be about 60 variations of screen that can be created. This stems back to my early days when the largest memory size on system controlled PCs was less than 256k, not megs, kilobytes …

:slight_smile:

Just a grumble here to Corona guys… This is just 12 months I have been trying to  use widgets and most of that debug time has been debugging Corona implementation. If the widget code had worked the app would have been in the store 9 months ago!! :angry: