|
Post by Ultima on Sept 13, 2007 22:03:40 GMT -5
Is your copy of Vista a 64-bit edition? My guess is that the way I'm handling the returned value from user32.dll's MonitorFromPoint() function is probably invalid... I'm "converting" a hWnd pointer into an integer, which works fine under 32-bit systems, but under 64-bit, I *think* it behaves differently... Le sigh. Gotta figure this one out again :<
Edit: Hm, maybe I've already found a solution...
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 22:38:17 GMT -5
Incidentally of note, I run pSX Frontend v1.11 in Windows Vista Home Premium ( 32bit) using a GeForce 8800 GTX (162.22). Odd. I wonder why it doesn't function properly in my case. Perhaps pSX Frontend is indeed functioning properly and the problem is in regard to my own system.
|
|
|
Post by Ultima on Sept 13, 2007 22:43:22 GMT -5
Heh sorry about that; I tried looking over your old posts, but (somehow) managed to overlook that very post -.-
[SNIP] If you don't mind, can you test this executable?
Edit: As an aside, I think I've gotten the column show/hide system down... What a pain it was to fix one stupid typo... Ended up taking probably an hour or two staring at and messing with my code before realizing I was using one measly variable in the wrong place :<
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 22:48:03 GMT -5
I'm afraid I was able to reproduce the same problem and solution with the contents of testmonitor.rar.
|
|
|
Post by Ultima on Sept 13, 2007 23:00:18 GMT -5
[SNIP] Can you try this build and tell me what the outputs are for when pSX shows up properly, and when it fails? You can press Ctrl+C on the "Output" dialog to copy the text and paste it here.
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 23:00:29 GMT -5
SUCCESS 0x00010001 2 guiXpos=505 guiYpos=234
FAILURE 0x00010001 2 guiXpos=577 guiYpos=584
EDIT- I believe the above information may be flawed. The instructions of your post above were different when I first looked at them.
|
|
|
Post by Ultima on Sept 13, 2007 23:01:25 GMT -5
Eh what the...? What is your desktop resolution...? Edit: Yeah, I updated the post because I didn't expect you to have read the previous post (I deleted it pretty quickly). It's not much different, though; the (again) updated build only automates the process of getting guiXpos and guiYpos. Still, I guess it's worth a try. I can't make heads or tails out of these results
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 23:07:54 GMT -5
I run in two resolutions depending on what I am doing. 1360x768 and 1920x1200. I have reproduced the problem in both resolutions. Below are the results of the updated build. In particular, I did this in 1360x768.
VISIBLE --------------------------- Output --------------------------- guiXpos = 0 guiYpos = 0 MonitorFromPoint = 0x00010001 ValidateCoordinate = 2 --------------------------- OK ---------------------------
INVISIBLE --------------------------- Output --------------------------- guiXpos = 577 guiYpos = 595 MonitorFromPoint = 0x00010001 ValidateCoordinate = 2 --------------------------- OK ---------------------------
|
|
|
Post by Ultima on Sept 13, 2007 23:14:09 GMT -5
This is peculiar as peculiar gets. I'm really not seeing what's going on here...
guiMaximized guiWidth guiHeight
What are these INI keys set to when it works, and when it fails?
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 23:19:29 GMT -5
In 1360x768. Using the Minimize method to reproduce the problem.
VISIBLE guiMaximized=0 guiWidth=350 guiHeight=529
INVISIBLE guiMaximized=0 guiWidth=122 guiHeight=174
|
|
|
Post by Ultima on Sept 13, 2007 23:28:34 GMT -5
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 23:32:24 GMT -5
I am unable to reproduce the problem with that build. EDIT- I notice a difference in the programs behavior now. It seems to flash on the screen briefly in whatever state it was in before being closed after I close it.
|
|
|
Post by Ultima on Sept 13, 2007 23:35:34 GMT -5
FINALLY! 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. So you can't reproduce the problem with a maximize any more? And by the way, thanks a bunch for your quick and continuous cooperation If you weren't sticking around, it might've taken days to get it fixed xD Edit: Yeah, it flashes because I restore the window if it's maximized or minimized before I grab the window size, write it to the INI, and then fully exit the application. If I don't restore the window, the window size/position grabber returns nonsense numbers. It's not a very elegant solution, but there appears to be no other way for me to accurately record those numbers into the INI.
|
|
xaaz
New Member
Posts: 25
|
Post by xaaz on Sept 13, 2007 23:42:44 GMT -5
You are correct. I can't reproduce the problem in either the Minimize or Maximize fashion. I would even hazzard to say that it is no longer a problem.
|
|
|
Post by Ultima on Sept 13, 2007 23:48:20 GMT -5
*Phew* Now that that's over with, I can finally get back to completing the near-finished Detailed view Thanks again!
|
|