Build Your Own Arcade Controls Forum

Software Support => DOS/WinCab => Topic started by: Mametrix-Reloaded on December 13, 2006, 12:09:59 am

Title: Selection bounds bug and Betabrite support (Split from Tri-Vue thread)
Post by: Mametrix-Reloaded on December 13, 2006, 12:09:59 am
Not to hijack the thread but.... Chris, when I started out I was going to use numbers just because of the keypad I had. Problem was, I showed 32 selections on screen, but someone could put in 33 and it would play the song that was in the "33rd" slot which when you paged down, was in slot 00 once you changed pages.. in reality they could put in 99 and it would play song the 99th song from whatever song was in the 00 slot.

How can you get around this?

(while I have your attention, are there any plans to add support for a beta-brite, or by chance is it already there an un-documented? (second project))
Title: Selection bounds bug and Betabrite support (Split from Tri-Vue thread)
Post by: JustMichael on December 13, 2006, 04:43:51 am
Chris,
If you add a "highest numbered song" limit, could you also add a "lowest numbered song" limit as well?
Title: Selection bounds bug and Betabrite support (Split from Tri-Vue thread)
Post by: Chris on December 13, 2006, 09:38:42 am
Not to hijack the thread but.... Chris, when I started out I was going to use numbers just because of the keypad I had. Problem was, I showed 32 selections on screen, but someone could put in 33 and it would play the song that was in the "33rd" slot which when you paged down, was in slot 00 once you changed pages.. in reality they could put in 99 and it would play song the 99th song from whatever song was in the 00 slot.

How can you get around this?

(while I have your attention, are there any plans to add support for a beta-brite, or by chance is it already there an un-documented? (second project))
Really?  Hmm.... that's obviously a bug. I must have introduced it when I re-wrote the virtual changer, because the way it worked before if I had allowed such a bug through the system would have crashed.   Should be an easy enough fix...

As far as Beta-Brites and other serial devices: Yes, I most definately plan to incorporate support for external displays, but I need to rewrie the code for the internal displays first.  Once I do, the displays will all be virtualized and you'll be able to write any data to any display.  I also plan on supporting LEDWiz outputs now that I have one, if I can figure out how to do it.

--Chris
Title: Re: Selection bounds bug and Betabrite support (Split from Tri-Vue thread)
Post by: Chris on December 13, 2006, 09:43:41 am
Chris,
If you add a "highest numbered song" limit, could you also add a "lowest numbered song" limit as well?
"Lowest"?  Are you able to enter selections below the bottom and get the previous page?
Title: Re: Selection bounds bug and Betabrite support (Split from Tri-Vue thread)
Post by: JustMichael on December 13, 2006, 06:53:55 pm
No.  I meant the lowest number a selection can be (the starting number for selections). 
Title: Re: Selection bounds bug and Betabrite support (Split from Tri-Vue thread)
Post by: Kevin Mullins on December 14, 2006, 01:32:02 am
As in a "range" of selections?

Such as in my project only needing from 100-299 and that's it. (?)
(100 being the LOWEST and 299 being the HIGHEST)