Thread: RRGAS - Gas prices for the US - Status: Updated 12/01/10

Ok, revised theory

It looks like whichever plugin it goes through last will have the indicators working. But will kill it for every other plugins indicators.

I'm looking at the source from 26 Oct 2007, which on deeper invetigation shouldn't be affected by this, so I can only suppose that something has been changed in the source code since then.

Originally Posted by ThunderStick

The only thing I dont like is that it displays the Gas station names in lower case, would be great if they were all uppercase.

It has now been changed so that the first letter is capitalised, and if the name is only two characters ie BP they are both capitalised.

Further update.

Just went back to 26th October 07 executable and the indicators work fine in two plugins, whereas they don't in the later versions.

Originally Posted by ThunderStick

will this work with IG4

gasnav works with ig4 as long as you have enabled coordinates

Originally Posted by Enforcer

It has to be the way the plugin is handling the Indicator code.

Having a quick look at the way RR handles the Indicator codes with regards to extensions, it looks like the plugin has to return one of the following

'false' - if the indicator is not processed by this plugin
'true' - if it is and it's to be changed to true.
path to graphic file - if it's to show a graphic.

Now if a plugin returns anything other than 'true' or 'false' that indicator path will take on that value as it's path.


so if a plugin has been written that doesn't have the line

ReturnIndicator = "False" as a default for when it doesn't process it, it will mess that indicator and anyone else's indicator up.

Also another possibility.

If the value of IND is changed in the plugins indicator routine, that will also change the name of the indicator that RR will look for.

Originally Posted by Enforcer

Ok, revised theory

It looks like whichever plugin it goes through last will have the indicators working. But will kill it for every other plugins indicators.

I'm looking at the source from 26 Oct 2007, which on deeper invetigation shouldn't be affected by this, so I can only suppose that something has been changed in the source code since then.

This is what I thought that ending thoughts were on the disscution between me,sonic, and guino. My plugins have always left that line just as it says in the comment directly above the line "ReturnIndicator="false".

Originally Posted by monkeyracer

The root of the issue is that there are some plug-ins that need to be loaded in a certain order, if you have two that need to be loaded last, only one wins. Someone want to make a plug-in manager plugin?

Actually, Blue made a fantastic Plugin Manager for me for use in the DFX skin. It can turn on and off the plugins from within the skin, and saves the X, lines to an include file. Then all that is needed is X,PluginManager in the menu.skin.

The only problem, and not a fault of BLue's plugin, is they are simply in alphabetical order. There is no way for it to know what plugins are friendly, not friendly, need to be at the bottom, if there are 2 fighting to be at the bottom and loaded last ect....

Originally Posted by Enforcer

Ok, revised theory

It looks like whichever plugin it goes through last will have the indicators working. But will kill it for every other plugins indicators.

I'm looking at the source from 26 Oct 2007, which on deeper invetigation shouldn't be affected by this, so I can only suppose that something has been changed in the source code since then.

Originally Posted by Enforcer

Further update.

Just went back to 26th October 07 executable and the indicators work fine in two plugins, whereas they don't in the later versions.

So, what do we do to fix it?

Are we to now assume that there will be an official release instead of all these beta's floating around?

this order works for me:

/, X, Extension Name
X,powermon
X,RRStrings
X,Mp3Art
X,rrgas

but... that's really just a temporary solution...

Originally Posted by monkeyracer

So, what do we do to fix it?

Are we to now assume that there will be an official release instead of all these beta's floating around?

Well I think Guino needs to be made aware of my theory, and if it's true make the neccesary changes, however his time is mimited at the moment and there are quite a few 'quirks' at the moment.

Going back to an older version (12th October) but then you lose the weather and any other enhancements that are more recent updates.