Next Public Release Candidate (2014.2187)

Solar2D Daily Builds and Public Releases
#81

@Walter, were you able to reproduce the bug on S3 with the code I provide, you can also reproduce it easily on iPod 4 and iPhone 5

#82

@info0512, is this a confirmed bug with a reported bug ID or just an issue you’re currently experiencing?

If it is a reported bug, what is the bug number?

Is it happening with build 2100?

If this is not a confirmed reported bug, please start a new forum thread and let us see if it’s a local issue you are having or a bug that needs to be addressed.  Even if it’s a bug, it’s in a plugin and plugin fixes are not tied to daily/public builds.

Rob

#83

@nmichaud, Thanks for the project code. I was able to reproduce the problem in all Corona builds (include 1262 for Graphics 1.0).  I can reproduce the problem in the Corona Simulator running the Samsung SIII skin using a simple program that generates a two pixel newline and moves it around the screen.

The line width change occurs because of Dynamic Scaling. Scaling a 320x480 app to the Samsung SIII skin scales the line width to fractional values, which the OpenGL rendering engine needs to handle. The reason it shows up as an issue in your code is because of the changes in Widgets Tableview that cleaned up some formatting issues. This shifted the location of the separating lines from the previous widget builds and now these lines fall on locations that cause the issue when Dynamic Scaling is applied.

If you run your code on build 2100 or 2179, you don’t see the problem UNTIL you scroll the table. When you do that, you see the same issue with the lines stroke width increasing and decreasing as it moves up and down the screen.

Trying to get everything “pixel perfect” when Dynamic Scaling is used, is a hard thing to do and not sure what we can do to make it right and handle all scaling situations.

#84

I wouldn’t release to the public until you fix this MAJOR ISSUE with EFFECTS it is a show stopper in my book, to the point that if it takes to long to fix I am moving to another engine (which sucks because I just renewed yesterday grrrr) (yeah i am a little pissed over this one)

http://forums.coronalabs.com/topic/45048-fill-effects-and-newimage-or-newrect-with-image-fill-broken/

#85

Hello:

  I try to build a device build with 2187. And I found “facebook.lua” is not there?!

  1. Device:   iPad
  2. OS/Version:  iOS 7.1
  3. Sample files:  first two line in app just cannot work

local facebook = require( “facebook” )

facebook.publishInstall( “14306335638xxxxxx” )
4. Description : first two line in app just cannot work
5. Bonus : I try build 2169 and no problem

Bob

#86

@bob Do you have Facebook listed under plugins in build.settings? It’s a new requirement. See gotchas here http://docs.coronalabs.com/daily/api/library/facebook/

#87

@Tom, thanks for the explanation, but why in that case the line separator provided by the list is always good regardless of the scaling ?

#88

Any updates on when can we expect a fix for this one?

ZJ

#89

Nmichaud, as a quick workaround, use a newRect as separator instead of a newLine. I just tested that.

alex

#90

Thanks Alex,

We are going to give it a try :slight_smile:

#91

Guillermo,

The bug you reported was fixed in today’s daily (2014.2188). All the other issues you have pasted (the forum threads) refer to now solved issues.

Thanks,

alex

#92

@alexf I’ve made some test with the latest build and now it’s working perfectly. Thank you!

#93

@GuillermoFG: Sure thing. Glad to help.

alex

#94

@jonjonsson: Thank a lot. It works.

Bob

#95

@alex will transitions fixes be included in the public release?

#96

@primoz.cerar Yes.

#97

@GuillermoFG: Thanks for your persistence! The transition bug was a show stopper for me.

@alexf: http://forums.coronalabs.com/topic/44763-why-my-simple-code-leaks/ was also related to the transition bug and have been fixed in 2014.2188. Just tested and no problems anymore. So Bug case 30859 can also be closed. It was a major issue for me so thank you for fixing it!

#98

@polygonblog: always welcome.

alex

#99

Super. 2189 is looking real good. Seems like a lot of fixes went into it at the last minute which is wonderful. 

Quick question on the storyBoard bug reported by Guillermo. I am glad to see this one fixed as opposed to saying we don’t support storyBoard anymore… Will this also mean a refresh to the storyboard code on the GitHub?

Thank you very much. 

#100

@kerem: No storyboard update needed, the issue was not in the storyboard framework, but in the transition framework.

alex