Switch to full style
Post a reply

Primo 1.2 & Dimkawa skin problem

Thu Oct 06, 2011 10:57 pm

Guys,

I'm running Primo 1.2 with Dimkawa 1.3.7 skin & I have a small problem with the speed limit warning display.

The problem I have is when I go over the speed limit in a 50 km/hr zone (Australia) & the speed limit symbol changes to yellow to indicate that I'm speeding, the numbers disappear from the centre of the circle.
The numbers in the circle are replaced by 3 black dots [SIZE="6"]...[/size]

When I go below the speed limit again & the yellow disappears, the numbers return & the display is normal again.

What's strange is it only seems to happen in a 50 km/hr zone, all other speed zones (as far as I've tested) display the numbers correctly.
I haven't noticed it happen when using the default skin so I guess it's Dimkawa skin related.

Is there any way to have the numbers display correctly?

I'm thinking maybe there's a corrupt image somewhere.
I'll have a dig around but it's out of my league.

Cheers.

Fri Oct 07, 2011 5:44 am

Sounds like something somewhere is corrupt, yes. With same skin, my "overspeed" changes to [color="red"]red[/color], also...are you sure yours goes to [color="yellow"]yellow[/color]?

In any case, try replacing the skin.zip(s) with a new downloaded copy from here:
:link:
No need to make any other changes..just power Primo down, replace the skin.zip(s) in Content/Skin. If the downloaded one has a different name from the one you are replacing, (such as diMkaWA_P136_day.zip vs the new one as diMkaWA_P137_day.zip), change the name of the new one to match the old one (ie change diMkaWA_P137_day.zip to diMkaWA_P136_day.zip, etc), then you will not have to make any new configurations within Primo..it will just start right up with all your settings in place, but actually be the newer version running.

Fri Oct 07, 2011 9:18 am

Yep. Definitely changes to yellow.
The background of the circle I mean. Red circle with white centre changes to red circle with yellow centre when overspeeding.

I'll download the skin again as you suggested, but I only downloaded it from there less than 1 week ago.

I'll give it a try nonetheless.

Fri Oct 07, 2011 9:41 am

Stuff like this is always the process of elimination.
First is to make sure the skin.zip is OK.
Next may be to change the day/night color scheme to make sure that is not related.
Then, it may be that a graphic for your particular resolution within the skin files may be missing or corrupt.

HiroboFreak wrote:The background of the circle I mean. Red circle with white centre changes to red circle with yellow centre when overspeeding.


Ah. OK...that's normal then.

Sat Oct 08, 2011 8:57 am

Fresh download & reinstall - Problem persists.
Day skin - Problem persists.
Night skin - Problem persists.

:doh:

Only in 50 km/hr zones.
Anyone else having this issue?

Sat Oct 08, 2011 9:36 am

What resolution is your device? When the text is too big to fit into the space allocated by the skin it puts three dots ... to indicate that the text continues, It may be a problem that's only related to your resolution and KPH format displays. I'll have a look into the skin and find what element controls the spacing, giving it more room may help.

Sat Oct 08, 2011 10:06 am

HiroboFreak wrote:Fresh download & reinstall - Problem persists.
Day skin - Problem persists.
Night skin - Problem persists.

:doh:

Only in 50 km/hr zones.
Anyone else having this issue?


I have the same issue with navteq map not with Teleatlas!

Sat Oct 08, 2011 10:27 am

Fatboyfun wrote:What resolution is your device? When the text is too big to fit into the space allocated by the skin it puts three dots


Does not happen (at all, at any speed limit) with 480x272, so my guess would be a 'fault' in 480x234 or 800x480 in the template within the UI folder...OR...the correct font is not in use.
Not sure about his, but in mine the FONT folder is under Primo/ with the digital.ttf supplied with the skin.

Sat Oct 08, 2011 11:27 am

Fatboyfun wrote:What resolution is your device? When the text is too big to fit into the space allocated by the skin it puts three dots ... to indicate that the text continues, It may be a problem that's only related to your resolution and KPH format displays. I'll have a look into the skin and find what element controls the spacing, giving it more room may help.


Mine is 800x480 resolution.
Good point, however it displays correctly when speeding in 110 km/hr zones so one would assume there is enough space.

I'll check that the font folder is in the correct place.
I thought the digital.ttf font was only for the screen saver?? (the option is there somewhere to display that font in the screen saver)

Sat Oct 08, 2011 1:03 pm

HiroboFreak wrote:I thought the digital.ttf font was only for the screen saver?? (the option is there somewhere to display that font in the screen saver)


I believe that is correct. However, at other resolutions some sort of font replacement may be called for. Or not. It was just a guess.
Really odd that any other two digit (or THREE digit) speed over-limit displays OK, but not 50, and only 50.

Sat Oct 08, 2011 1:09 pm

I've never seem this problem on my 480x272 devices, but in the past when I was experimenting with skins I did see what you describe, but it seems odd that it only affects 50 KPH overspeed, and a three digit speed display works.

Sat Oct 08, 2011 8:59 pm

& even stranger, 50 displays fine normally, only plays up when overspeeding. :scratch_one-s_head_

I guess I can live with it if it can't be resolved, definitely a bug though.

Sun Oct 09, 2011 2:38 am

Use the voice notification for speeding.
Better than watching a screen to see what youre doing wrong. ;)
Bazzle

Sun Oct 09, 2011 8:34 pm

I realise I can do that.
I'm after a solution for the issue.

Wed Oct 26, 2011 3:05 am

HiroboFreak wrote:I'm after a solution for the issue.


There is a new version of the skin recently released--P1.3.8:
http://www.navitotal.com/forums/showthread.php?6625-diMka-WA-P1.3.8-Skin-for-iGO-Primo-1.2

Whether this release addresses whatever is causing your issue is unknown by me, but it certainly could not hurt to try it.
Post a reply