REQUEST : rr.ini setting available in skins

**Enforcer** · 03-11-2006, 01:51 PM

As the title says.

Is it possible to make the settings in rr.ini available to skins.

for example I would like the path of the external GPS to be available, so that when I want the skin to go to full size, I have the correct path, without the user having to adjust it manually.

This isn't the only one that would be useful, so can this be done?

**guino** · 03-11-2006, 07:09 PM

can be ADDED easily.. just make a list of everything you'd like to use and how you'd like to use it..

**fliplap** · 03-11-2006, 08:14 PM

indeed, things like variables and includes would be really useful.

I'd like to be able to put something like:
INC, general.skin

in almost every one of my skin files. In general.skin would be a bunch of header labels/indicators/buttons I use, as well as maybe paths to programs or logos, things like that.

**Enforcer** · 03-12-2006, 08:26 AM

Originally Posted by guino

can be ADDED easily.. just make a list of everything you'd like to use and how you'd like to use it..

At the moment it is mainly for paths. etc

Well one way would be to say enter the category before the = and get the bit after the =

eg

B,000,450,200,050,"LOAD;gps-full.skin;iGPS;e:\Program Files\iNav\iGuidance\iGuidance.exe;iGuidance"

would become

B,000,450,200,050,"LOAD;gps-full.skin;iGPS;!gpspath!;iGuidance"

Obviously use something else instead of the !'s if necessary.

Oh and can we add a command to get the RR install path as well and allow it to be used in paths within skins.

cheers

**liquid_smoke** · 03-12-2006, 12:34 PM

thats a good idea, i would like something like this also.
so making multiple screens for GPS would be easier for end users to setup.
also making multiple web browser screens, (currently having issues doing this).
But im not sure if just including these paths avail to the skin is the best solution as the input to change the settings would be a step back.
Now if i could create a skin that listed all the paths and editable from inside the skin, and saved somewhere inside the skin, would be the best option.

overall, i think all the settings that could be moved to skin specific settings, should come with the ability to be set and configured from inside the skin. Otherwise things just get more confuseing as to where and how you setup everything. So far you have RR.ini, ExecTBL.ini x2, KetTbl.ini, Gestures.ini and prob some others. I really think there needs to be a redesign on how RR gets configured. Even it were just a frontend to all these different .ini files (best route). It will only get worse and more confuseing with the current setup.
I think this should be top priority over any additional features i or others may want. It will increase the user base, give RR a more level of professionalism, and make things easier for everybody.
Sorry to go on and on about this!
But take a look at the setup routine for Centrafuse, its best feature by far if you ask me. CF will win a whole lot of users based solely on its ease of setup, users i think, would be better served with RR.
Currently if i were to reccomend a frontend to a total newbie or even a friend, i would almost have to reccomend CF ONLY because i dont want to have to deal with any of there setup issues and when they are comfortable with carputers tell them to step up to RR for the advanced user.

**guino** · 03-12-2006, 01:19 PM

I'll see what I can do about the settings and the includes..

In regards to the config tool.. this is my last priority... I rather like that only the users with a minimun level or experience and determination use RR (they tend to provide better feedback and information regarding issues) -- at least while RR is in development/testing.. a config tool for everything maybe worked out later, but personally I won't get to it in a long while.. in fact, the only reason why there's the current config tool is because users took the initiative of doing most of it (Mr. Wizard, drait, skippy76, etc).. or you'd still be editing INIs manually for everything following readme.txt...

**liquid_smoke** · 03-12-2006, 03:34 PM

Originally Posted by guino

or you'd still be editing INIs manually for everything following readme.txt...

ouch, that would be rough. I dont think that the lack of an easy config will filter out all the people with low experience but true for most. I wanna lure those that DO have the technical know how, but are just lazy, like me.
lol.

well im gonna have to start up some graphics for a new config tool to try to lure someone to code it to work. If you build it they will come right? LOL.

thanks guino.