DonationCoder.com Software > T-Clock
T-Clock 2010 (download)
sagji:
@kronckew - Build # added to about screen.
Okay, as luck would have it, my brother who just moved down here and is staying with us for a while has a 42" TV with a PC input. This gave me a much better test platform for the High DPI bugg. So...
Monitor: 42" Toshiba 1080p HD TV
OS: Windows 7 Professional
Resolution: 1920x1080
DPI: 150
Dialog Position: Where it Belongs... (Finally!)
In case anyone is wondering, the origional code was actually correct, I just needed to add the DPI aware option to the manifest file - which required VS2010. *Sigh* ...I really liked VS2005 better.
Only (other) down side at this point is I'm not sure if/how well it will run on Windows 2000 after being compiled with MSVS2010.
On a brighter note, I can finally get on with some of the other ideas/suggestions that have been mentioned/discussed/requested above.
-Stoic Joker (July 16, 2010, 10:26 PM)
--- End quote ---
Murphy was so impressed by your fix he slipped a x86 version into the x64 folders so it doesn't work on my system.
Stoic Joker:
Murphy was so impressed by your fix he slipped a x86 version into the x64 folders so it doesn't work on my system.-sagji (July 19, 2010, 01:27 PM)
--- End quote ---
:wallbash: 40 downloads in 24 hours and its just got to be the one release I package wrong.
[Expletive Replete] Murphy. :D
sagji:
Well this one runs.
But it isn't any different - except there is extra text on the about page - but it wraps after the second - and 3/4 of the second line gets clipped off.
It is still appearing off screen, and still shows scaled coordinates to window spy. If I move it so the right edge is adjacent to the taskbar then with the mouse at the right edge of T-Clock's window the x screen position is about 1400 but when i move it right is suddenly jumps to over 2000.
Stoic Joker:
Well this one runs.
But it isn't any different - except there is extra text on the about page - but it wraps after the second - and 3/4 of the second line gets clipped off.-sagji (July 20, 2010, 04:41 PM)
--- End quote ---
Yeah, oops ... The test machine (looked fine, but) was at some weird res/DPI setting so I gotta redo that part - It was a bit of an (after thought) rush job.
It is still appearing off screen, and still shows scaled coordinates to window spy. If I move it so the right edge is adjacent to the taskbar then with the mouse at the right edge of T-Clock's window the x screen position is about 1400 but when i move it right is suddenly jumps to over 2000.
--- End quote ---
Man, I've tried everything I can think of trying to duplicate this to aviod picking on your hardware. But, I think we may need to explore that possibility. I had hoped that someone else with that type of setup would chime in to confirm or disprove the behavior ... but it seems it just the two of us stuck head-2-head. I'm debating on adding a (work arround) option to save last dialog position as a last resort.
Everything I try makes it worse, and the more I research this everything points at the origional code as being correct.
*Shrug* I'm stumped... :(
sagji:
It is still appearing off screen, and still shows scaled coordinates to window spy. If I move it so the right edge is adjacent to the taskbar then with the mouse at the right edge of T-Clock's window the x screen position is about 1400 but when i move it right is suddenly jumps to over 2000.
--- End quote ---
Man, I've tried everything I can think of trying to duplicate this to aviod picking on your hardware. But, I think we may need to explore that possibility. I had hoped that someone else with that type of setup would chime in to confirm or disprove the behavior ... but it seems it just the two of us stuck head-2-head. I'm debating on adding a (work arround) option to save last dialog position as a last resort.
Everything I try makes it worse, and the more I research this everything points at the origional code as being correct.
*Shrug* I'm stumped... :(
-Stoic Joker (July 22, 2010, 06:50 AM)
--- End quote ---
I think I have found what's wrong with the x64 version.
The two versions (x64, and x86) have different manifests. The x86 has both the sections that are in the x64 clock.exe but in the opposite order, and also has a third section that includes the dpiAwareness setting. So it looks like the x64 version isn't set as DPI aware.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version