Main > Software Forum
BETABRITE SCROLL SIGN IN ARCADE OS
Netcat:
Silver YOU RULE!!
I agree however the installer doesnt quite work.
Also
In my humble opinion, adding controller info to the LED sign really clutters it, can we have an option or checkbox that allows (name and description) or (Name, description controller info)
Thanks Dude.
You're the best
Netcat:
One more thing.
I am sure we are going to be getting this running with ArcadeOS and not Just MameWah.
my next step with my program weas to enable it to generate either
A. The mameWah 5000+ Files
OR
B. the One ArcadeOS file > LIST.LCD
Any chance I could persuade you to make LCDGen compatible with MAmeWah AND ArcadeOS?
I'd really really appreciate it, plus it save me a boatload of programming
MustardTent:
--- Quote from: Silver on August 15, 2005, 08:48:47 pm ---Hi,
Installer - man I've been meaning to lose that completely. Think I will just stick the VB6 runtime files and a link to the msxml installer up there. I've tried about 50 times to create a good installer with VB6 enterprise, but it only ever seems to work on the system its created on....
lost my thread in my previous post - meant to mention that I was not included any control info until I knew the basic bit worked - which it does :)
I can get it to include control data - but whats the best method - just tag it on after the name? Will BB scroll this automatically? How do they treat 'return's' (Ascii 13 or 10)? If you guys let me know what works well I can stick it in....
--- End quote ---
Silver -- just did some testing. The betabrite does not read the character \r (ascii 13) correctly, but it does recognize \n (ascii 10). Also, really long words are automatically scrolled along the sign. Multiple words are tokenized by spaces and displayed appropriately.
My vote is for support of controls info in the sign. I know your program already supports this, but just wanted to let you know people want it. I believe you already have a radio button to enable/disable, so I think we're all happy, eh netcat? :)
Hope this helps, and also I hope it helps negate some of my previous laziness :'(. If there's more testing you need done -- I'm your man.
Silver:
--- Quote from: Netcat on August 15, 2005, 09:41:37 pm ---I agree however the installer doesnt quite work.
--- End quote ---
Ok I've made one final attempt at a new install package. If this fails, I'll scrap it.
--- Quote ---In my humble opinion, adding controller info to the LED sign really clutters it, can we have an option or checkbox that allows (name and description) or (Name, description controller info)
--- End quote ---
I wondered if it would... Also thought it might be distracting to have stuff scrolling all the time - but then it is an 'Arcade at home'....
By name and description I presume you mean game name + clone info? That's already taken care of (and the tick boxes for "remove clone info" should already work in the current beta).
--- Quote from: Netcat on August 15, 2005, 09:45:26 pm ---my next step with my program weas to enable it to generate ...
B. the One ArcadeOS file > LIST.LCD
--- End quote ---
This should not be very hard to add - I'm currently not familiar with how ArcadeOS stores/expects to find the LCD info. Is it documented somewhere?
--- Quote from: pkurby1 on August 15, 2005, 10:09:10 pm ---
Silver -- just did some testing. The betabrite does not read the character \r (ascii 13) correctly, but it does recognize \n (ascii 10).
--- End quote ---
Excellent thanks...
--- Quote ---My vote is for support of controls info in the sign. I know your program already supports this, but just wanted to let you know people want it.
--- End quote ---
No problem - is it best to have it all in one line seperated by spaces or does it display better if the controls are seperated by ascii(10)'s?
I should probably go read the BBrite protocol and see what kind of display trickery it can do here.....
Silver:
Netcat - interested to know where you got the headers and enders you used in your qbasic program from.... you appear to use several "extended" asci characters (ie above ascii decimal 127) which technically fall outside the control codes of the alpha protocol (v1 of which betabrite uses). They can be used to display special characters, but you use them right at the start which would normally be where the betabrite would look for 5 NUL characters to lock up the baud rate...
Not too bothered as it obviously works as is, but just looking at the control codes for adding different display/wipe effects...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version