Skin iGO nextgen by pongo (DISCUSSION)

**BIRBANTE** · 18th April 2019, 07:05 PM

Originally Posted by Troburn

Hello, i am trying to replace traffic light icon within skin with a simpler version,...... but old icon is still display, at a loss to find and other locations to replace....

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.

**Blackttulip** · 19th April 2019, 12:18 AM

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

**Boki** · 19th April 2019, 06:25 AM

Wrong assumption

Put this values in sys
[rawdisplay]
dpi=300
base_dpi=240

Try to browse Forum next time.

**vasile1955** · 19th April 2019, 09:12 AM

Update 19-04-2019 Skin iGO nextgen by pongo

Updated skin, in principle, nothing new, just a lot of technical changes, optimization in plug-ins, switching options for speedcams to be in the section "Load, unload plugins"

Spoiler: Link

Thanks Pongo

**quartzo** · 19th April 2019, 09:28 AM

[Only registered and activated users can see links. ]

Skin_iGO_Nextgen_by_pongo+ux_plugins_2019.04.19

Updated Skin iGO nextgen by pongo ,

- in principle, nothing new, just a lot of technical changes, optimization in plug-ins, switching options for speedcams to be in the section "Load, unload plugins"

P.S.
In the default, added code 5 - a multifunctional camera, which in the original does not exist at all

Thanks to pongo.

**nawaf** · 19th April 2019, 07:06 PM

thanks quartzo for the updat ....
one note on this update :
I had problem with favorites button in the cockpit ... once clicked it closes the app...
I had to revert back to: button_favorites.zip from previous UX .... and now the favorites button works.

I am not sure others have the same problem or not!
thanks again

**MarcNow** · 19th April 2019, 08:11 PM

And what about great UX "ad_waypoint"? is it discontinued?

**userninenine** · 19th April 2019, 08:54 PM

Confirmed: Problem with favorites button in the cockpit ... once clicked it closes the app...

Also cannot find "switching options for speedcams to be in the section "Load, unload plugins" " - still there as in the past.

**BIRBANTE** · 19th April 2019, 09:21 PM

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

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.

**Boki** · 20th April 2019, 10:05 AM

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.

Thread: Skin iGO nextgen by pongo (DISCUSSION)

Thread Tools

Display

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions