Multiple Buttons Per BOG IN Scenarist 5.5

[Eric69]

Hi

Im currently working on a project which needs multiple buttons per BOG as illustrated in this tuorial:

http://www.reykroona.com/?p=52

Its needed for an Audio Select Toggle Situation

The problem lies in that I also have a CLOSE button thats needs to close the Pop Up. My buttons sometimes cant naviagte to that Close button since its either in the On or OFF state and the button cant have more than one target when adjust dirrectional the remote settings.

If someone can come up with a solution to this scenerio Id be gratefull....something small Im missing

:stupid:

[mp3dom]

I've not understand you. Do you mean the "Close" button is also a 2-state button? If it's a one state button, you can directly link your 2 state button to your close menu. Just do a direct navigation link from 1st state to the close button, then right click and choose the second state and re-do the navigation link to the close button. You need to use fake-buttons only when you need to navigate from and to a 2 state button.

[Eric69]

Thanks for the help.....

The Close Button is a one state button only. The problems is that the close button is only a one state button and can only connect to another 1 state button....correct?

Once the button next to the Close Button is in the "Off" state the Close Button will NOT navigate to it. It navigates fine once its in the "On" state.

[rik1138]

You have to do it manually in the properties window (set the navigation). You can't just use the arrows in the graphical interface, that will only apply to the top-most button in any BOG.
Click on each button of the BOG, and make sure the 'Neighbor' section of the Property window is the same for each one. That section has the upper/lower/left/right settings for each individual button.

Let me know if that makes sense... :)

And navigating _TO_ any of your audio buttons (from any other button, the Close or other audio buttons) will need to go through a dummy button to determine if it should link to the 'Off' state or 'On' state button...
I usually have a dummy button for each language (like a 'To_Eng' button and 'To_French' button), with the commands to determine if it should be going to the On or Off button for that language...

(Hehe, see more detailed info below! Posted at the same time. :) )

[mp3dom]

Ok, you need to point to a virtual button (create a virtual bog, and a virtual button inside, with auto-action enabled). For the routing, almost all "2 state" buttons needs its 'virtual button'. Every virtual button should take care to choose which of the two states you need to show to the user.
In summary:
real button "Audio 1" + virtual button 1 (that decide which of the two possible states of Audio 1 you need to show)
real button "Audio 2" + virtual button 2 (that decide which of the two possible states of Audio 2 you need to show)
real button "Close" (1 state). The Close button routes to virtual button 2 (when you press UP for example) and to virtual button 1 (when you press DOWN for example)

Virtual button 1 and 2 should have something similar to:
Virtual button 1:
If PrimaryAudio(PSR1)==1 SetButtonPage <button "Audio1ON">
SetButtonPage <button "Audio1OFF">

Virtual button 2:
If PrimaryAudio(PSR1)==2 SetButtonPage <button "Audio2ON">
SetButtonPage <button "Audio2OFF">

And so on...

Pay more attention if the buttons are for subtitles (mainly if you have more than one stream). In that case you need, prior of all, to see if subs are enabled!
Something similar to (for button of first subtitle stream):
if PSR2<=2147483647 Setbuttonpage <button1OFFstate> #no subtitles enabled, so the button is off state
MOV GPR2,PSR2 #get value of subtitle
AND GPR2,0x00FF (to have the stream number) #get subtitle number
If GPR2==1 Setbuttonpage <button1ONstate> #On state if subtitle stream is 1
Setbuttonpage <button1OFFstate> # it means we have enabled stream number 2 or higher, so actual button go in off state

Hope this helps.

[Eric69]

Thanks Guys....

Ha...what a cluster Fu**

The client has abondoned this idea for now but its something I'll work on for future projects