Starting with the next build server update (Friday) the following
windows-specific display properties will be accessible:

// Excerpt from test.. you may want to just add them to some labels to see
the values in your UI... or use Log.sendLog()
// to send these results to you.
Display d = Display.getInstance();
        Log.p("Logical DPI: "+
d.getProperty("windows.DisplayInformation.LogicalDpi", "Unknown"));
        Log.p("Diagonal Size in Inches: "+
d.getProperty("windows.DisplayInformation.DiagonalSizeInInches",
"Unknown"));
        Log.p("Logical Raw DPI X: "+
d.getProperty("windows.DisplayInformation.RawDpiX", "Unknown"));
        Log.p("Logical Raw DPI Y: "+
d.getProperty("windows.DisplayInformation.RawDpiY", "Unknown"));
        Log.p("Logical Raw Pixels Per View Pixel: "+
d.getProperty("windows.DisplayInformation.RawPixelsPerViewPixel",
"Unknown"));
        Log.p("Logical Resolution Scale: "+
d.getProperty("windows.DisplayInformation.ResolutionScale", "Unknown"));



These values may help us determine why your fonts appear small.

Steve

On Mon, Sep 19, 2016 at 3:04 PM, Steve Hannah <[email protected]>
wrote:

> Had to Google to see what the compute stick was.  Looks very cool!
>
> I have been digging into the UWP mmToPixel conversion today and everything
> looks like it's in order.   If anything, it might actually be the most
> accurate of any of the platforms for the conversion - and this could be the
> issue.  If this is on a television, then a millimetre sizing may actually
> produce text that is too small.  E.g. 2.5mm on a monitor is fine.  On a
> television, you wouldn't be able to see it at all because you'd typically
> be sitting back too far.
>
> I'll add some display properties that you can read to get the display
> information at runtime.  That might help you to track down the issue - or,
> might help me to improve things if you can provide this information to me.
>
> Best regards
>
> Steve
>
> On Mon, Sep 19, 2016 at 2:56 PM, Bryan Buchanan <[email protected]>
> wrote:
>
>>
>> 1360x768, DPI set to 100% (default).
>>
>> It's an Intel Compute Stick plugged in to the HDMI port of an LG TV.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "CodenameOne Discussions" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> Visit this group at https://groups.google.com/grou
>> p/codenameone-discussions.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/codenameone-discussions/65c16cda-1597-4ba4-b3be-a15fce4b
>> 0e02%40googlegroups.com
>> <https://groups.google.com/d/msgid/codenameone-discussions/65c16cda-1597-4ba4-b3be-a15fce4b0e02%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Steve Hannah
> Software Developer
> Codename One
> http://www.codenameone.com
>



-- 
Steve Hannah
Software Developer
Codename One
http://www.codenameone.com

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/CAGOYrKX%2BoB1XCJo-PDyszDZE96Kfz0O3ZTuY_Ecx4yHn70AXtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to