Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

composer.showoverlay comes up in background
Started by laurasweet8888 Nov 27 2018 05:57 AM

2 replies to this topic

Best Answer laurasweet8888 , 27 November 2018 - 06:34 AM

OK,  I changed this:  display.getCurrentStage():insert( UI.frontGroup )

 

to this: WorldGroup:insert( UI.frontGroup )

 

where WorldGroup is my the base set like this: local WorldGroup = self.view -- add display objects to this group

 

and all my problems went away.  

 

I really have to stop copying code out of the sample programs :)    

 

[TOPIC CONTROLS]
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

laurasweet8888

[GLOBAL: userInfoPane.html]
laurasweet8888
  • Contributor

  • 110 posts
  • Corona SDK

I have used showoverlay before and it worked as expected.  But this time when I call it the scene loads behind my current scene.  At first I didn't think it was doing anything at all until I set my current scene elements to transparent.  Then I could see the overlay in the background. 

I have racked my brain and can't figure out what could cause this.  I also set model=true and my my current scene buttons still function.  It is all very strange.  I am looking for ideas to chase down.   Thoughts?  

 

L



[TOPIC: post.html]
#2

laurasweet8888

[GLOBAL: userInfoPane.html]
laurasweet8888
  • Contributor

  • 110 posts
  • Corona SDK

  Best Answer

OK,  I changed this:  display.getCurrentStage():insert( UI.frontGroup )

 

to this: WorldGroup:insert( UI.frontGroup )

 

where WorldGroup is my the base set like this: local WorldGroup = self.view -- add display objects to this group

 

and all my problems went away.  

 

I really have to stop copying code out of the sample programs :)    

 



[TOPIC: post.html]
#3

davebollinger

[GLOBAL: userInfoPane.html]
davebollinger
  • Corona Geek

  • 1,259 posts
  • Enterprise

as long as you keep the display hierarchy in mind you can "safely" do this either way (above or below other display elements, as desired)

 

display has one and only one (at present, though they leave this "open" for future) "stage" (which itself is just a DisplayGroup), accessible via the method display.getCurrentStage()

 

when Composer is loaded, it's creates its own "stage" (which is a DisplayGroup) as a child of the display stage, accessible via the property composer.stage.

 

when scenes are created, they each have a "view" property (which is a DisplayGroup) which is a child of the Composer stage, layered in the order of scene creation.  "normal" use of Composer will properly handle the layering of any active scene.view's, so as long as all "scene content" is inserted into the scene's view, then inter-scene element layering is also properly handled.

 

"wrongly layered" elements are typically the result of either

1) failing to insert into ANY group (which then defaults to the display stage, so on top of everything else already there)

2) inserting into the WRONG group (which could place it above/below other elements, depending on where that parent group is)

 

but also, maybe,..

3) loading Composer "late" (after other groups have created in the display stage, so composer.stage will be on top of all of them) and then failing to "rearrange" the set of display groups as actually desired afterward




[topic_controls]
[/topic_controls]