Thread: Skin iGO nextgen by pongo (DISCUSSION)

Originally Posted by Blackttulip

I know that's not the best resolution for my tablet,but,is there a way to change it?

You are confusing the method Phildu has indicated to you, and that of changing the dpi in the sys. With the Phildu method you can change the size of the keyboard only, while varying the dpi values in the sys you get the variations of the whole screen.
The result you got was by chance, and now I'll explain why.

With a setting: dpi ="auto", the dpi value of your device adapts to the nearest "standard" dpi value.

Your tablet has 170 as a PPI value and has adapted to the standard value of 240, (+70), instead of 160, (-110).
When you set 270, (+30), it actually remained at 240, when instead you set 290, (+50), it adapted to the value 320, (-30), but closer.

I'll show you the proof I made for another user in another forum.
I have a Huawei P20 Lite with 432 as PPI value, (PPI and dpi actually represent different things but for practical purposes we can say that they match), so in my case the phone adapts to the standard value of 480 dpi, (+48).

Spoiler: image

[Only registered and activated users can see links. ]

As you can see I also set the dpi = 560, (+80 from the value 480 and -80 from the value 640), but it has adjusted to the value closest to the real one.
Then I set dpi = 640 and the screen is enlarged, then I set the dpi = 600, (-40 from the standard 640 but +120 from the standard 480), and the screen remained the same. I have also tried to set dpi = 800, but it does not work, beyond dpi = 640 results are not obtained.

From this test we can also see that small variations in the dpi value do not result in small screen variations.

I have not tried with base_dpi = ....... but I believe that it does not work ...... or as Arimi writes in his sys; base_dpi = ??? ; maybe needed only for iGO Avicsync.

Birbante, I did not set those values accidentally
My friend have in car 1024x600 7". After some experimenting, we stays at values I give in #1526.
Now, look better in his pics, and tell me what is wrong with them. And with yours, also.

Ux update:

• add_buttons.zip
• button_favorites.zip
• speedcam_mod.zip

Spoiler: ux update

This post requires you to click the "LIKE this post" button and hit F5 to read this content.

Thanks to pongo.

Originally Posted by Boki_Srb

Now, look better in his pics, and tell me what is wrong with them. And with yours, also.

My dear Boki you misunderstood me, there is nothing wrong with your values, I just explained how the dpi variations in the sys work.

When I said that the result was a case I was not referring to you but to what Blackttulip wrote:

At dpi = 270 is perfect for the Keyboard

At dpi = 290 is perfect for the app

if he tried as values dpi= 250 dpi and dpi=270, would not change anything, both values would have been adapted to the nearest default value ....... 240

The functioning of the dpi can be summarized as follows:

Small variations in dpi values do not match relative small screen variations,

the dpi values that are used by the program are only these: 120, 160, 240, 320, 480, 640,

every other intermediate value that is set is adapted by the program to the nearest default value, or lower or higher.

If anyone intends to do further tests even using the base_dpi =, he is welcome.

If Blackttulip wants to vary the size of the keyboard only, he must follow the advice of Phildu.

You did not understand the point

Your screen has a certain resolution (in your case 2280x1080 but it does not matter at all).
Is it even possible to display a higher resolution than its physical possibilities? Absolutely not. What happens when you set the parameters out of range?
Well, this creates an interesting situation. and depends only on software. It is very interesting then, instead of reducing the size of objects, NextGen it actually increases them. Why? I do not know.
This is what is wrong in the view.

Therefore, if you can not hit the correct values, the size of keyboard is not good.

Originally Posted by Boki_Srb

Is it even possible to display a higher resolution than its physical possibilities? Absolutely not.

True, but I never talked about "resolution", (if you look closely I have never used this term), but of "density". The unit of measure would be the PPI, (Pixel Per Inch), and not DPI, (Dot Per Inch), but I wrote what usually happens that they are confused;

"(PPI and dpi actually represent different things but for practical purposes we can say that they match)"

What happens when you set the parameters out of range?

The maximum value is used, ie 640, I wrote that I tried to set 800 but the screen remained the one of the value 640.

It is very interesting then, instead of reducing the size of objects, NextGen it actually increases them. Why? I do not know.

In reality with "standard" resolutions the proportions are regular, these things happen with "anomalous" resolutions, in which all proportions are not maintained.

By changing the dpi we can get small "adjustments", we cannot think of solving everything with the variation of dpi, also because variations of the whole screen are obtained, or larger, (closer), or small, (more distant).

To get variations of particular things like buttons, windows, etc., we need to work on the Skin where the dimensions are set, but we need to know what we're doing, otherwise we have to settle for .....

Originally Posted by BIRBANTE

True, but I never talked about "resolution", (if you look closely I have never used this term), but of "density". The unit of measure would be the PPI, (Pixel Per Inch), and not DPI, (Dot Per Inch), but I wrote what usually happens that they are confused;
... etc

I know all about that matter.
All this parameters are in very close correlation.

A set of six generalized densities:

Code:

Please Login or Register to see the links

these are the standards for android, so no setting over these values do not make changes.

Every screen is set for certain density and resolution. Softer is responsible to create a view, the driver is for display it. And all under the control of the operating system.
Again (to simplify) - what's wrong, when you define a larger dpi value, and the picture becomes bigger instead of smaller?