xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 6, 2007 13:05:26 GMT -5
That's quite interesting, patrickp. I use the Windows version myself and I'm afraid I'm not familiar with Linux. I did however explore my Windows version of psxfrontend.ini via Notepad and discovered that you are absolutely correct in using Notepads Replace for the relevant Paths. It worked like a charm. That being said, I'm the lazy type, so I'm still in favor of pSX Frontend fixing the Paths on it's own. -Xaaz
|
|
|
Post by patrickp on Sept 6, 2007 13:16:20 GMT -5
Oh, we're all lazy, xaaz. it's just that Ultima's Linux version isn't as full featured as the Windows one, so we have to learn to do things on our own! ;D
|
|
|
Post by Ultima on Sept 6, 2007 19:24:12 GMT -5
I'm betting on the the path stuff just not happening. pSX Frontend handles multiple versions of pSX, each of which can be placed in multiple locations on disk. Just because the location for one of the versions is moved doesn't mean it's moved for every other version. Or am I missing something here?
As for the "global" switches... I believe patrickp has asked me for the ability to set defaults, which is an alternative that I would be more willing to implement than having a global setting (though I'm still on the fence about it too).
|
|
|
Post by Ultima on Sept 13, 2007 9:47:26 GMT -5
Question about VSync option implementation... Should I bother differentiating between fullscreen and windowed VSync, or should I make one option toggle both? I'm leaning toward the latter, as there doesn't seem to be much point (to me) in turning VSync on for one, but not on for the other Edit: I've implemented the real "List" view now, and renamed the old "List" view to "Detailed." Also added "Small Icon" view for completeness I guess. Edit: Should I... um... add columns for "Detailed" view? If so, what columns should I add? I've got some ideas, but want to see what other people think first.
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 13:08:08 GMT -5
For the "Detailed" view I would imagine the following would be interesting to have listed.
1.Switches Used 2.Version of pSX Used 3.Memory Cards Used (ie, which slot and card name) 4.BIOS Used
Basically listing all variables is how I personally envision a "Detailed" view.
-Xaaz
|
|
|
Post by Gamesoul Master on Sept 13, 2007 13:17:14 GMT -5
Is it not possible to create a customizable list of columns that show? Like Windows behaviour is basically what I'm referring to. As for that "Version of pSX Used"... wouldn't a variable for that have to be set first? The last time I used the frontend (a couple weeks ago), I recall nothing about telling it which version of pSX I'm using.
If it's not too much trouble, probably better to give two different options for windowed/fullscreen VSync. If it *would* be a bit of trouble to move things around for that, then don't worry about it, as I would assume that most people would have it on or off regardless of video setting. Though that isn't certain, as I could imagine people having it on during fullscreen and off during windowed, where speed is a slightly higher problem of maintaining.
|
|
|
Post by Ultima on Sept 13, 2007 14:13:02 GMT -5
Indeed, a pSX Version column won't happen because I've no way to figure it out, and it makes little sense (to me) to have the user specify a version for each profile. I was planning on making the columns customizable, but there isn't any easy way to do so in a clean manner in AutoIt (yes, there we go again with the AutoIt limitations :-\). I mean, I can easily make columns "hidden" by setting their widths to 0, but they won't really be hidden, as the user can just make the "hidden" column wider, and it would no longer be hidden. That's why I asked in the first place (otherwise, I would've just added everything). Meh, I'll see...
Moving stuff around isn't a big problem, so I guess I'll just go ahead and add the extra VSync option...
|
|
|
Post by patrickp on Sept 13, 2007 15:02:51 GMT -5
Besides, if people want to know the version number a particular profile is booting (i.e. if it's significant), they can include it in the profile name.
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 16:18:44 GMT -5
I don't particularly see the problem in determining which version of pSX the user is running. As I understand it, for all Windows releases (barring 1.8 and 1.9) the executable is of a different size. Granted, I'm not a professional programmer and I have no idea how pSX Frontend's code is set up, but couldn't a small function be written that queries the filesize of the "psxfin.exe" executable? A quick glance at my own directory of pSX Author's releases shows the following.
1.0=psxfin.exe 988KB 1.1=psxfin.exe 992KB 1.2=psxfin.exe 996KB 1.3=psxfin.exe 1,012KB 1.4=psxfin.exe 1,128KB 1.5=psxfin.exe 1,136KB 1.6=psxfin.exe 1,144KB 1.7=psxfin.exe 1,148KB 1.8=psxfin.exe 1,160KB / readme.txt 13KB 1.9=psxfin.exe 1,160KB / readme.txt 14KB 1.10=psxfin.exe 1,332KB 1.11=psxfin.exe 1,404KB 1.12=psxfin.exe 1,828KB 1.13=psxfin.exe 1,868KB
Querying the filesize of the executable (and in two cases, the readme file as an example) would remove the need for the user to specify which version they are using as well.
I'm not sure if the same concept would apply in Linux though, seeing as how I'm more or less ignorant in that department.
-Xaaz
PS - Hurray for two Vsync options!
|
|
|
Post by Ultima on Sept 13, 2007 17:03:16 GMT -5
psxemulator.proboards54.com/index.cgi?board=support&action=display&thread=1155421460&page=17#1157641724I'm already aware of that method of guessing the version (it's different from detecting the version). I'm not particularly interested in hardcoding the file size values for each and every release of pSX for something that's not guaranteed. It would also put my releases of the frontend in lockstep with pSX's -- not something I want to be forced into, which is one of the reasons I added the "Extra Switches" field in the first place in pSX Frontend v1.11. There are several assumptions you're making with your suggestion that I just can't make: 1) that the user actually keeps the different versions in separate directories (I know I don't), and that the user doesn't rename the readme (they might want to keep every readme from version to version in the same directory with the executables in the same directory) 2) that the user doesn't modify the executable in any way (example: UPX packing, or ResHacking, which I've done before) 3) that pSX Author will never ever release another version with the same executable and readme size (it can happen) There are probably others, but the point is that hardcoding the hashes and/or the file sizes of various files is not a scalable solution, and isn't guaranteed to work all the time. I'm not a fan of half-assed features (excuse the language) xD Gamesoul Master will probably recall how I was making a ruckus over multi-monitor detection not working correctly, and after much fussing, I got it working satisfactorily (and not in a half-baked manner either ). Thanks for your continued feedback and suggestions though! Much appreciated
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 13, 2007 17:03:41 GMT -5
I personally wouldn't need that. Infact, only really useful information I can think of is if you would add a flag in the profiles to mark whether the game works or not. With big lists it would be easier to check what to test each time a new version comes out. Makes sense?
Other than that, I'm not all that interested in detailed views.
edit: I also keep all my pSX exes in a same folder, and only keep the latest readme. The newest exe is always psxfin, and I rename the older stuff according to their numbers.
|
|
|
Post by Ultima on Sept 13, 2007 17:11:21 GMT -5
Regarding the detailed view, I *think* I've thought of (half thought-up, half found-in-documentation) a way to hide unwanted columns somewhat cleanly in AutoIt (no guarantees at this point), but you will still be able to inadvertently unhide columns as I've explained was possible before. Maybe I should also add an option to hide the column headers too so that that doesn't happen ( or at least lock the column headers -- or both; it seems I can't lock column widths). In that way, you'll be able to change the "Detailed" view back into the current "List" view, and all will be back to Business As Usual™ @ patrickp: Unfortunately, I don't have a copy of Linux installed (lol, yes, again). To add to that, I'm not sure any of the changes I'm making right now are relevant in Linux either (VSync doesn't work in Linux right?). Listviews might be possible, but I'm already having one hell of a time messing with it on Windows So yeah, I'm not sure when I'm going to be messing with the Linux version :< Just a non-progress update on that build, I guess
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 18:19:14 GMT -5
I believe I have found what seems to be a bug of some sort. Whether or not it is a bug in pSX Frontend or in something else I am uncertain of.
Incidentally of note, I run pSX Frontend v1.11 in Windows Vista Home Premium (32bit) using a GeForce 8800 GTX (162.22).
Occassionally when I close pSX Frontend and then go to use it again it will not appear on my desktop. During these instances it does however appear in the taskbar as well as in Task Manager, but when clicking on it in the taskbar nothing happens and it remains "invisible."
At first I thought it was just Windows Aero acting up so I attempted to refresh my desktop with no success. I then explored the Frontends taskbar right-click menu (restore, move, size, minimize, etc) and the only option or combination of options that made the program visible was Maximize. From it's maximized state I could only either close the Frontend or minimize it. Attempting to restore it to a windowed state did not function. I then disabled Windows Aero but the problem persisted. Using Alt-Tab and WindowsKey-Tab also did not work. The only solution I could find was to restart my computer, after which the Frontend would appear and function as normal.
I then experimented and found I was able to reproduce the problem. The Frontend only experienced the above if during it's previous session I closed it via the taskbar right-click menu while it was either maximized or minimized.
I am at something of a loss as to why this happens. I also do not recall this ever happening with any of my other applications.
|
|
|
Post by Ultima on Sept 13, 2007 19:29:34 GMT -5
Check psxfrontend.ini, and look at guiXpos and guiYpos... I'm guessing it's some odd, off-screen numbers, right? If so, then my off-screen-detection function is no longer working under Vista. Ugh... It's hard for me to fix without a copy of Vista installed... Try setting both of those INI keys to 0 and see if the problem persists.
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 19:59:27 GMT -5
It seems you are absolutely correct, Ultima. Entering 0,0 fixed the problem after it occurred. I then reproduced the problem and fixed it with 0,0 again to confirm it.
|
|