Thread: Who has iGuidance 2.1?

Originally Posted by Marvin Hlavac

Well, to be technically correct, I wouldn't say the new 2.1 doesn't "allow" it. I'm sure the 2.1 is ready for doing the same (or more) if a proper *.ini is introduced. It is just that the old theme.ini is not working in the new 2.1, and that users like us haven't figured out on our own yet how to modify it to work in the 2.1.

Hopefully the developer of the software will make a new *.ini file available so we can have some more fun again ;-)

Actually, some one contacted INAVCORP regarding theme.ini and version 2.1,and they specifically said that it is not supported. You can find the post in the "IG Font is killing me......" thread

Michael

Okay, it does seem to work (finally). I've been playing with it for a few moments now... Rename the file to ctheme.ini ;-) It does seem to work in 2.1 ;-)

Yes, it is described in this thread: close to the bottom, the second posting above the posting by iNav_Product. It does make sense that they renamed the file, they wanted users to see how "they" configured the new 2.1 version, they didn't want the old "customized" settings to interfere with our upgrades from 2.0 to 2.1.

It may actually be safer to start experimenting with creation of ctheme.ini just by putting in the file the bare minimum of what you need, let's say just the fonts, and then, step-by-step add a new item and see if it still works ;-)


I started by saving just this in Notepad, and named it ctheme.ini

; street name font size in points @ zoom level
STS=20 20 20 20 20 20 20 20 20 20 20

Originally Posted by Marvin Hlavac

Yes, it is described in this thread: http://www.gpspassion.com/forumsen/t...TOPIC_ID=28166 close to the bottom, the second posting above the posting by iNav_Product. It does make sense that they renamed the file, they wanted users to see how "they" configured the new 2.1 version, they didn't want the old "customized" settings to interfere with our upgrades from 2.0 to 2.1.

It may actually be safer to start experimenting with creation of ctheme.ini just by putting in the file the bare minimum of what you need, let's say just the fonts, and then, step-by-step add a new item and see if it still works ;-)


I started by saving just this in Notepad, and named it ctheme.ini

; street name font size in points @ zoom level
STS=20 20 20 20 20 20 20 20 20 20 20

K, it's experts like you that make me happy. So, any chance you want to look through my Routis.exe. and see if we can do the same thing, with theme, ctheme, heck, any *theme, to get the same changes made?

Michael

No, it will not work I don't think, because Routis 2004 is the same as iGuidance 1.1, and the theme.ini was introduced in the 2.0 version. However, I do plan on installing the old Routis on my home computer for the reason that I want to take some comparison screenshots so I can revisit an old issue of mine which is the too wide roads in 3D-view mode in 2.0 and 2.1 versions. When I do install it, I will have a look.

Btw, is it just me, or is there any one else who hates the new road width? I just liked it the way it used to be in Routis in 3D-view mode.

Michael, I just got home from work and on my home pc I uninstalled iGuidance and installed Routis (they cannot live together ;-) I checked for the possibility to use *.ini file the same way it's done in iGuidance, but I'm sorry to say it will not work with that version :-(