Is there a way to enable/disable scrolling long street names? I know DIMKA does that. Or is it possible in sys.txt? Supposedly enabling this feature causes memory problems sometimes, so I am trying to find a way to turn it off.
Thanks
- Posts 128
- Location USA
- WRZ$
149.40
- Device IPAQ 310
And with a nod to the future iphoneOS 3.0, I give you kikker 3.0. As always, please report any bugs. See first post in this thread for screenshots.
Changes in this release:
1. Redesign of Cockpit fields area.
2. Redesign of the Turn Indicator in the main directional panel.
3. Smaller transparent 'zoom in' and 'zoom out' buttons.
4. Overspeed and round speedcam icon moved to left edge whether circular compass is shown or not.
5. Circular compass moves over to the right when overspeed/speedcam icon appears. Compass can still be turned off however.
6. Cockpit fields can have either a light or dark background. Dark background always shown in night mode.
7. Dark background of Cockpit fields allows for either "VFD Blue", "Orange LED", or "White Glow" colors of the field labels.
8. For IPAQ 31x users - Bluetooth Manager now accessed by tap of lower right corner in map mode, and Dial Pad now accessed in Cockpit mode.
Changes in this release:
1. Redesign of Cockpit fields area.
2. Redesign of the Turn Indicator in the main directional panel.
3. Smaller transparent 'zoom in' and 'zoom out' buttons.
4. Overspeed and round speedcam icon moved to left edge whether circular compass is shown or not.
5. Circular compass moves over to the right when overspeed/speedcam icon appears. Compass can still be turned off however.
6. Cockpit fields can have either a light or dark background. Dark background always shown in night mode.
7. Dark background of Cockpit fields allows for either "VFD Blue", "Orange LED", or "White Glow" colors of the field labels.
8. For IPAQ 31x users - Bluetooth Manager now accessed by tap of lower right corner in map mode, and Dial Pad now accessed in Cockpit mode.
- Posts 9
- WRZ$
50.90
Hi Kikker
Good work cockpit fields much better full width.
I found a minor problem with the release:
<Find Menu><Find POI><Around Cursor> = ! Failed to open file: blackstripe2.bmp exiting application
Added "blackstripe2.bmp" from release 2.5 and now all ok.
rgds Phill
Good work cockpit fields much better full width.
I found a minor problem with the release:
<Find Menu><Find POI><Around Cursor> = ! Failed to open file: blackstripe2.bmp exiting application
Added "blackstripe2.bmp" from release 2.5 and now all ok.
rgds Phill
Phill
GPS:- Chinese Navlink 5", CE 5 with PEZ-GPS Menu V2.0
Running:- Igo 8.3.4.102650 (Kikker 3.2 A18), Amigo 8.4.2.109504 (DJ Amigo 3.2.1), TomTom 910.9185, Navigon 7.4.2.802 & 7.4.3.201, Garmin XT V5.00.20W
GPS:- Chinese Navlink 5", CE 5 with PEZ-GPS Menu V2.0
Running:- Igo 8.3.4.102650 (Kikker 3.2 A18), Amigo 8.4.2.109504 (DJ Amigo 3.2.1), TomTom 910.9185, Navigon 7.4.2.802 & 7.4.3.201, Garmin XT V5.00.20W
- Posts 100
- WRZ$
65.90
I have tried this kikker 3.1. Great stuff, but 2 suggestions
1) Is there any way to show the speed limit on map screen always..? An option to turn off or on may be(Like in Ultra skin).
2) The growing on the turn indicator is a waste of resources and valuable screen real estate in my opinion. Nobody will look at it and the distance to the next turn is shown in big letters anyway. So, this must be removed.
1) Is there any way to show the speed limit on map screen always..? An option to turn off or on may be(Like in Ultra skin).
2) The growing on the turn indicator is a waste of resources and valuable screen real estate in my opinion. Nobody will look at it and the distance to the next turn is shown in big letters anyway. So, this must be removed.
- Posts 26
- WRZ$
51.50
Are there any chance that you will change the arrow to an car ?
- Posts 62
- WRZ$
31.30
IMO, the screen in the 320x240 version is a little cluttered. Having the status indicators wrap around to a second line makes the current road name squooshed up too tight. Is there was a way to remove the address numbers on the right and left of the street name? That's really not important data to have while navigating on most roads, and would open up some screen real estate.
- Posts 425
- Location Somewhere near Brigadoon
- WRZ$
804.60
- Device
HTC M9 / HTC Sensation XE (Viper + mods etc)/ +Trusty Mio C710 (modded) still going strong

