|
Post by patrickp on Aug 15, 2006 16:56:34 GMT -5
That's right, those options were in the switch list for pSX 1.0, Ultima. At a guess, w would be width (in pixels?) and h would be height but d? d would suggest depth (colour depth?) but I don't see any point in setting this for pSX. Most likely refresh rate? A moot point anyway since this switch is no longer in the list, as you pointed out.
Ah! When you said you'd fixed it, I assumed you meant in the current version. As I said, there is a workaround in that you can make sure the last folder you select (i.e. for the emulator executive) is the pSX folder - assuming you have the frontend in that folder, too.
Yes, on this side of the Atlantic we tend to use flash rather than flashy - as in 'flash git' or 'flash Harry.'
|
|
|
Post by Ultima on Aug 15, 2006 18:28:50 GMT -5
Yeah those were my assumptions as well (w = width, h = height, d = depth), but it didn't seem to make a difference whatever setting I used. To me, flash is either a noun or a verb... doesn't sound like an adjective at all... Oh well
|
|
|
Post by pSX Author on Aug 15, 2006 18:55:45 GMT -5
Yeah - that command line option was left over from much older versions of pSX - years before I released it... I forgot to remove it for 1.0 (I did a massive amount of tidy up leading up to the release and thats something I missed) - it didn't do anything in 1.0 afaik.
|
|
|
Post by Gamesoul Master on Aug 15, 2006 19:44:16 GMT -5
Ultima: Well, wouldn't you know it. The Windows API is written in C, so the syntax is almost exactly the same (lightly modified to conform to Basic). This following Basic function will write the specified value of the specified key to the specified section of the specified file (.ini). Keep in mind that, just as in C/C++, you have to provide the full filename (that includes the whole path), but I think you must already know the function to retrieve the current directory, so I guess just concatenate "psx.ini" to the end of the string returned for currentDirectory. You'll have to set that equal to a proper number variable to catch what it returns (which is a zero if it fails, and a non-zero number if it succeeds). This is the exact equivalent of the function I use to write the .ini entries. There is a GetPrivateProfileString function also, which requires a couple more arguments to pass, but they are the same (and in the same order) as the C/C++ equivalents, as described by pSX Author at the end of the first page of this thread. It seems that soon, my frontend will become obsolete. I am glad, however, to have been able to give this idea the attention it deserves, and if anybody wants my source code for a few laughs, just ask. Very nice frontend, Ultima. I'm sure you'll have it working to its full potential in no time.
|
|
|
Post by Ultima on Aug 16, 2006 0:37:33 GMT -5
Aw, I didn't mean to steal your motivation with my version... Sorry 'bout that rapidshare.de/files/29569530/pSX_Frontend_v1.02.rar.htmlKnown Limitations ================= - You cannot use a custom BIOS in a profile shortcut
History ======= v1.02 (2006-08-16) + Ability to create a shortcut based on current profile + Ability to select BIOS + Use psx.ini for paths if it exists ~ Remember last used directory when selecting files ~ Renamed the previous "Advanced" tab to "Switches", reserving the "Advanced" tab for other stuff (so far, only the BIOS selection) ~ Save psxfrontend.ini to same directory as frontend ~ Tiny fix for Restore Last Session menu item (took 3 clicks to enable if it was disabled at start) To be honest, I haven't had done enough testing on the frontend, so I can't be sure everything's in working order (especially the BIOS selection, it's raw and can be dangerous ). The concepts seem to be right in my head though, so that's (mostly) how I'm moving along (threw in some minor tests here and there). Sorry for making you guys my guinea pigs Edit: I'm stupid, and my readme file was missing stuff or was incorrect... reuploaded -.-
|
|
|
Post by Gamesoul Master on Aug 16, 2006 6:34:40 GMT -5
Your list of BIOS looks oddly familiar... Don't worry about "stealing my motivation". I'm really stuck in terms of writing the damn GUI, else it'd be a great contender to your frontend. I even have all the non-GUI parts written (and very little GUI code that I *do* know). Oh well... maybe someday I'll finish it (of course by that time, I better make sure everything I can think of is implemented XD). Was the function I gave you any use, or did you have that handled already? I ask because if you're using the function, there is no "danger" with the BIOS selection, as the change to psx.ini is very clean and simple, with virtually no room for error (and even if there's somehow an actual error, pSX will default to SCPH1001.bin in the default directory anyway). Known Limitations: - Doesn't seem to read *any* paths from psx.ini (instead, reads it's values from its own .ini file, which doesn't exist upon first use)... not any kind of issue except for first run - Doesn't accept any kind of relative pathnames (I wouldn't bring this up, except I know 100% that this can be easily implemented) - If the last limitation is resolved, there will no longer be an issue where full pathnames (spaces and everything) can't be used (as my program proves) Other than that, everything seems to work as it is supposed to (I tested a bunch of BIOS files, as well as command-line options, game-loading, profile loading/saving, and creating shortcuts... pretty much everything I could think of. Requests/Suggestions: - When a required value is missing (mainly the program path for the emulator), it should have a function to fall back on that searchs the current directory (and/or default directory, which would be an extension of fixing the related limitation listed above) for the missing item before returning an error message to input the correct path. - Also, I'd request changing "Restore Previous Session" from being a menu toggle option, to instead be a button that calls a function to load the settings saved upon exit the last time it was used. Or better yet, just *always* load the settings from the previous session (meaning settings would have to *always* be saved upon exiting the app), and add an option to clear the current settings. Keep up the good work!
|
|
|
Post by patrickp on Aug 16, 2006 7:20:12 GMT -5
Hm, rapidshare doesn't exactly seem to be the most obliging of hosts: "You have requested the file pSX_Frontend_v1.02.rar (131 KB). This file has been downloaded 4 times already. "You have reached the download-limit for free-users." Waaaah! I wannit! I wannit! I wannit! How about trying www.hostfile.org/index.php? Someone here recommended it before; can't remember who or where... but they do .exe files and .rar and.zip files. Incidentally, did anyone notice WinRAR's free offer of WinRAR 3.51 a week or two back? I bought winRAR a few years back, but now my spare machines and friends all have 3.51. ;-D TBH, looking at Ultima's v1.01, I don't really think a more sophisticated GUI is really necessary: it's already well useable. BTW, will the v1.01 .ini file work with v1.02, Ultima (bet you've said in the readme and I haven't bothered to read it yet... :/)? Well, I did just read it, it's looking really impressive. How about having it read _from_ as well as to shortcuts? I already have a slew of them, and if it saves me setting them up all over again... well, you know how ineffably - er - laid back I can be...
|
|
|
Post by Ultima on Aug 16, 2006 7:33:15 GMT -5
www.hostfile.org/psxfrontendv102.rar@gamesoul Master: I don't store default paths. pSX Frontend only uses the correct paths when you select a valid pSX executable, its assumption being that the same directory would contain a psx.ini. The reason I did it this way was that some people might use different versions of pSX in different directories. If a pSX executable is not selected, the file selectors will behave in the default way: start from whatever directory was last used. As for relative paths, I opted not to do it because of the possibility that people include spaces in their paths (maybe they moved their memcards directory to C:\Memory Cards for whatever reason). In that case, a long name path still couldn't be used until I converted it to short filenames again. About the fallback thing, I would've done that, but there are (probably) people like me who rename the executable to fit multiple versions of pSX into one folder, so it does no good to try to pick one out of all of them. Since the executable is the most integral part of this whole emulator, I'd find it odd that someone wouldn't pick the executable immediately anyway, so a fallback isn't really necessary, IMHO. Um, the code you gave me above I've no clue how I'd use it in my code, but I only said my BIOS code was "dangerous" because I didn't test it thoroughly, not that I actually thought it was I ditched the "Restore Last Session" option and made pSX Frontend load all the time like you said. I added the "Clear Settings" item to the File menu, as I didn't know where to put it as a button that wouldn't stick out like a sore thumb -- it doesn't fit anywhere in terms of context with the other widgets around it. Loading automatically all the time was something I was considering before I actually added the option to toggle that behavior, but at the time, I wasn't sure how I'd reset all the fields without having to do it manually, widget by widget. Then I realized that all I had to do was delete the "pSX Frontend Settings" section and reload it... Somehow, I have a feeling this isn't something I'm going to want to do in the future, if I ever add more settings unrelated to profiles (but for pSX Frontend itself), so I think I'm going to have to split the settings section off from the last session...
|
|
|
Post by patrickp on Aug 16, 2006 8:44:11 GMT -5
It's looking very complete now, Ultima but, inevitably - there's a few bugs! First and foremost, the long-awaited BIOS selection doesn't work: when I looked at it, it only allowed selection of scph1001.bin. Fine, I thought, that must be a default; I probably have to select the emu executable to set the relative path for the BIOS folder. So I did. Now it only allows selection of dtlh3000.bin - that's one I haven't even got! It doesn't even allow selection of scph1001.bin... just checked - yes, it's changed psx.ini to read dtlh3000.bin, too. It does write the relative path correctly, though: bios\dtlh3000.bin. The Disc selector only allows selection of an image, and not a CD drive now, as well. The shortcut creator works, but it might be a nice idea to be able to set where it will be created - ATM it just creates it in the pSX folder - or even a default to create it, say, on the desktop? As I mentioned before, how about including reading from shortcuts as well, so you can simply create a profile from an existing shortcut? Just add BIOS selection and voila! instant profile! I'm just off to modify the frontend .ini - see if that'll set the BIOS as wanted... Edit: looks like what's happening is that on first running the frontend, it shows scph1001.bin (US) as the selected BIOS and writes this to its .ini file: it writes to psx.ini as bios\scph1001.bin (US), but to its own .ini file just as scph1001.bin (US). It allows no change to this. As soon as you select psxfin.exe as the emulator file, it changes the selected BIOS to dtlh3000.bin (US), again allowing no change from this, and writes it to psx.ini as bios\dtlh3000.bin (US), and to its own .ini file as dtlh3000.bin (US). Manually modifying psxfrontend.ini to another BIOS doesn't help; it just changes it back to dtlh3000.bin (US) as soon as you run the frontend again.
|
|
|
Post by Ultima on Aug 16, 2006 10:53:22 GMT -5
I'm not sure about backwards compatibility, though I don't see why not, seeing as how I never changed the variable/key names. I *think* I fixed the BIOS selection -- lol I did say it was dangerous after all ;D Additionally, the BIOS selection thing now displays only what BIOS files exist in the directory specified by psx.ini (well, a directory isn't specified directly, but I extract it from the PS1 key in the [BIOS] section).
As for the Disc selector, what do you mean? When you select "Drive" and then "..." you can pick the drive letter, can't you?
I'll see about the shortcut importing, though it sounds like it could be a real pain to do, since I have to play guessing games with the commandline arguments.
|
|
|
Post by patrickp on Aug 16, 2006 11:33:24 GMT -5
I'm not sure about backwards compatibility, though I don't see why not, seeing as how I never changed the variable/key names. I *think* I fixed the BIOS selection -- lol I did say it was dangerous after all ;D Additionally, the BIOS selection thing now displays only what BIOS files exist in the directory specified by psx.ini (well, a directory isn't specified directly, but I extract it from the PS1 key in the [BIOS] section). No, it doesn't display what BIOS files I have in the bios folder; as I said, when I first run the frontend, before changing anything, it shows spch1001.bin (US), and nothing else; then once I've set the emulator executable (thus specifying the emulator folder, I presume?), it shows dtlh3000.bin (US) (which I don't even have - but is the first entry in GM's BIOS list) and nothing else is shown or can be selected. Something just occurred to me - both these BIOS names have (US) appended - possibly as part of the name? Is it actually looking for files with (US) etc appended to the filename? If so, no wonder it can't find any! ;-) Looking at the .inis it writes a correct filename (bios\dtlh3000.bin) to psx.ini, but dtlh3000.bin (US) (without the bios\ folder) to psxfrontend.ini. Maybe I'll try renaming some BIOS files and see if it picks them up... Edit: no, that isn't it... No, you can only select Image - there's no option to select Drive. There was in v1.01, although I didn't use it. Well, that's just a luxury - sort of an extra on the shortcut creating side.
|
|
|
Post by Ultima on Aug 16, 2006 12:04:22 GMT -5
lol, next time, when I say "now," it means "the version I have right now" xD I'm still confused about the drive thing... I see it perfectly well O.o
|
|
|
Post by patrickp on Aug 16, 2006 12:40:12 GMT -5
I'm still confused about the drive thing... I see it perfectly well O.o Like this: Image is the only entry on the list! Similarly: This is a BIOS I don't even have!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 16, 2006 14:17:55 GMT -5
Just a suggestion to the host thing. If you have a google account (gmail, google groups, anything) you can use googlepages to host plenty of files. If someone happens to need a gmail invitation btw, I have more than enough. But I suppose the hostfile.org place seems to work quite okay. I don't know if it has any kind of bw limits, but here's another link if you need one for now. bob.lintbox.net/files/pSX_Frontend_v1.02.rarEDIT: I don't see either of the issues patrickp is seeing in the 1.02. Works okay for me. Couple suggestions. As was mentioned, create the shortcuts to the desktop instead of the base folder. And in the profile tab, doubleclicking a profile name from the list should probably load the profile. Possibly run the profile even. If possible, user option to select the default action for that. EDIT2: It looks like the shortcut doesn't get created to base folder afterall, but the last used folder.
|
|
|
Post by Ultima on Aug 16, 2006 15:02:08 GMT -5
I can't read double-click actions with AutoIt. Otherwise, I would've done that already =T www.hostfile.org/psxfrontendv103.rarHistory ======= v1.03 (2006-08-16) + Ability to clear current settings + Ability to specify where you'd like to save shortcuts ~ Always remembers previous session ~ If BIOS directory found, only those that exist are listed in BIOS combobox ~ Fixed BIOS stuff (hopefully) ~ Split pSX Frontend settings off from previous session settings, so now there are 2 profile names that can't be used: "pSX Frontend Settings" and "Last Session" Still need to look at (no guarantees)... - Importing shortcut profiles - Relative paths So much stuff going on, remind me what I forgot and/or haven't done.
|
|