Graphics

Hi all-

We're transitioning our basketball arena to XPression from another system, and I'm having some problems getting my scorestrips to function properly via DataLinq and Visual Logic. I'm guessing this might be a situation where scripting will work better, but have no idea how to start in on that. We use OES scoreboards and the basic stuff (clock, score, etc.) all works fine. Here are the things I'm still trying to figure out:

1) Once a team reaches 7 fouls in the half, I need it to display a text field that reads "Bonus". Then, once a team gets to 10 fouls, I either need it to switch to a different text field that reads "Bonus+" or just add a text field that is just the + sign next to Bonus. Right now I have visual logic set up so that when the fouls equal a specific number (7, 8, 9, 10) that the text field should be visible. But nothing appears.

2) When a team gets to 10 fouls, instead of returning the number 10, the OES returns Ëš, which in turn displays on the board. How can I change this to display the number 10 instead?

3) I have two different versions of the scorestrip, for two different fascia boards. When setting them up, I copied and pasted the visual logic for how the halves display (for example, when OES returns the numerical value 3, I have a text field that reads "OT" visible.) For some reason, this works perfectly through 4OT on one of the scorestrips, but on the second one it works for OT and 2OT, and then the last two values also display 2OT instead of 3OT/4OT. I thought there might have been something that was messed up in the copy/paste, so I rebuilt the visual logic for those two and still have the same issue. Any thoughts on what could be causing that? I feel like I'm going crazy!

Thanks in advance for any help!
"‹Rob

Do you mind posting your visual logic for the 1st issue?
#XPression

I'm sure this script could be more refined but this gets it done for the fouls/bonus. Place the script below on the text object that represents the fouls. You would have to do the same for the visitors fouls. I called the text fields "HomeBonus" and "HomeBonus+".In my case I have two distinct text fields. Change this script to match your text fields that you want to turn on and off. I'm sure if you use fouls as an integer you could use >= instead of doing one logic argument for each number. But at least this way you can see how it does what it does and maybe use it elsewhere.

dim bonus as xpBaseObject
dim bonusPlus as xpBaseObject
dim fouls as xpBaseObject
Scene.GetObjectByName("bonus"�,bonus)
Scene.GetObjectByName("bonus+",bonusPlus)

if text = "7" then
bonus.visible=true
bonusPlus.visible=false
else if text = "8" then
bonus.visible=true
bonusPlus.visible=false
else if text = "9" then
bonus.visible=true
bonusPlus.visible=false
else if text = "10" then
bonus.visible=false
bonusPlus.visible=true
else if text = "*" then
text = 10
fouls.visible = false
else
bonus.visible=false
bonusPlus.visible=false
end if

#XPression

I do have a question though. Once the OES system displays the "*" the number of fouls will just sit at 10. What are you going to do with that?
#XPression

Give this a try on the period text field. This simply replaces the number in the text field so you can get rid of the "OT" text field. You would add this script to the text field that is fed by the "period" data field on OES

dim period as xpBaseObject
scene.GetObjectByName("Period",period)

if text = "3" then
text = "1OT" [LEFT]else if text = "4" then[/LEFT]
[LEFT][COLOR=#555555][FONT=Helvetica Neue][SIZE=13px]text = "2OT"
else if text = "5" then[/SIZE][/FONT][/COLOR][/LEFT]
[LEFT][COLOR=#555555][FONT=Helvetica Neue][SIZE=13px]text = "3OT"
else if text = "6" then[/SIZE][/FONT][/COLOR][/LEFT]
[LEFT]text = "4OT"[/LEFT]


end if
#XPression