"Graham McKechnie" <gmknospam@bigpond.net.au> wrote in message
news:e98NR41AGHA.2644@TK2MSFTNGP09.phx.gbl...
> Simon,
>
> Thanks for your reply. You originally mentioned that VS2003 double buffers
> the screen - that was the bit I didn't understand. Could you expand on
> that?
>
> I didn't know that AutoScaleMode.None gave you the default VS2003
> behaviour. A bit late now as I'm nearly done converting this app, but I'll
> keep that in mind for some other apps that I want to convert that will
> never run on high resolution devices.
>
>> Supporting DPI awareness in your Controls: Why don't you just handle the
>> GDI drawing in the OnPaint event then change each hard coded coordinate
>> to something like:
>>
>> value * g.DpiY / 96.
>
> Well I do practically the same.
> SizeF scale = new SizeF(g.DpiX / DOTSPERINCH, g.DpiY / DOTSPERINCH);
>
> But I've also found using OnParentChanged very useful as well eg
> if (((Form)Parent).AutoScaleDimensions.Width == 192f)
> {
> this.ScaleControl(new SizeF(2f, 2f), BoundsSpecified.Height);
> this.shadowPen.Width = 2f;
> this.framePen.Width = 2f;
> }
>
> I've now got both devices sitting side by side and just swap them over and
> retest as I go. That's not too bad once you get used to it.When I got my
> 4700 I never thought I was going to use the 5450 again and thought I'd
> sell it, but I'm glad I kept it. Active sync does a pretty neat job of
> handling the swapping, plus my phone. Not so sure the older versions of AS
> would have handled all that swapping.
>
> I am already using Michelangelo. My real problem was that I had crappy
> icons in the first place. I'm going to get a professional icon maker to
> make me some new ones. My icon drawing efforts are like "don't give up
> your day job"
>
> Graham
>
>
> "Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
> news:umyqxMvAGHA.1028@TK2MSFTNGP11.phx.gbl...
>> Hi Graham,
>>
>> The 2003 solution was simple but under developed and didn't support hires
>> devices such as the iPAQ h4700 which is 640x480 dpi or the iMate JasJar
>> etc..There are still lots of new devices being manufactured that only
>> contain QVGA screens 240x320. So with VS2005 Microsoft has added support
>> for both types. This makes sense as you can take advantage of the nice
>> higher resolution making your icons, text etc look nice and crisp.
>>
>> If you want to go back to double buffering (as per VS2003) then you can
>> set the AutoScaleMode of class Form to None.
>>
>> There was also a nasty little bug in VS2003 re imagelists. It wouldn't
>> support transparent backgrounds when adding Icons via the designer. So
>> this had to be done via code. So it wasn't so much hardship for me to
>> support hires as all I had to do was add additional code to change the
>> size of the imagelist depending on the resolution, then create a bigger
>> icon from the exiting icon stream.
>>
>> Supporting DPI awareness in your Controls: Why don't you just handle the
>> GDI drawing in the OnPaint event then change each hard coded coordinate
>> to something like:
>>
>> value * g.DpiY / 96.
>>
>> I personally always use Icons and use the Michelangelo icon editor - do a
>> google I'm sure you'll find the site I can't remember it now.
>>
>> Cheers
>> Simon.
>>
>>
>> "Graham McKechnie" <gmknospam@bigpond.net.au> wrote in message
>> news:e5UDb%23oAGHA.204@TK2MSFTNGP15.phx.gbl...
>>> Hi Simon,
>>>
>>> Could you explain that further? The 2003 technique sounds like a simpler
>>> solution, so there must have been a good reason for going away from it
>>> in 2005. Is it quicker the new way?
>>>
>>> I keep revising the way I'm doing this and I keep finding new ways to do
>>> the same thing. But I would like to make it as efficient as possible.
>>>
>>> For my custom controls I'm swinging to handling the scaling with
>>> ScaleControl in OnParentChanged, but then you need to check who the
>>> Parent is. But that doesn't get around using g.DpiX and g.DpiY in
>>> OnPaint if you happen to adjust anything in there.
>>>
>>> Re ImageLists I now find that I need both 16x16 and 32x32. Is there a
>>> tool around that easily converts gif, icons, bmp etc. from one size to
>>> another. I've been redrawing them, which I'm not to flash at and it's
>>> taking for ever.
>>>
>>> Graham
>>>
>>>
>>> "Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
>>> news:%230fRuyoAGHA.3352@TK2MSFTNGP10.phx.gbl...
>>>> This is because 2003 double buffers the screen when deploying a non-dpi
>>>> aware app on a hires device.
>>>>
>>>> Cheers
>>>> Simon.
>>>>
>>>> "Graham McKechnie" <gmknospam@bigpond.net.au> wrote in message
>>>> news:uUvhK1mAGHA.1124@TK2MSFTNGP10.phx.gbl...
>>>>> Simon,
>>>>>
>>>>> I must have got away with something then in 2003. My icons look just
>>>>> right when I deploy the 2003 app to either device.
>>>>>
>>>>> Graham
>>>>>
>>>>>
>>>>> "Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
>>>>> news:uQcwXviAGHA.2912@tk2msftngp13.phx.gbl...
>>>>>> VS2003 didn't handle scaling icons. VS2005 works the same as VS2003.
>>>>>> You still have to specify the size of the imagelist in both 2003 and
>>>>>> 2005.
>>>>>>
>>>>>> It would have been nice for VS2005 to automatically change the size
>>>>>> of the toolbar imagelist as when running in hidpi you want to use
>>>>>> 32x32 not 16x16.
>>>>>>
>>>>>> Cheers
>>>>>> Simon.
>>>>>>
>>>>>> "Graham McKechnie" <gmknospam@bigpond.net.au> wrote in message
>>>>>> news:%236VeX5dAGHA.2536@TK2MSFTNGP09.phx.gbl...
>>>>>>> Simon,
>>>>>>>
>>>>>>> Reasonable - but still a bloody pain to have to do all this, when
>>>>>>> VS2003 handled it all automatically.
>>>>>>>
>>>>>>> Every dynamically added control requires scaling and then testing on
>>>>>>> both devices. That's a fair amount of testing, just to convert an
>>>>>>> app to VS2005 - eh?
>>>>>>>