- OS iOS6
Thanks kikker....nice clean skin BTW,
With 480 x 272 res, the speedcam icon overlaps the secondary distance to manuver.
This change needs to be made in speedcam_480_272.ui to make it right.
<SPRITE sprSCWSpeedCamera1 x=58 y=109 z=1 phasemodel="navigation.curr_speedcam.category" bmp="$speed_cams.spr">
<SPRITE sprSCWSpeedCamera2 x=59 y=111 z=2 phasemodel="navigation.curr_speedcam.enterexit" bmp="$speed_cam_enterexit.spr">
<SPRITE sprSC04 x=1 y=184 z=50 bmp="$speed_cam_speedlimit.bmp" >
<TEXT txtSC01 x=7 y=184 w=28 h=40 z=51 align="CENTER" fontsize=18 font="tahomabd" color=#000000 textmodel_wstr="navigation.curr_speedcam.speed_limit.number_text" visiblemodel="navigation.curr_speedcam.speed_limit.valid">
<TEXT txtSC02 x=7 y=184 w=28 h=40 z=51 text="!" visiblemodel="!navigation.curr_speedcam.speed_limit.valid" align="CENTER" fontsize=18 font="tahomabd" color=#000000>
;<SPRITE sprSC05 x=90 y=178 z=1 bmp="bgspeedlimit.bmp" >
<TEXT txtSCW_AvgSpeed y=142 w=30 glowsize=1 color=#FFFFFF color2=#000000 align="CENTER" fixedwidthnumbers=1 fontsize=16 font="tahomabd" textmodel_wstr="navigation.curr_speedcam.avg_speed.number_text" visiblemodel="navigation.curr_speedcam.avg_speed.valid" >
<TEXT txtSCW_AvgSpeedUnit y=146 w=16 glowsize=1 color=#FFFFFF color2=#000000 align="LEFT" fontsize=12 font="tahomabd" textmodel_wstr="navigation.curr_speedcam.avg_speed.unit_text" visiblemodel="navigation.curr_speedcam.avg_speed.valid">
<DIRDISTALIGNER xxx x=2 w=50 align="CENTER" control=txtSCW_AvgSpeed padding=4 control=txtSCW_AvgSpeedUnit>
<TEXT txtSCW_Distance x=58 y=142 w=36 glowsize=1 color=#FFFFFF color2=#000000 align="CENTER" fixedwidthnumbers=1 fontsize=16 font="tahomabd" textmodel_wstr="navigation.curr_speedcam.distance.number_text" visiblemodel="navigation.curr_speedcam.distance.valid">
<TEXT txtSCW_DistanceUnit x=59 y=146 w=10 glowsize=1 color=#FFFFFF color2=#000000 align="LEFT" fontsize=12 font="tahomabd" textmodel_wstr="navigation.curr_speedcam.distance.unit_text" visiblemodel="navigation.curr_speedcam.distance.valid">
<DIRDISTALIGNER xxx x=52 w=50 align="CENTER" control=txtSCW_Distance padding=4 control=txtSCW_DistanceUnit>
With 480 x 272 res, the speedcam icon overlaps the secondary distance to manuver.
This change needs to be made in speedcam_480_272.ui to make it right.
<SPRITE sprSCWSpeedCamera1 x=58 y=109 z=1 phasemodel="navigation.curr_speedcam.category" bmp="$speed_cams.spr">
<SPRITE sprSCWSpeedCamera2 x=59 y=111 z=2 phasemodel="navigation.curr_speedcam.enterexit" bmp="$speed_cam_enterexit.spr">
<SPRITE sprSC04 x=1 y=184 z=50 bmp="$speed_cam_speedlimit.bmp" >
<TEXT txtSC01 x=7 y=184 w=28 h=40 z=51 align="CENTER" fontsize=18 font="tahomabd" color=#000000 textmodel_wstr="navigation.curr_speedcam.speed_limit.number_text" visiblemodel="navigation.curr_speedcam.speed_limit.valid">
<TEXT txtSC02 x=7 y=184 w=28 h=40 z=51 text="!" visiblemodel="!navigation.curr_speedcam.speed_limit.valid" align="CENTER" fontsize=18 font="tahomabd" color=#000000>
;<SPRITE sprSC05 x=90 y=178 z=1 bmp="bgspeedlimit.bmp" >
<TEXT txtSCW_AvgSpeed y=142 w=30 glowsize=1 color=#FFFFFF color2=#000000 align="CENTER" fixedwidthnumbers=1 fontsize=16 font="tahomabd" textmodel_wstr="navigation.curr_speedcam.avg_speed.number_text" visiblemodel="navigation.curr_speedcam.avg_speed.valid" >
<TEXT txtSCW_AvgSpeedUnit y=146 w=16 glowsize=1 color=#FFFFFF color2=#000000 align="LEFT" fontsize=12 font="tahomabd" textmodel_wstr="navigation.curr_speedcam.avg_speed.unit_text" visiblemodel="navigation.curr_speedcam.avg_speed.valid">
<DIRDISTALIGNER xxx x=2 w=50 align="CENTER" control=txtSCW_AvgSpeed padding=4 control=txtSCW_AvgSpeedUnit>
<TEXT txtSCW_Distance x=58 y=142 w=36 glowsize=1 color=#FFFFFF color2=#000000 align="CENTER" fixedwidthnumbers=1 fontsize=16 font="tahomabd" textmodel_wstr="navigation.curr_speedcam.distance.number_text" visiblemodel="navigation.curr_speedcam.distance.valid">
<TEXT txtSCW_DistanceUnit x=59 y=146 w=10 glowsize=1 color=#FFFFFF color2=#000000 align="LEFT" fontsize=12 font="tahomabd" textmodel_wstr="navigation.curr_speedcam.distance.unit_text" visiblemodel="navigation.curr_speedcam.distance.valid">
<DIRDISTALIGNER xxx x=52 w=50 align="CENTER" control=txtSCW_Distance padding=4 control=txtSCW_DistanceUnit>
" We never really grow up, we only learn how to act in public
"
- Posts 128
- Location USA
- WRZ$
149.40
- Device IPAQ 310
jugulator wrote:I have tried this kikker 3.1. Great stuff, but 2 suggestions
1) Is there any way to show the speed limit on map screen always..? An option to turn off or on may be(Like in Ultra skin).
2) The growing on the turn indicator is a waste of resources and valuable screen real estate in my opinion. Nobody will look at it and the distance to the next turn is shown in big letters anyway. So, this must be removed.
1.) That's a pretty good suggestion. I'll stick that option in an upcoming release.
2.) I think it looks pretty good and easy to read. Besides, many like the indicator, which doesn't take up much space at all. Furthermore, it retracts off the page when not needed, and the background BMP shifts to the left, saving space. So, it only appears when you are within 300 meters of your next turn.
- Posts 128
- Location USA
- WRZ$
149.40
- Device IPAQ 310
@ gummismurfen - Yes, will probably add an option to add a car. But, I cringe every time I see cars on those maps. They don't move around like the nice vector-based cursor. So, it looks sort of funny when the car appears to be heading straight at a sharp curve in the road.
@ aremot - Will eventually add option for speedlimit to appear although a bit hesitant to add actual speed as well considering it's already an option for the cockpit fields.
@ gone down south - I might add the option for the address numbers to appear within a specified distance of the destination as well as the option to turn off altogether.
@ Kitzie - I purposefully use the secondary turn area for the speedcam icon. I think the presence of a speedcam trumps the importance of the secondary turn, and sticking the icon out into the map area looks a little out of place. The way it appears now is the same way the default skin has it. You can always tap it to remove the speedcam icon if you really need to see the secondary turn icon at that moment.
@ aremot - Will eventually add option for speedlimit to appear although a bit hesitant to add actual speed as well considering it's already an option for the cockpit fields.
@ gone down south - I might add the option for the address numbers to appear within a specified distance of the destination as well as the option to turn off altogether.
@ Kitzie - I purposefully use the secondary turn area for the speedcam icon. I think the presence of a speedcam trumps the importance of the secondary turn, and sticking the icon out into the map area looks a little out of place. The way it appears now is the same way the default skin has it. You can always tap it to remove the speedcam icon if you really need to see the secondary turn icon at that moment.
- Posts 420
- Location RO
- WRZ$
128.90
- Device Samsung Galaxy M52
- OS Android 13
Hy kikker,
I like very much your new skin
- the idea with speedlimit is good
- the growing left-side turn indicator is a nice/good thing.Dont erase it
- I think , an option for arrow - car ( who like it ) is welcome
Thanks for your work, fasiol
I like very much your new skin
- the idea with speedlimit is good
- the growing left-side turn indicator is a nice/good thing.Dont erase it
- I think , an option for arrow - car ( who like it ) is welcome
Thanks for your work, fasiol
- Posts 26
- WRZ$
51.50
when i have this
[roundaboutcam]
enabled=0
centery=20
in sys.txt the car in gj skin moves good
[roundaboutcam]
enabled=0
centery=20
in sys.txt the car in gj skin moves good
- Posts 35
- WRZ$
76.40
Did not find a bug yet (-: Did 30km of testing with VGA on HTC Touch Diamond.
In the gurjon skin the est. time of arrival is spoken by the TTS voice, a feature what i absolutly like - maybe thisone can also be build in (surely not important)
Will do some more testing with 3.01
In the gurjon skin the est. time of arrival is spoken by the TTS voice, a feature what i absolutly like - maybe thisone can also be build in (surely not important)
Will do some more testing with 3.01
