When turn by turn is active. There is a adjustment for km. Which effect does it have?
5 km is the default setting I testet it but figured it not out.
When turn by turn is active. There is a adjustment for km. Which effect does it have?
5 km is the default setting I testet it but figured it not out.
Set it to 500 m and do a simulation , you will see the Result
HI.I have a question about the pongo,i've increase the skin to dpi=280 its the best one for my tablet but the keyboard on the adress display is to big is there a way to reduce only the keyboard
Thanks
you can try to modify those 2 lines into "the_skin_by_pongo.zip"
1) - the_skin_by_pongo\ui_nextgen\common\ui\the_skin_by_pongo_params_landscape.css
keyboard_h:410; (replace 410 by 260)
then
keyboard_h:260; =ok
------------------------------------------------------------
2) - the_skin_by_pongo\ui_nextgen\common\ui\the_skin_by_pongo_params_portrait.css
keyboard_h:410; 324 (replace 410 by 324)
then
keyboard_h:324; = ok
before modification
Spoiler: pic1
after modification
Spoiler: pic2
Last edited by Boki; 18th April 2019 at 06:20 PM.
And resolution of your tablet is... screen size is...?
As your keyboard is not good on mentioned dpi, so that is not good resolution for it.
Hello, i am trying to replace traffic light icon within skin with a simpler version, have used Dview to create icon required and have replaced all traffic_light.bmp files in data\ui_nextgen\res\common and all dif res folders, also in the data\gfx folder but old icon is still display, at a loss to find and other locations to replace, help much appreciated thanks
The traffic light icons you see on the map belong to 95% to the speedcam.zip file, activated either from txt files or from .spc files inside the content/speedcam folder.
Those icons found in the data.zip appear only if they are not included in the files mentioned above, but are contained in the map information, especially the Here maps.
The bmp icons are inside the folders of the various resolutions in ui_nextgen/res/common, and they are the ones that appear on the map.
In the nodpi folder there are the svg icons, those that are in the menus and those that appear in the alert icon, manipulating these svg icons is a bit more complicated, you have to use Adobe Illustrator.
Thanks for the quick reply.
My tab is a Asus Zenpad 7' (1024x600) that i use daily at work.
Spoiler: pic1
At dpi = 270 is perfect for the Keyboard
At dpi = 290 is perfect for the app
Spoiler: pics2
But the Keyboard
Spoiler: pic3
I know that's not the best resolution for my tablet,but,is there a way to change it?
Thanks
Last edited by Boki; 19th April 2019 at 06:22 AM.
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
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.
Wrong assumption
Put this values in sys
[rawdisplay]
dpi=300
base_dpi=240
Try to browse Forum next time.
Bookmarks