RedGreen doesnt honour default background colour when painting

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install Brad Wilson's Dark theme (or any other theme that uses a
non-white background colour)

When painting, RedGreen doesnt use the default background colour and thus
produces a white bar as long as the function definition, just above it.

I also dont agree with the way that this functionality (hiding the Test
Attribute) obscures stuff like:
a) the Test framework type involved
b) any parameters to the Test/Fact attribute
(until I move the caret into the attribute)

If there was a way to just turn it off via an option dialog, that would be
ducky.

(This is a separate issue but I've already added two to the list and I dont
want to go buffing people - exposing some more actions so they can be bound
to keys like TD.NET does would be nice (stuff like rerun the same tests).)

Original issue reported on code.google.com by bartel...@gmail.com on 19 May 2009 at 11:14

[GoogleCodeExporter]

Original comment by RoryBec...@gmail.com on 19 May 2009 at 11:17

[GoogleCodeExporter]

As covered in #15, I understand the painting better now.  I think you should be 
able
to see the text though, so making the background have a degree of opacity might 
help?

Original comment by bartel...@gmail.com on 21 May 2009 at 9:55

[GoogleCodeExporter]

I thought I'd always been using the background color, but obviously, I wasn't. 
I 
fixed that in the last bit of code committed. Rory has started a build, so you 
should see a fix for this any moment.
Jim

Original comment by tenHoleH...@gmail.com on 21 May 2009 at 12:39

[GoogleCodeExporter]

... and are you adding opacity :P Is there a way to make it configurable or are 
you
intentionally keeping it options dialog rot-free?

Original comment by bartel...@gmail.com on 21 May 2009 at 3:33

[GoogleCodeExporter]

I am intentionally on a limited time Open source projet :P 
Really, I'd love help from anyone. These days I get about 30 minutes a week to 
spend 
on this. Sometimes more sometimes less. 
I haven't looked into the opacity part, but knowing DevExpress tools, it should 
be 
doable. I was hiding the text because one of my initial ideas was to have a 
uniform 
view of the testing world you write a [Fact] your cube buddy writes [Test] and 
it 
doesn't matter all come out the same. It may not have been the best idea, but 
this 
is an experiment.

Original comment by tenHoleH...@gmail.com on 21 May 2009 at 4:12

[GoogleCodeExporter]

How anyone finds the time at all baffles me.... I'd love to have the time to 
invest
but would find it too hard to justify to the other things in my life clamouring 
for
my time.  If only I was 15 years younger!

Re presenting tests in a way that makes the type of framework a secondary 
concern -
If you want to paint the word "Test" in a uniform manner, and still surface all 
the
detail of the marker attribute I guess that's going to be complex as you're not 
just
adjusting display parameters anymore. I'd be guessing that from both 
visualisation
and implementation perspectives it would be easier to tweak the attributes of 
the
text than try to replace it.  But then I've never had the time to absorb a Mark
Miller walkthrough sequence on all this... Hey, arent MS making this all _so_ 
easy in
10 anyway :P

Anyway, thanks for letting me dump in my mad requests and not completely 
laughing
them out of court :D

Original comment by bartel...@gmail.com on 22 May 2009 at 9:19