@davidcondolora and @roaminggamer, thanks very much for your invisible object suggestions. I’ll check those out.
@davidcondolora, re: anchorX/Y … WOW! That’s a beautiful sight :) All realigned and relatively painless. Thanks so much!
Only 2 mod-tranistion problems left, opened new thread here:
black rectangle fades in/out of upper-left-screen quadrant on opening any lua file (module)
a broken video (mov) transition
@beernathan: Any luck on any of this? Due to the IDFA issue I too am likely going to have to update my game to Graphics 2.0, and the compatibility mode leaves much to be desired. All of the transitions happening (Graphics 2.0, Composer) around the release of my game have left me frustrated with Corona.
Hi @davidcondolora,
Frustrating for me too - no reply from @Rob-Mircale. feel like I can’t progress without some direction here as Corona is not behaving as per the documentation.
I’m confused about why with Graphics 1.0, your text block is drawing where it is.
If you use the old style text creator: local mytext = display.newText(“somestring”, 100, 100, 200, 100, native.systemFont, 14)
Then there is no difference between G1 and G2 in graphics compatibility mode. But when I use the display.newText() in the new way, it’s not drawing in the right place with your G1 method. The red dot represents 100, 100 on your screen. The display.newText() you are telling to draw it’s top left corner at 100, 100, which under G1 it is not. It’s centering the block on the X axis. I don’t know why the Y axis is drawing as high on the screen as it is. It’s almost like it’s got a :setReferencePoint() on it or it’s like the display.newText() in the new mode is behaving like it should in G2 mode.
I would say the G1 version with the new style is a bug. The way it should work in G1 and G2 with compatibility mode is that you should get a 200x100 box. The text should be centered in that box and then the top left should be at 100, 100.
In G2 without compatibility mode, that block should be centered at 100, 100. Which is what looks like is happening in G1 builds.
Hmmmmm. OK thanks @Rob-Miracle - so if I read your comment right, you’re saying G1 with the new style had a bug in it, and that G2 with compatibility isn’t compatible with that G1 bug 
I’m happy that at least i know that - it’s a much more solid foundation for me to move forward on, as I can update my “new style” calls across the board to make them compatible with “G2 compatibility mode”. At least then I can move onto a current release before I make the big jump to G2.
That’s what it would appear to be. G2 is working as it supposed to.
Rob
Rob will be happy to hear that I’ve finally made the leap and implemented G2.0 with compat=1 to get me up to the current version of Corona. There were *lots* of pitfalls - porting to compatibility=1 is not as easy as it sounds. I’d be happy to write up the challenges, but I figure I’m one of the last on G1.0 - if there’s a need let me know and I’ll write it up.
Thanks,
Nathan.
@beernathan: I wouldn’t mind hearing about the challenges. I went through basically all of the process before hitting some show-stopper problems (which Corona helped me get past), but I haven’t gone back to it since, as I was able to submit with G1.0. But I will eventually have to modernize like everyone else, so any insight is helpful!
@Rob, I’m running graphicsCompatibility = 1 now, and trying to transition to 2.0. I think the only offending thing that I’m using is setReferencePoint. All of my objects are center referenced like this:
[lua]
local label = display.newImageRect(“images/label.png”, 100,100);
label:setReferencePoint(display.CenterReferencePoint);
label.x = 646; label.y = 706;
label.scene = “label”;
[/lua]
Based on what I’m reading, it looks like all I need to do is remove the setReferencePoint line of code for each object. Is that right?
That should take care of it. We also dropped out the legacy sprite library with the Graphics 2.0 build. If you need it, you can download ti from github and just drop it in your folder and won’t miss a beat.
Rob
So the big changes were…
Text edit - needs to conform with the new widget.
Buttons: Having alpha=0 was OK before G2.0, but now it acts like isVisible = false, so you need to have an alpha greater than 0 if you want it to receive touch or tap events.
Text: If you use the new style of text creator (which has alignment) then you need to change all x,y coordinates used on creation to establish position - they are now top left (were mid points)
ScrollWidget: A couple big things changed. The coordinates of items in the scrollview are now relative to the whole screen - used to be relative to the scrollview group only. Also (and this took me ages!) when created they scroll a little down (or right, depending on the scroll axis). When you grab them and they bounce back they are fine again. The only way to resolve this was to use a scrollToPosition command when first showing the scrollview - this resets the scroll the first time, and it’s fine from there on…
That’s what I had noted down - could be other surprises though
Nathan.
Nate, buttons/objects should have zero alpha (or make them is visible = false) if you want them to recieve touch events but not have them visible.
You should use the property “isHitTestable” to allow them to recieve touch events.
i.e.
MyButton.isHitTestable = true
@beernathan: Thanks for the write-up! I had no idea that alpha = 0 now acts like isVisible = false. I usually use isVisible and isHitTestable, but odd that they changed the alpha behavior. Thanks!
@Rob,
Thanks very much. Mostly ok, but several Problems
Currrent stand out …
Corona staff have consistently recommended that I create a series of rectangular, hand-coded, overlay objects to distinguish user touches on irregular-shaped juxtaposed objects. The 50 visible objects were center referenced; they’re fine. The ‘alpha = 0.01’ overlays were upper-left xy referenced. All 100+ have shifted out of place.
I’ll include sample code for one overlay. Tried to include a pic but can’t find the accepted file format.
Do you you know of any search-and-replace-based syntax assignment to easily readjust their new centered location to their former upper left xy location? Or, worst case, can you recommend a clever algorithm to recalculate the values?
[lua]
me_shape_1 = display.newRect( 835, 100, 57, 60 );
me_shape_1.alpha = .01;
me_shape_1.order = 1;
me_shape_1.match = me;
me_shape_1.isMask = true;
[/lua]
Thanks.
Np 
@Ibolduc: I just went through the same ordeal. Anywhere you use display.newRect, if you expect it to be Top-Left aligned, you’ll need to manually anchor it to top left. My recommendation is to include this line after you create the object:
me\_shape\_1.anchorX = 0; me\_shape\_1.anchorY = 0
Positioning should work as expected from here, now that it has a top-left anchor point.
I believe that .alpha = 0 has always prevented touch events unless .isHitTestable is set.
Rob
I noticed you mentioning using alpha 0.01 for your your overlay (invisible) touch objects.
My assumption is you want the overlay to act as a touch object but to not be visible to the user.
Might I suggest one of two better options?
Use a fully transparent (alpha == 0) rectantgle and set the isHitTestable attribute to true. Why? In my experience, previously using your technique over several devices, I found that sometimes low alphas got treated like zero alpha and thus no touch was recorded. Also, sometimes even low alphas are visible, thus creating ugly artifacts.
Use an imageRect and fill with a fully transparent texture. I use this solution exclusively now. In fact, all my projects keep two textures:
When prototyping and debugging I use fillW.png for my (later to be invisible) touch objects/helpers so I can see them, position them, and verify their placement. I may set the alpha to 0.5 and colorize them too based on my debugging situation.
Then, after I’m satisfied, I change the fill texture to fillT.png and bingo, an invisible touch object that always works.
I hope this helps.
Nope - my game had been in production for nearly a year with alpha=0 - I’ve never used isHitTestable. Perhaps the default for isHitTestable changed between G1.0 and G2.0.