Messages - sagji [ switch to compact view ]

Pages: [1] 2 3 4 5next
1
Developer's Corner / Re: Diff before commit
« on: November 08, 2010, 10:20 AM »
For me the diff before commit is the final approval step.
It is were I make sure of code quality - conformance to coding style and naming convention.
Make sure that any test code is removed.
Make sure I have tested all code paths.
Make sure that all changes correspond to something in the change description - even if it is just "review changes"
Make sure that all required changes have been done.

The only time I don't do the diff is if there is no decision in the change - such as adding in an update from an external source (e.g. updating to a later version of a 3rd party library.)

2
T-Clock / Re: T-Clock 2010 (beta - download)
« on: July 25, 2010, 05:30 PM »
As an experiment I added the DPI aware to the x64 version's manifest.
It now appears in the right place <added> and the calender appears on screen </added>.
But it isn't scaling correctly internally.

I have attached before and after images for the about, mouse, and quicky tabs - the others appear normal.
In the mouse tab the list of actions starts too soon so overlaps the controls for setting the actions.
In the quicky tab the list doesn't fill the remainder of the page.
The font in the tabs is smaller - so more fit on one line.
The label with the build information fits better but still wraps onto a second line and gets clipped.

3
T-Clock / Re: T-Clock 2010 (beta - download)
« on: July 25, 2010, 04:26 PM »
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.

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... :(
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.

4
T-Clock / Re: T-Clock 2010 (beta - download)
« on: July 20, 2010, 04:41 PM »
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.

5
T-Clock / Re: T-Clock 2010 (beta - download)
« on: July 19, 2010, 01:27 PM »
@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.

Murphy was so impressed by your fix he slipped a x86 version into the x64 folders so it doesn't work on my system.

Pages: [1] 2 3 4 5next
Go to full version