The NEW Build Your Own Arcade Controls
Main => Audio/Jukebox/MP3 Forum => Topic started by: ArcadeFX on June 03, 2002, 03:45:58 pm
-
JukeboxFX Bets 0.05 Released
- Major bug fix to the visualizations. Runs 100% better now.
- Added 3 additional visualizations
- Help section has been added.
- Many UI updates.
- ID3 tag editing improvements.
Download the latest version today. http://www.move360media.com/mame/arcadefx/index.htm
-
Pretty spiffy Jiffy, although, out of curiousity, do you have an ETA for 640x480 Resolution Support on it, as well as with ArcadeFX... they both look to be beautiful programs and I love nice graphix on my Arcade cabinets which is why I was curious about VGA 640x480. I know there was talk about it a while back either here or on your MSG board, so I was just wondering... Thanks much kindly.
mS
-
I have not planned a 640 x 480 UI yet but it should not be too hard. Just need to make a few changes.
-
I will add 640 x 480 and see how much it increases the file size. If it is too big I will just make a new exe for it and have two download.
Huh? I'm just curious, but why would it increase the file size? Don't you just scale everything?
-
No, I don't scape the images. Raster images do not scale very well as compared to a vector format image. Scaling a raster images makes it look like your image got hit with an ugly stick. I don't own an ugly sitck.
But is it not the size of the graphics that will increase the file size. It is the addition of the code/logic to resize the display and move UI objects around the screen for each resolution.
-
Oh I know they can look horrible, but I do it anyway... Thats also why I keep my image files external to the program, that way once the user gets his cab setup he/she can resample the images to the appropriate size.
I'm not quite sure what you mean by extra logic. Here's what I do: (I realize it's a different coding lang., so it'll be different.)
You take all the objects on the form and upon initilization you actually place/resize them. You place them not in actual pixel values but as a percentage of the total screen size. Before you place anything you call GetSystemMetrics to get the screen resolution and manually resize the form to the screen size. Now you place everything in relative position to the height and width of the screen. Once your done make the form visible. Now your app instantly supports any resolution!
Once again I don't know if the language your using supports such functions. I realize it's a pain to code this way, but it makes it easier in the long run. When I wish to add something I don't have to fiddle with it's size and shape, I can just plop it on the form, assign values to it, and it'll take care of the rest.