categories screen name in VideoPlayer

Archived
1

I cant figure out how to get back to this screen using a button…

i have tried


showHomeScreen()

showHomeScreen(screen)

But neither work…

i have a welcome screen then on their i have 2 buttons
1.) more info
2.) start watching

well I was able to get the more info to send back to the welcome screen but then the

“exit while”

that would normally take me to the categories screen, just takes me back to the more info screen.

i even tried this but just makes a loop!!


    showWelcomeScreen()
    showHomeScreen(screen)
    showMoreInfoScreen()
    showHomeScreen(screen)

and yes i have read the docs but I cant find it anywhere

2

I have even tried adding another Fake screen to get this to work too…

it does the same thing. anyone got any ideas?

i also tried adding a fake home screen but that didn’t go well wither, i would love to find out about this as well…

Chad Socolovitch

3

Thanks Chris, i think i got it fixed!!

for anyone else having this issue, it comes down to being sure that the screen closes, behind you each time.

to do that you have to break the event loop so what i did and is working at this time.

is add EXIT WHILE after each command like this

while true
msg = (wait 0, screen.Get MessagePort())
if msg.isButtonPressed() then
   if msg.GetIndex() = 1
show welcomeScreen()
exit While
   end if
if mgs.GetIndex() = 2
showWhatever()
exit while
    end if
  end if
end while
close.Screen()

this is just an example, but gives you an idea, that each time i break out of the WHILE loop and it still reads the screen.Close()

hope that helps

this could be wrong and anyone feel free to pipe in if it is.

4

well its buggy!

when i get back to the welcome home facade screen it gets hung up on the button (page) i just came from.

i might have to move it twice to get it to go to to the START button to continue.

but im off to bed and have no way of fixing it before the deadline so i guess its stuck on this release till i can figure out what its doing

5

The navigation order of screens naturally follows a stack. It is best to structure your code with a function for each screen. The function should set the screen up and then execute an event loop. That way when you exit the event loop, the firmware’s internal currently displayed screen stack will match the event loop from the next function on your BrightScript call stack.

Any other navigation order of screens other than a stack calls for sophisticated programming skills, and a management of references to screen objects that you can explicitly call Close() on.

–Kevin

6

Kevin,

I have closed each and get back to the screen as needed but its still acting odd with the buttons on the welcome screen.

so if i got 3 screens away and i hit the “go home” button. it will take me back there no problem…
it appears to close all the screens behind me but then when i hit the start button it takes 3 clicks and/or going back up to start before i can actually start…

i will upload the package and let you see it, its hard to describe

7

Great I upload another package and its doing the same thing over, just starts to open and then closes…

and i checked over everything before packaging it and it was working…