So this has long been a pet peeve of mine and I don't understand why
Microsoft and 3rd party ISVs can't get their you know what together and
resolve this issue once and for all.
Due to my advancing age, my eyesight isn't as good as it once was. As
such, I run all of my systems that support 1024x768 or above resolutions
using "Large Size (120 DPI)" in display settings.
Doing this and then trying to use the Crossword puzzle in the Experience
pack is, well, an Experience in frustration. The puzzles become
unplayable as there is no way to scroll in the window and you are unable
to see the entire puzzle.
Victoria, can you please take this feedback to not only the Experience
developers but to all developers at Microsoft. If you're going to offer
this option in the OS, then application developers need to take this
into account.
When using the large DPI settings, dialog boxes have text chopped off,
you can't always see or navigate to controls in windows, etc., etc.

--
Paul Adare
MVP - Windows - Virtual Machine
http://www.identit.ca/blogs/paul/
Scientists were excited this week at having isolated a brief sound which
occurred immediately before the Big Bang.
Apparently, the sound was, "uh oh".

Paul Adare wrote:
> So this has long been a pet peeve of mine and I don't understand why
> Microsoft and 3rd party ISVs can't get their you know what together and
> resolve this issue once and for all.
> Due to my advancing age, my eyesight isn't as good as it once was. As
> such, I run all of my systems that support 1024x768 or above resolutions
> using "Large Size (120 DPI)" in display settings.
> Doing this and then trying to use the Crossword puzzle in the Experience
> pack is, well, an Experience in frustration. The puzzles become
> unplayable as there is no way to scroll in the window and you are unable
> to see the entire puzzle.
> Victoria, can you please take this feedback to not only the Experience
> developers but to all developers at Microsoft. If you're going to offer
> this option in the OS, then application developers need to take this
> into account.
> When using the large DPI settings, dialog boxes have text chopped off,
> you can't always see or navigate to controls in windows, etc., etc.

The problem is well known, but not likely to be properly addressed until
Windows Longhorn. Nonehteless, it's being driven more by new high-res
displays than human visual impairment. Unfortunately while so many
designers and developers are young enough to have excellent vision, this
is still not rated highly enough.

In the meantime you might find some of the tips on
http://www.microsoft.com/enable/ helpful.

--------------------------------------
http://msmvps.com/thinice/

In article <42551A5A.2020807@Nospam.mvps.org>, in the
microsoft.public.windows.tabletpc news group, Mike Williams
<mikew@Nospam.mvps.org> says...

> The problem is well known, but not likely to be properly addressed until
> Windows Longhorn. Nonehteless, it's being driven more by new high-res
> displays than human visual impairment. Unfortunately while so many
> designers and developers are young enough to have excellent vision, this
> is still not rated highly enough.
>

Thanks Mike, I'm well aware of the problem and this is not a new problem
and really isn't being driven by new high-res displays. I've been using
the large DPI settings since Windows 95 and this has always been a
problem, though not a universal one. There are a few developers out
there that account for this when coding, and I know for a fact that
there are APIs that allow for this setting to be checked and have
applications adjust their behaviour accordingly. This is not something
that needs to wait for Longhorn to be fixed.

--
Paul Adare
MVP - Windows - Virtual Machine
http://www.identit.ca/blogs/paul/
Scientists were excited this week at having isolated a brief sound which
occurred immediately before the Big Bang.
Apparently, the sound was, "uh oh".

The problem occurs with many non-Tablet applications as well. In some
applications the characters run off the components and other applications
refuse to run at all with large fonts. Software writers should pay more
attention to these issues, but as Mike Williams points out this is more
likely to come about by giving the developers high-res monitors than it is
by getting them to spend time with their parents or grandparents.

"Mike Williams" <mikew@Nospam.mvps.org> wrote in message
news:42551A5A.2020807@Nospam.mvps.org...
> The problem is well known, but not likely to be properly addressed until
> Windows Longhorn. Nonehteless, it's being driven more by new high-res
> displays than human visual impairment. Unfortunately while so many
> designers and developers are young enough to have excellent vision, this
> is still not rated highly enough.

Paul Adare wrote:
> In article <42551A5A.2020807@Nospam.mvps.org>, in the
> microsoft.public.windows.tabletpc news group, Mike Williams
> <mikew@Nospam.mvps.org> says...
>
>
>>The problem is well known, but not likely to be properly addressed until
>>Windows Longhorn. Nonehteless, it's being driven more by new high-res
>>displays than human visual impairment. Unfortunately while so many
>>designers and developers are young enough to have excellent vision, this
>>is still not rated highly enough.
>>
>
> Thanks Mike, I'm well aware of the problem and this is not a new problem
> and really isn't being driven by new high-res displays. I've been using
> the large DPI settings since Windows 95 and this has always been a
> problem, though not a universal one. There are a few developers out
> there that account for this when coding, and I know for a fact that
> there are APIs that allow for this setting to be checked and have
> applications adjust their behaviour accordingly. This is not something
> that needs to wait for Longhorn to be fixed.

