Software Support > DOS/WinCab
wincab 3.0b11 radio/random button bug? + clearqueue bug
Chris:
--- Quote from: Cadder on September 20, 2006, 08:51:19 am ---OK :-[ problem solved. I had the Xarcade set to a different mode, and the offending buttons were all programmed to be a "C".
Shoot me now. :banghead:
--- End quote ---
Great to know!
--- Quote ---1. There seems to be a difference between 3.1.1 and 3.11b, in that all of the song titles now appear in upper case, and between quotes "LIKE THIS"
The artist appears fine, in normal case.
Is this a new setting I've missed?
--- End quote ---
Actually, this is an old setting that was broken in b11 and fixed in 3.1.1.
The "old way" to do this will be found in all the skins except default.skn and cd4-1.skn. Look in the [Titlestrips] section and you'll see:
--- Code: ---# If AddQuotes is set to True, song titles will be
# displayed in quotes. This was a common practice on
# old jukeboxes; it is less common today.
AddQuotes=True
# If ForceUpperCaseTitles or ForceUpperCaseArtists is set
# to True, song titles or artist names on the title strips
# will always use uppercase. This was a common practice
# on old jukeboxes; it is less common today.
ForceUpperCaseTitles=False
ForceUpperCaseArtists=True
--- End code ---
The "new way" in default.skn and cd4-1.skn has a new [Fonts] section that looks like this:
--- Code: ---[Fonts]
# Note: The "Small" fonts are not yet implemented.
TitleFont = bluehigh.ttf
TitleFontSize = 26
TitleFontCondensed = bluecond.ttf
TitleFontCondensedSize = 24
TitleFontSmall = bluecond.ttf
TitleFontSmallSize = 13
TitleFontColor = Black
TitleFontCase = UpperCase
TitleFontAddQuotes = True
TitleFontQuoteSymbol = "
ArtistFont = bluehigh.ttf
ArtistFontSize = 22
ArtistFontCondensed = bluecond.ttf
ArtistFontCondensedSize = 18
ArtistFontSmall
ArtistFontColor = Black
ArtistFontAddQuotes = False
TitleFontCase = Normal
--- End code ---
So you'll be interested in the AddQuotes and Case settings.
--- Quote ---2. I seem to have lost mouse control. It worked in 3.11b but not 3.1.1.
The cursor appears, but doesn't move.
--- End quote ---
There are two different alleg42.dll's based on which version of Windows you are using. The default alleg42.dll only supports Windows XP; you'll need to rename it to something else and rename alleg42-98.dll to alleg42.dll in its place.
--- Quote ---I also found a "free credits" bug that I'll start a separate subject for...
--- End quote ---
Interesting. There is only one way I know of to get free credits, and that's to set the juke to Free mode, queue up a bunch of songs, switch to Credit mode, and clear the queue, as you'll get a credit back for each song in the queue...
Chris:
Oh, by the way: In your control map, it looks like you've rotated your GUI inputs to match your screen. The jukebox should do this for you, so BTN_GUI_DOWN should always go toward the bottom of the skin, not the bottom of the physical screen. Is this not working properly? (I'm at work so I can't try it now...)
Cadder:
Oh! yeah, I forgot to mention that. The GUI motion buttons stay aligned to the physical screen, not the logical (rotated) one. Same as the mouse. (I have to hold it sideways)
Also just to clarify, the alleg42 under win2K: I need to use the '98 version?
Cadder:
I'm using win2K SP4. The mouse won't move no matter which alleg42 I use.
:(
Chris:
--- Quote from: Cadder on September 20, 2006, 10:11:23 am ---Oh! yeah, I forgot to mention that. The GUI motion buttons stay aligned to the physical screen, not the logical (rotated) one. Same as the mouse. (I have to hold it sideways)
--- End quote ---
Well, the keyboard not re-orienting is a bug; I haven't figured out how to re-orient the mouse yet.
--- Quote from: Cadder on September 20, 2006, 10:28:01 am ---Also just to clarify, the alleg42 under win2K: I need to use the '98 version?
--- End quote ---
Yes... in this case 98 actually means "Not XP".
--- Quote ---I'm using win2K SP4. The mouse won't move no matter which alleg42 I use.
:(
--- End quote ---
Ouch. Hmm. I have a Win2K test box at home, I'll take a look. (I've been at work for 28 hours now, though, so I have no idea when "at home" will be or if I'll be sufficiently awake to write code... LOL )
--Chris
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version