Ux update:
- add_buttons.zip
- button_favorites.zip
- speedcam_mod.zip
Spoiler: ux update
Thanks to pongo.
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.
Last edited by Boki_Srb; 20th April 2019 at 10:07 AM.
Ux update:
- add_buttons.zip
- button_favorites.zip
- speedcam_mod.zip
Spoiler: ux update
Thanks to pongo.
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:
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 ....... 240At dpi = 270 is perfect for the Keyboard
At dpi = 290 is perfect for the app
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.
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)"
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.What happens when you set the parameters out of range?
In reality with "standard" resolutions the proportions are regular, these things happen with "anomalous" resolutions, in which all proportions are not maintained.It is very interesting then, instead of reducing the size of objects, NextGen it actually increases them. Why? I do not know.
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 .....
This has been asked before by others and me.
In android ver pal, pongo skin how can the map fonts be changed.?
At the moment by default there are 2 types. One is white with black shadow. This one is OK
The other is transparent with white border. The letters are very small and close together and whenever they display they are unreadable.
Sorry I dont have another picture at the moment
I know all about that matter.
All this parameters are in very close correlation.
A set of six generalized densities:
these are the standards for android, so no setting over these values do not make changes.Code:Please Login or Register to see the links
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?
Last edited by Boki_Srb; 21st April 2019 at 09:34 AM. Reason: typo - one letter correction :-)
Guys can you provide me with the location of TRAFFIC SIGNS icon and SPEEDCAM icon bmp...so I would like to replace it.
Here is PONGO
Spoiler: CLICK
and I would like to replace it with this one from PAL
Spoiler: CLICK
I tried with speedcam from PAL it does replace speedcams but some options from skin are missing i guess it has to remain with its own speedcam file. Does anybody knows where exactly inside SKIN.ZIP or DATA.ZIP PONGO keeps those two things?
Thank you.
NOTICE: By no means I advise installing illegal software nor I support such actions. This is just for EDUCATIONAL PURPOSES. Please use my post in order to understand or learn something new. I am a proud owner of LICENSED NAVIGATION but just to satisfy my curiosity I test, read and research. Sharing illegal material is against the law.
hi,
This files are in the " data ":
1) In folders "xxxhdpi, xxhdpi ............." under the name "traffic_light.bmp ".
2) In the " nodpi " folder, under the name " spr_traffic_light.svg " !
Bookmarks