There certainly are APIs to do this, but my perspective (as a past
member of both Office and Windows teams) is that sufficient resources
are not going to be allocated to do anything major on this till
Longhorn. There's plenty of code that just isn't going to get touched
for now with the current distribution of display resolutions.

Some bad problems have been addressed with each release in recent years,
but new problems are introduced with new software all the time, so the
clean-up efforts are always running waaay behind.

In article <42551EBA.20004@Nospam.mvps.org>, in the
microsoft.public.windows.tabletpc news group, Mike Williams
<mikew@Nospam.mvps.org> says...

> There certainly are APIs to do this, but my perspective (as a past
> member of both Office and Windows teams) is that sufficient resources
> are not going to be allocated to do anything major on this till
> Longhorn. There's plenty of code that just isn't going to get touched
> for now with the current distribution of display resolutions.
>
> Some bad problems have been addressed with each release in recent years,
> but new problems are introduced with new software all the time, so the
> clean-up efforts are always running waaay behind.

Gotcha. I think I misunderstood what you were trying to say. I don't
really expect this to be backported to existing applications, however,
since this problem obviously does have a solution, I don't see the need
to wait for Longhorn to come out, and I really fail to see why Microsoft
(and ISVs) continue to release software that ignores this problem!

--
Paul Adare
MVP - Windows - Virtual Machine
http://www.identit.ca/blogs/paul/
Scientists were excited this week at having isolated a brief sound which
occurred immediately before the Big Bang.
Apparently, the sound was, "uh oh".

Paul Adare wrote:

> I don't see the need
> to wait for Longhorn to come out, and I really fail to see why Microsoft
> (and ISVs) continue to release software that ignores this problem!

It's actually a security measure, so that visually-impaired hackers are
deterred from exploiting those programs.

--------------------------------------
http://msmvps.com/thinice/

Hi Paul,

I agree my team could have done a better job of supporting various DPI
settings in the Experience Pack and for that I apologize. It is a little
ticky to get right because you can design something that works in 120 DPI,
but then breaks in 130 DPI since there is almost no limit to the screen size
/ resolution / DPI mixture that one can have on their computer. Rather than
resorting all the way back down to 96 DPI you may want to play around with
the Custom DPI setting in Display Properties and see if you can find a DPI
setting that is greater than 96 and less than 120 that works in Ink
Crossword and is still readable to you. I'm sorry I don't have a better
answer for you right now, but my team and I are commited to finding a way to
handle this better in the future.

Thanks,
Dustin


"Paul Adare" <padare@newsguy.com> wrote in message
news:MPG.1cbecd7a5ad7cc4a989cb8@msnews.microsoft.c om...
> So this has long been a pet peeve of mine and I don't understand why
> Microsoft and 3rd party ISVs can't get their you know what together and
> resolve this issue once and for all.
> Due to my advancing age, my eyesight isn't as good as it once was. As
> such, I run all of my systems that support 1024x768 or above resolutions
> using "Large Size (120 DPI)" in display settings.
> Doing this and then trying to use the Crossword puzzle in the Experience
> pack is, well, an Experience in frustration. The puzzles become
> unplayable as there is no way to scroll in the window and you are unable
> to see the entire puzzle.
> Victoria, can you please take this feedback to not only the Experience
> developers but to all developers at Microsoft. If you're going to offer
> this option in the OS, then application developers need to take this
> into account.
> When using the large DPI settings, dialog boxes have text chopped off,
> you can't always see or navigate to controls in windows, etc., etc.
>
> --
> Paul Adare
> MVP - Windows - Virtual Machine
> http://www.identit.ca/blogs/paul/
> Scientists were excited this week at having isolated a brief sound which
> occurred immediately before the Big Bang.
> Apparently, the sound was, "uh oh".

In article <425529A3.50104@Nospam.mvps.org>, in the microsoft.public.windows.tabletpc news
group, Mike Williams <mikew@Nospam.mvps.org> says...

> It's actually a security measure, so that visually-impaired hackers are
> deterred from exploiting those programs.
>

:-)

--
Paul Adare
MVP - Windows - Virtual Machine
http://www.identit.ca/blogs/paul/
Scientists were excited this week at
having isolated a brief sound which
occurred immediately before the Big Bang.
Apparently, the sound was, "uh oh".

In article <u2RTFa4OFHA.508@TK2MSFTNGP12.phx.gbl>, in the microsoft.public.windows.tabletpc
news group, Dustin Hubbard [MS] <dustinhu@online.microsoft.com> says...

> I'm sorry I don't have a better
> answer for you right now, but my team and I are commited to finding a way to
> handle this better in the future.
>
>
No worries Dustin, I really appreciate the personal response! Please pass on my thanks and
kudos to your team. Other than the display problem (which while is frustrating, is nothing
news <g>) everything else has been a great Experience for me!

--
Paul Adare
MVP - Windows - Virtual Machine
http://www.identit.ca/blogs/paul/
Scientists were excited this week at
having isolated a brief sound which
occurred immediately before the Big Bang.
Apparently, the sound was, "uh oh".