Infinity-Profan

- Page 1 -

through Anpassung of Api 19 on 16 I had me display.fullscreen zerballert -
functions now but again Api 16 on all Systemen.

01/24/15 ▲

Konstanten added:

display.rotation //=1
display.fullscreen//=2
display.keepon //=3
display.rotation.left //=8
display.rotation.right //=0
display.rotation.top //=1
display.rotation.bottom //=9
display.rotation.sensor //=4

01/24/15 ▲

2 New Features:

display.width //=100
display.height //=101

gives each The physikalische Size or. Number of Pixel the Displays back, quasi %maxx and %maxy. but deference: wrong itself according to Rotation! deference: The Size the Mainwindow gui.hwnd can small his z.B. unless the Vollbildmodus active is!

01/24/15 ▲

2 New Features:

display.xdpi //=102
display.ydpi //=103

Liefer back, wieviele Pixel the display per Inch indicating.

05/07/15 ▲

iF (07.05.15)

2 New Features:

display.xdpi //=102
display.ydpi //=103

Liefer back, wieviele Pixel the display per Inch indicating.

but deference: there's evident no Possibility The utterly detailed
Size the Displays herauszurechnen - about The wide in cm o.ä.,
because the dpi-indicated not perfect very are. One unit with 7,5cm
breitem display yields to the bill only 6,5cm. the shining but
any APPs To concern or. complete Android, because alike which APP I
from the PlayStore teste, tappt im dunkeln calculate any so "un"genau. find I pity.
Perhaps. has Yes yet someone a idea, where The detailed Size standing. in the momentum
faith I nirgends.

05/07/15 ▲

HofK

have another little sought, but no exakte indicated found.
an understandable deutschsprachige statement to generellen Problematik under [...]

relating itself auf [...]

. below finds itself there:
"To create alternative bitmap drawables for different densities, you should follow the 3:4:6:8:12:16 scaling ratio between the six generalized densities. For example, if you have a bitmap drawable that's 48x48 pixels for medium-density screens, all the different sizes should be:

36x36 (0.75x) for low-density
48x48 (1.0x baseline) for medium-density
72x72 (1.5x) for high-density
96x96 (2.0x) for extra-high-density
180x180 (3.0x) for extra-extra-high-density
192x192 (4.0x) for extra-extra-extra-high-density (launcher icon only; sea note above)"

can I not any more simply double? How comes Date on the vorletzten worth?

Fazit: Android rechnet well always "ungefähr", means ~ moreover supra on the Page, but already antiquated:
"Note: Beginning with Android 3.2 (API level 13), these size groups are deprecated in favor of a new technique for managing screen sizes based on the available screen width.
dpi (low) ~120dpi
mdpi (medium) ~160dpi
hdpi (high) ~240dpi
xhdpi (extra-high) ~320dpi
xxhdpi (extra-extra-high) ~480dpi
xxxhdpi (extra-extra-extra-high) ~640dpi "

XProfan 11

on what i was hoping would one worth of Vendor - cache in ever of/ one
Info - where The Displaymaße in mm see or inch or so. Scheints but
net To give.

HofK

If it soon useful for each simply bestimmbar is, can we Yes a scheduler all available tools open. Then one see, whether The difference in anybody shape systematic or completely chaotic is.

Och Yes, jo!

- Page 2 -

The whole Konstanten as Getter are unnecessary, function must rewritten go so tappt im dunkeln (How others too) just one assoz. aray supply if no Param transfer watts.

11/07/15 ▲

yet differently: The individual Getter are thoroughly meaningfully, but the FN
without Params must too any Assoziationen supplying.

11/07/15 ▲

OK, ex 0.7.2 (next Version)

reicht one print display().fontsizes or display()["fontsizes"] for display(display.fontsizes) since the FN display without Params one assoz. aray supply.

11/07/15 ▲