Quote: Originally Posted by
MrTrunks 
My exectbl was empty besides like 5 lines that didnt look like they did anything anways...I used the exectbl.ini that you posted for the muted preset bug in its place and removed the locate like you said.
I'm using com port 5. I also checked my rr.ini and localdatacapture is set to 0. I am guessing that this means disabled. I'll let you know what happens tomorrow.
Thank LS
EDIT:
I just noticed there is an exectbl.ini in the road runner root folder and also in the lsx skn folder....Which one is being used? Should I delete one of them?
EDIT 2:
I couldn't wait...I went out to my truck and tried what you said. By removing locate from the exectbl.ini, this fixed the problem, I am able to exit and then open RR again and it starts fine whereas before when I exited and tried to start RR it froze at the locate command!
Do you plan on making the locate command on initial start to be an option to be turned on and off in setup? I'm not sure if others had this same problem as me but having a toggle button is much easier and also having it set to off by defaulted lsx install. This all make sense? Thanks LS!
what i figured, seems the locate bug is still around. Ill talk to guino about it.
There are 2 Exectbl.ini files. One is local and one is global.
The local one is the one that comes with a skin, so all code that is in the local version will only work with that skin. The global one (inside RR root) works across all skins.
It is safe to delete the global file, only if you havnt edited it with your own stuff.
It is NOT safe to delete the local version. Its the glue that binds RR, my skin and my custom code together in a happy 3 way action.
in light of the locate issues lingering around, i think i will set it up as an option that can be turned on/off and off by default.
If your location is off by 20 miles or so, you need to update your zips.dat file with more recent data. There is a thread around here somewhere with links to newer versions of this file.
Quote: Originally Posted by
montgomeryt But isn't this DLL needed for find location for things like the Gas finder and so on ?
i dont think that dll is needed by RoadRunner for a while now. I do not have it and everything still works.
Quote: Originally Posted by
hari-bhari is there currently any way to search for a song by its title? i.e. if the song is named 'good morning', is there any search feature where i can type part of the name and itll bring me a list of songs containing the text. someone pleaaaaaaase enlighten me.
YES AND NO
The code for searching is there, but the button is not visible to the user. If you disable ilist on the audio_browser.skin you will see the search button.
It was not intentional to remove the search feature from being accessed, but as it is now there is no way to search for anything. What i think ill do is post a new audio_browser.skin file that will split the playlist button in half and put search on the right side of that button. I may do this in the next 5 min or so, so look below or on the first page for the link.
Quote: Originally Posted by
bobbykokinos I have the exact same problem but, I've asked several questions and am having a hard time getting any answers in here.
I did the same thing as you, tough. I turned off the GPS functionality in RR but still have iGuidance running. I don't think XPort has anything to do with it. I think its the option where it shows you what city you are in (which is always usually 20mi off for me for some reason anyway so its pretty useless) on the main screen or it has something to do with the fuel finder. My RR is running but I have no speed or compass in RR because its all disabled.
see above
Quote: Originally Posted by
mnickolson Can someone tell me were the 2 presets are stored to get the band button to work. I have tried and tried and am to the point of just giving up. I got to thinking if I knew were it was stored I could just put them in I think.
band button?
Linear Mode
