On a “Personalize Desktop” a user may set the text size to 125%, 150%, or 
even larger, which makes the menu and forms ugly.  Is it possible to exclude 
the xBase application from this setting so it runs with normal text size of 
100% (default)?
Many thanks,
-Itai

On 11/15/2013 4:40 PM, Itai Ben-Artzi wrote:
> On a “Personalize Desktop” a user may set the text size to 125%, 150%,
> or even larger, which makes the menu and forms ugly.  Is it possible to
> exclude the xBase application from this setting so it runs with normal
> text size of 100% (default)?
> Many thanks,
> -Itai

I've seen this very commonly with newer computers, with win 7 and higher 
it is much easier for the user to change the font scaling.

when the user changes the font scaling/dpi from the normal 96dpi 100%, 
to something larger such as "Larger fonts 125%" (120dpi), then the text 
is larger but the getboxes and other controls to not resize larger.

I've used a function to get the screen dpi, and use the COLPIXELS with a 
normal number when creating dialogs. normal uses 7 pixels per char, 
larger font scaling such as 120 dpi looks best with COLPIXELS set to 8 
pixels per char.

there is also a way to auto resize controls when the dlg is resized 
which is great also.

These are settings with eXpress, there may be something similar for the 
gui that you are using.

Hope that helps,

Shaun

Shaum,
What is COLPIXELS?

On 12/18/2013 4:46 AM, Itai Ben-Artzi wrote:
> Shaum,
> What is COLPIXELS?
>
>
It's part of DCRead GUI command in the XBase++ addon eXPress++ from 
http://www.donnay-software.com/

On Fri, 15 Nov 2013 13:40:33 -0800, Itai Ben-Artzi wrote:

>On a “Personalize Desktop” a user may set the text size to 125%, 150%, or 
>even larger, which makes the menu and forms ugly.  Is it possible to exclude 
>the xBase application from this setting so it runs with normal text size of 
>100% (default)?
>Many thanks,

I don't think it's possible to exclude an app from this because the
change is made on a system level.  As shaun said, it's getting more
common for users to do this, especially as monitors get bigger (as
resolution increases the actual pixel size often gets smaller and
since object dimensions are based on pixel counts, everything gets
smaller and harder to read, so users raise the DPI setting in an
attempt to compensate).  Unfortunately this causes havoc in apps that
aren't designed to handle it.  So in our apps we need to test the DPI
setting at startup and adjust things accordingly.

Top-Down Library has an Application Scaling feature that allows us to
easily make our apps DPI-Aware.  This can be seen in action in the TD
demo app.


Regards,
Clayton

Clayton Jones   www.cjcom.net 
 Top-Down Library for Xbase++
 X-DBU Database Utility   
 X-MEMO Memo Field Replacement
 Spell-X  Spell Checking for Xbase++

Thank you, Clayton.
When compensating for enlarged DPI, do you change the font size or object 
size?
Can xBase use fraction point (eg 8.6) or only natural number (eg 7 or 8) in 
setFontCompoundName()?
Many thanks,
-Itai

Itai,

Sorry for my late reply, I've been real busy and away for awhile.

>When compensating for enlarged DPI, do you change the font size or object 
>size?

Both.  The TD app scaling feature treats object size and font size
independantly.  With normal scaling (when DPI is 96) they are in
synch.  But with increased DPI they operate independently.  Since the
font size is already increased by the DPI, the object size is
increased to match.  In addition, as the DPI increases the font may be
reduced a small amount in order to bring the two parts into harmony.
The challenge in designing the system was to find numbers that kept
everything looking pretty much the same.  If you try it with the TD
demo app you'll see what I mean.  There are slight differences at the
various DPI settings, but no show-stoppers.

Because of the way this approach works, it is unnecessary to "declare"
to the OS that the app is DPI aware (typically done with a special
section added to the manifest).  This usually is done in order to
prevent the OS from applying DPI virtualization (in Vista and later),
which provides some level of automatic scaling support to applications
that are not DPI-aware.  

I have tried it with and without the declaration and have seen no
difference.   


>Can xBase use fraction point (eg 8.6) or only natural number (eg 7 or 8) in 
>setFontCompoundName()?

I tried that once and it didn't work.  



Regards,
Clayton

Clayton Jones   www.cjcom.net 
 Top-Down Library for Xbase++
 X-DBU Database Utility   
 X-MEMO Memo Field Replacement
 Spell-X  Spell Checking for Xbase++

Many thanks, Clayton.
I'll try the TD as suggested.
-Itai