Storyboard problem - Images in following storyboards do not display

#1

Hello All!

I am having problems with a storyboard app. The first scene is the splash screen and it works. Once the timeout expires it is supposed to jump to scene_buttons where it clears the screen with a background image and then puts up 4 widget buttons.

If you click a button, it jumps to another scene and then comes back to the scene_buttons for their next option.

The following link is the source and image files. If you can’t see it, let me know.

https://www.dropbox.com/sh/p13ql3q3mbwhho6/Bl05SsJQa5

For starters, the scene_buttons background is not displayed, and next the buttons are not visible. The splash image stays on the screen and the buttons are active but invisible.

Update:
I changed the view as to an iPad Retina and can see some images apparently behind the splash screen image (since it didn’t fill the screen). The buttons screen is apparently behind the splash screen, although you can click the buttons even though you can’t see them.

What am I doing wrong?

Thanks!
Stu [import]uid: 99429 topic_id: 36985 reply_id: 336985[/import]

#2

I’ve not downloaded your project yet, but what you are describing is a feature of storyboard.

For storyboard to manage anything, it has to be inserted into a specific display group that is usually called “group”. At the top of functions like createScene() you will see a line of code like this:

 local group = scene.view

This is the display group you must put your assets into if you want storyboard to swap them in and out. If you don’t any images you create will sit above storyboard and hide storyboard behind it. This is so you can implement heads-up displays like controls, high scores, etc. Things you want to persist from scene to scene.

It sounds like maybe you’re creating your splash screen in main.lua and never removing it. Normally in my case, I don’t load anything graphical in main.lua, but include a splash.lua file that is a storyboard scene. In main.lua you to a storyboard.gotoScene(“splash”) and it will show your loading screen, when your timer is up, you can have it go on to your menu scene.
[import]uid: 199310 topic_id: 36985 reply_id: 145232[/import]

#3

That’s what it does now, the problem is that the splash screen never goes away.

The second scene has the blank background and buttons to select the next option. The problem is that with the splash screen over the top of everything else, it won’t work.

You can click the area where the buttons are (although invisible) and it jumps to the third - fourth scene…

I never would have figured it would be that difficult, or perhaps I’m doing something wrong.

It is similar to layers in graphics apps except I have not used (intentionally at least) anything to make it behave like that. For some reason, the splash screen is the top layer and everything else goes under it.

Thanks for your info!

Stu [import]uid: 99429 topic_id: 36985 reply_id: 145237[/import]

#4

Thanks Rob,

That appears to be the problem. I failed to put the splash screen image in the splash group, so when that scene was taken down, it didn’t take down the image down.

Why it appeared to be on the top layer, I don’t know.

Stu

[import]uid: 99429 topic_id: 36985 reply_id: 145238[/import]

#5

I’ve not downloaded your project yet, but what you are describing is a feature of storyboard.

For storyboard to manage anything, it has to be inserted into a specific display group that is usually called “group”. At the top of functions like createScene() you will see a line of code like this:

 local group = scene.view

This is the display group you must put your assets into if you want storyboard to swap them in and out. If you don’t any images you create will sit above storyboard and hide storyboard behind it. This is so you can implement heads-up displays like controls, high scores, etc. Things you want to persist from scene to scene.

It sounds like maybe you’re creating your splash screen in main.lua and never removing it. Normally in my case, I don’t load anything graphical in main.lua, but include a splash.lua file that is a storyboard scene. In main.lua you to a storyboard.gotoScene(“splash”) and it will show your loading screen, when your timer is up, you can have it go on to your menu scene.
[import]uid: 199310 topic_id: 36985 reply_id: 145232[/import]

#6

That’s what it does now, the problem is that the splash screen never goes away.

The second scene has the blank background and buttons to select the next option. The problem is that with the splash screen over the top of everything else, it won’t work.

You can click the area where the buttons are (although invisible) and it jumps to the third - fourth scene…

I never would have figured it would be that difficult, or perhaps I’m doing something wrong.

It is similar to layers in graphics apps except I have not used (intentionally at least) anything to make it behave like that. For some reason, the splash screen is the top layer and everything else goes under it.

Thanks for your info!

Stu [import]uid: 99429 topic_id: 36985 reply_id: 145237[/import]

#7

Thanks Rob,

That appears to be the problem. I failed to put the splash screen image in the splash group, so when that scene was taken down, it didn’t take down the image down.

