GUIntv

[GUIntv]

Sknight,

 

I see what you mean by the "Additional Parameters" box. If I implement something like that in GUIntv, I'd probably add an option called "Open With Flags" to the File menu. Open With Flags would open a window with a text field where unsupported flags could be entered before selecting a game. I don't think it will be difficult to code, but it's something I'll look into more after I finish the keyboard hack file GUI.

 

Out of curiosity, what Mac were you using when you needed to manually set audio parameters? The main reason I wasn't planning on supporting more flags is that most of them seemed designed to coax more performance out of slow machines. Seeing as GUIntv 2.0 and newer require at least Snow Leopard to run, I figured that the default hardware settings weren't going to be a problem for anyone.

Hi zagnalopius,

 

First of all, sorry for the lack of news from my side...

 

Something like you proposed ("Open with Flags" option) would be great!

As for your question I had to set up the audio parameters manually when I tried jzIntv on a hackint0sh, due to the some issues with the audio driver at that time. In fact such parameters have never been necessary on my real Mac (a Macbook Pro).

I would like to take this opportunity to wish you and everybody here a Happy New Year!

 

Keep up the great job!

[GUIntv]

Hey Sknight,

 

I just tried out your build of SDL and it works perfectly. Thanks a lot for posting it for everyone! If you don't mind, I'd like to include a link to in the next version of GUIntv.

 

No problem at all. Feel free to include a link to my binary! However, in order to comply with the LGPL license, please include also the links to the original source code and the patched file:

 

Original source code: SDL-1.2.14.tar.gz

Patched file: http://www.whpress.c...L_QuartzVideo.m

 

Regarding suggestions one and two in your post above, I didn't realize that specific file names were only necessary if the ROM's file paths weren't specified. I always thought jzintv required the system ROMs to be called "exec.bin" and "grom.bin" , so I designed the interface accordingly. Since there's really no need for a central Intellivision "system folder", I'll probably redesign the interface for the next release. I don't think I'll scan the system for ROMs, but I'll add controls in the preferences that let users specify separate paths for jzintv, EXEC, GROM, and ECS files.

 

Great! As a matter of fact, I've just seen in your last post (regarding GUIntv v2.5) that it will be possible to select different paths for every system file!

 

As far as suggestion number three goes, my main reason for writing GUIntv was to make it easier to play Intellivision games on OS X, so I'm trying to keep everything as simple as possible while providing the controls most people will want to use regularly. Personally, I don't see the use for most of the unsupported options except maybe rate control and the debugger. That said, I appreciate your interest in my project and if there are any features of jzintv that you think GUIntv should support, please let me know, and I'll see what I can do about adding them to a future release.

 

My suggestion was to implement something like the "Additional Parameters" box found in the jzIntv Launcher for Windows: jzIntv_Launcher_jzIntv_Launcher.jpg. That way your application would be more flexible letting the user specify extra parameters when needed. Some time ago (when running jzIntv on another machine) I had problems with the audio and I had to play with parameters like "--audiorate" and "--audiobufsize" to fix it, for instance.

 

Keep up the great work!

[GUIntv]

Hi guys,

 

I was able to build the SDL.framework with Xcode using the patched SDL_QuartzVideo.m file (for Lion fullscreen compatibility)!

For those who want to give it a try, here is the binary: http://goo.gl/Pu6V0. Just unpack it and copy it to /Library/Frameworks (repair owners permissions if necessary).

 

Enjoy it!

[GUIntv]

Ok, I think i've fixed the problem. Lion can't handle Applescript's beep command if it's used from Applescript Objective-C. I was trying to use beep to play a sound every time an alert dialog appeared and it was messing everything else up. That explains the issues Lion users were having, but what's really weird is that supposedly it wasn't a problem for everyone. I have no idea why.

 

GUIntv should work fine now, but during my recent testing, I've found an issue with jzintv and Lion. If you try to run jzintv in fullscreen mode on Lion, the screen goes black as usual, but instead of starting a game, jzintv quits with error 1010. The screen switches back to the normal Mac screen, but leaves behind an odd black window that floats over everything else. It can be moved, but the only way I've found to get rid of it is to log out.

 

It's not a bug in GUIntv because I have the same problem running jzintv directly from Terminal, so I think it's either an issue with jzintv or the current version (1.2) of the SDL framework. I tried using a few different builds of jzintv and got the same result. I also tried to build the newest version of SDL with Xcode but couldn't get it to work. If anyone can test GUIntv with version SDL version 1.3, I'd be interested to know if whether or not that helps.

 

Anyway, here's GUIntv version 2.1 for you to try. As usual, please let me know if you find any bugs. I'm also attaching a picture of the error message and black window that appear when I try to use fullscreen mode on Lion. Does anyone have any insight into why this is happening?

Hi Allen,

 

First of all, thank you so much for GUIntv. Sometime ago I have written an Applescript similar to yours (although it was simpler) but I never disclosed it because it was in alpha stage (however it worked fine for my personal purposes)...

 

I would like to take this opportunity to suggest some new features to GUIntv (based on what I have implement/intended to implement to my script):

 

1. Set a different directory for the jzintv executable. I don't think most users keep it with Intellivision system files. In my case, for example, it's in /usr/local/bin directory;

 

2. Ask the user to select the system files individually (so the files could have different names instead of ecs.bin, exec.bin and grow.bin). Another better option would be to scan the system directory and identify the files automatically based on the md5sum (for instance);

 

3. Allow the user to specify extra flags to jzintv (so the user could pass to jzintv parameters not supported by the graphical interface).

 

As for the fullscreen issue, Lion broke the compatibility with SDL 1.2 fullscreen support: http://forums.libsdl.org/viewtopic.php?p=29146. However there is already a fix for it: http://forums.libsdl.org/viewtopic.php?t=7527. I've just tried it and it worked fine! However I had to recompile jzintv to support SDL Unix style (instead of SDL framework) because I don't know how to build it properly with Xcode (I'm a Xcode newbie).

 

Thank you again for GUIntv. Keep up the great work!