Build Your Own Arcade Controls Forum

Software Support => DOS/WinCab => Topic started by: wrooster on February 19, 2007, 08:35:53 pm

Title: Default skin not working at 800x600
Post by: wrooster on February 19, 2007, 08:35:53 pm
There are a few others that do not work as well. Anyone have experience with this issue?
Title: Re: Default skin not working at 800x600
Post by: Chris on February 19, 2007, 08:48:39 pm
Not work in what way?
Title: Re: Default skin not working at 800x600
Post by: wrooster on February 19, 2007, 09:02:24 pm
At 1078 I've never had a problem with any of them, but at 800 the default skin (my favorite, by the way) will not allow the program to load. The screen flickers, and then I pop back to windows. When I use bjrock28, I don't have the problem, it loads normally.
Title: Re: Default skin not working at 800x600
Post by: Chris on March 05, 2007, 10:48:42 am
My apology for the delay getting back to you.  Can you set DebugLevel to 5 and post the resulting jbdebug.log file?

Thanks!

--Chris
Title: Re: Default skin not working at 800x600
Post by: welshmark on March 31, 2007, 10:03:20 am
I had this problem running at 1024x768 resolution on one of my old computers.  The "default" skin and "classic" wouldn't work (threw me back to windows), but aj28 and chrome would.  The skins worked fine on my other machines.  Changed my debug settings to 5, but didn't see anything out of the ordinary in the log.  After a bit of playing around, I figured out it only happened when the background image (bgmain.jpg and bgclassic.jpg in this case) were larger than my screen resolution (both were 1024x1024).  I pulled them into Paint Shop Pro, cropped them to 1024x768 and it fixed the problem.  Had to realign the buttons, but once I did that everything worked great.

PS. IMHO Wincab is the best jukebox program out there - I use it all the time.  Great job Chris!!!  :cheers:
Title: Re: Default skin not working at 800x600
Post by: Chris on March 31, 2007, 01:39:36 pm
They are larger on purpose; this allows them to be used both horizontally and vertically.  The jukebox calculates the appropriate window and crops on the fly.  The fact that manually cropping it yourself fixes the problem implies that there's a memory leak or boundary error somewhere in the skin reader.  This would also explain why some resolutions show the problem and others don't.