Why it appeared to be on the top layer, I don’t know.

Stu

[import]uid: 99429 topic_id: 36985 reply_id: 145238[/import]

#8

I’ve not downloaded your project yet, but what you are describing is a feature of storyboard.

For storyboard to manage anything, it has to be inserted into a specific display group that is usually called “group”. At the top of functions like createScene() you will see a line of code like this:

 local group = scene.view

This is the display group you must put your assets into if you want storyboard to swap them in and out. If you don’t any images you create will sit above storyboard and hide storyboard behind it. This is so you can implement heads-up displays like controls, high scores, etc. Things you want to persist from scene to scene.

It sounds like maybe you’re creating your splash screen in main.lua and never removing it. Normally in my case, I don’t load anything graphical in main.lua, but include a splash.lua file that is a storyboard scene. In main.lua you to a storyboard.gotoScene(“splash”) and it will show your loading screen, when your timer is up, you can have it go on to your menu scene.
[import]uid: 199310 topic_id: 36985 reply_id: 145232[/import]

#9

That’s what it does now, the problem is that the splash screen never goes away.

The second scene has the blank background and buttons to select the next option. The problem is that with the splash screen over the top of everything else, it won’t work.

You can click the area where the buttons are (although invisible) and it jumps to the third - fourth scene…

I never would have figured it would be that difficult, or perhaps I’m doing something wrong.

It is similar to layers in graphics apps except I have not used (intentionally at least) anything to make it behave like that. For some reason, the splash screen is the top layer and everything else goes under it.

Thanks for your info!

Stu [import]uid: 99429 topic_id: 36985 reply_id: 145237[/import]

#10

Thanks Rob,

That appears to be the problem. I failed to put the splash screen image in the splash group, so when that scene was taken down, it didn’t take down the image down.

Why it appeared to be on the top layer, I don’t know.

Stu

[import]uid: 99429 topic_id: 36985 reply_id: 145238[/import]

#11

Like I said above, it’s that way so you can do persistent things like a Heads up display, or some type of frame that’s intended to stay on top. Another example is a tabBar widget. You typically put that in main and not in a group, so the tabs stay on top.

[import]uid: 199310 topic_id: 36985 reply_id: 145249[/import]

#12

I’ve not downloaded your project yet, but what you are describing is a feature of storyboard.

For storyboard to manage anything, it has to be inserted into a specific display group that is usually called “group”. At the top of functions like createScene() you will see a line of code like this:

 local group = scene.view

This is the display group you must put your assets into if you want storyboard to swap them in and out. If you don’t any images you create will sit above storyboard and hide storyboard behind it. This is so you can implement heads-up displays like controls, high scores, etc. Things you want to persist from scene to scene.

It sounds like maybe you’re creating your splash screen in main.lua and never removing it. Normally in my case, I don’t load anything graphical in main.lua, but include a splash.lua file that is a storyboard scene. In main.lua you to a storyboard.gotoScene(“splash”) and it will show your loading screen, when your timer is up, you can have it go on to your menu scene.
[import]uid: 199310 topic_id: 36985 reply_id: 145232[/import]

#13

That’s what it does now, the problem is that the splash screen never goes away.

The second scene has the blank background and buttons to select the next option. The problem is that with the splash screen over the top of everything else, it won’t work.

You can click the area where the buttons are (although invisible) and it jumps to the third - fourth scene…

I never would have figured it would be that difficult, or perhaps I’m doing something wrong.

It is similar to layers in graphics apps except I have not used (intentionally at least) anything to make it behave like that. For some reason, the splash screen is the top layer and everything else goes under it.

Thanks for your info!

Stu [import]uid: 99429 topic_id: 36985 reply_id: 145237[/import]

#14

Thanks Rob,

That appears to be the problem. I failed to put the splash screen image in the splash group, so when that scene was taken down, it didn’t take down the image down.

Why it appeared to be on the top layer, I don’t know.

Stu

[import]uid: 99429 topic_id: 36985 reply_id: 145238[/import]

#15

Like I said above, it’s that way so you can do persistent things like a Heads up display, or some type of frame that’s intended to stay on top. Another example is a tabBar widget. You typically put that in main and not in a group, so the tabs stay on top.

[import]uid: 199310 topic_id: 36985 reply_id: 145249[/import]