Gamer125 / fofix

Automatically exported from code.google.com/p/fofix
0 stars 0 forks source link

Hitglows' color hard-coded #1206

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
When hitglows' colors are defined as "same as fret" in the theme.ini, the 
hitglows appear to use hard-coded color values, as opposed to the defined fret 
colors as evidenced by the fact that 5th fret hitglows remain orange despite 
the fret color being changed to fuchsia.
This bug's been around for a while, and I have noticed it before. I couldn't 
find an issue for it though.

Original issue reported on code.google.com by death.au on 22 Jul 2010 at 11:47

GoogleCodeExporter commented 9 years ago
it also uses the glow image from /data rather than /data/themes/theme

Original comment by fuzio...@gmail.com on 22 Jul 2010 at 11:52

GoogleCodeExporter commented 9 years ago
This seems to have disappeared with blazin's latest Theme changes. Hitflames 
appear to remain hardcoded though.

Original comment by fuzio...@gmail.com on 2 Sep 2010 at 5:07

GoogleCodeExporter commented 9 years ago
I just pushed an update related to hitglow/flame settings. 
http://github.com/stump/fofix/commit/90a27b5d344f24f4ea9a54b7eff146b3b04f2445

You can now completely disable hitflames as well as set them to the default 
glow color.
I've also fixed the glow.png code so it will use the theme's version if 
available.

Unfortunately, setting individual hitflame colors (based on fret colors) was 
too convoluted for me to fix.. maybe someone else can take a look.

Original comment by fuzio...@gmail.com on 27 Sep 2010 at 10:46