I think I have earnt it

[Guest]

I wouldn't mind a reply form some-one getting paid, concerning the issue in
regards to Windows' Accesibilty, font increases and overflowed dialog boxes.

Anything would help, and I have helped a multitude of people over the last
two days.

 

[Dave B.]

Are you implying that you want to get paid for posting in a Microsoft
newsgroup?
Good luck with that, I hope either I misunderstood or your kidding.

 

[Gene K]

Frankly, I do not understand. Please state your specific problems in an
understandable manner.
Gene K

 

[Guest]

READ previous posting:

'http://www.microsoft.com/wn3/aspx/n...y&mid=e04429a2-6877-4022-82c5-e233953f6749');

 

[Jupiter Jones [MVP]]

If you want support from a paid person, you will most likely have to pay for
that luxury.
These peer to peer newsgroups are monitored by people volunteering their own
time.
Occasionally Microsoft employees do post here, but they do so on their own
time.

 

[Guest]

-Idont' really care if your paid or not - I just want a Professional answer.
Not just a coloquial runabout solution from a Linux style forum post.

It's a pretty simple question - with I presume a fairly complicated answer.

How is it that if you change your system font or increase the DPI level of
your fonts that a very specific dialog instance (it's only one - every other
dialog is fine/customisable via resource hack) doesn't resize to fit it's
contents, is the code still from win3.0? , at the very least I wouldn't mind
finding out which library #32770 dialog is located - maybe the dialog is
actually there and I could make it WS_max by default, at least Grandma Will
be able to read the overflowed contents. (No-one likes to squint)

Actually here's another one - why not make the start menu Places pane
autosize (or atleast run code on OS startup that resizes it to accomodate
overflowed text) instead of grabbing it from msstyles/styles.dll?

What surprises me the most is that something so obvious was missed over and
over again with every release of Windows - will Vista fix this?

 

[Sharon F]

What surprises me the most is that something so obvious was missed over and
over again with every release of Windows - will Vista fix this?

Finally, Vista addresses some of this. It's not perfect but it's much
better than it has been in previous versions of Windows.

General: The operating system cannot address all issues since it's possible
for an individual app to dictate the maximum size of message windows and
other interface elements (text size, text type) spawned by that app. Vista
has made message boxes scalable for apps that make generic use of the
common dialog controls (and some other shared code). However, some
programmers get "creative" in this area or fail to consider all scenarios.
The results - you are already familiar with them - can be less than what is
needed by the end user.

Nowadays with larger monitors, it is not only visually challenged users
that need "elasticity" in this area. Even folks with good eyesight get
tired of squinting. Here's hoping that all programmers - for Windows and
for applications - strive to be more aware of these issues,

 

[Guest]

Yes - programmers can now use the great .net form classes which are much more
appropriate/more webstyle sizable. -but of course we all get lazy and just
look at who it works on our computer and never get it right for everyone -
even webpage programers lock users into a fixed size font expecting all of us
to be runing 1024x768.

what is bemusing though is...
Msoft standard programs (the ones that come with the OPsystem) don't
specify any dialog proerties when they are started (I presume this is to save
on speed), instead MSoft decided to set the proerties of the Standard
Container Dialog, and other containers like the TabPane to a specific size
with other specific properties aswell eg. nonsizable. These sizes/properties
therfore don't get sent to the instanciatied object like they would normally
by a programmer, Msoft programs assume that thier default properties are just
fine for all the Control Panel dialogs and yes - the Print dialog, again I
assume this is done to save on speed and memory (Probably 100 lines of code
to save on for each instance -but of course ram is cheep now so a couple of
extra B's ain't going to affect performance is it?)

I reccomend that for Vista Msoft make sure that all container dialogs are
set to resize_on_overflow (which is now possible with the new dialogs), I
just hope they remember to do this for all of the previous Forms that have
been around since I presume win95. So I think they would need to go back and
fix the dialog libraries for the old software not just the new.

So again I ask, if any one has any idea - where is #32770 located? I want it
to be WS_MAX=True so that I can get around this problem without having to
wait for vista (or need new fandangled hardware for granny to run Vista)

PS - would this be illegal - fixing Msoft?

 

[Sharon F]

So again I ask, if any one has any idea - where is #32770 located? I want it
to be WS_MAX=True so that I can get around this problem without having to
wait for vista (or need new fandangled hardware for granny to run Vista)

I have no idea. I use Windows, I don't write it.

PS - would this be illegal - fixing Msoft?

Illegal? Doubt it. However, "reverse engineering" is mentioned specifically
within the EULA as something to avoid. On the other hand, I've seen/used a
third party solution designed for use with XP: Enhanced Dialogs from
Stardock.