From: Dominik S. <do...@it...> - 2010-01-09 21:28:04
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When using white over back color scheme the legend() is unreadable, with apparently hard-coded white legend background - or is there a way to set it in the rc file? Dominik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAktI9NEACgkQ/EBMh9bUuzKvHgCg7HZbBpA+vMdLcCzfVvZcyARq JlsAnRGSuYMa0GXVnIG6M3RHrXGSOtQL =FlrY -----END PGP SIGNATURE----- |
From: Jae-Joon L. <lee...@gm...> - 2010-01-11 19:24:52
|
On Sat, Jan 9, 2010 at 4:27 PM, Dominik Szczerba <do...@it...> wrote: > When using white over back color scheme the legend() is unreadable, with > apparently hard-coded white legend background - or is there a way to set > it in the rc file? > Unfortunately no. I recommend you to manually change the color of the legend frame. l = plt.legend() l.legendPatch.set_fc(plt.rcParams["axes.facecolor"]) I'm not very kin to introduce a new rc param for this. I think it is good enough to have the legend background to follow the color of the axes, as above. I'll try to commit the relevant change soon. But any other suggestion will be welcomed. Regards, -JJ |
From: Dominik S. <do...@it...> - 2010-01-11 19:38:26
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jae-Joon Lee wrote: > On Sat, Jan 9, 2010 at 4:27 PM, Dominik Szczerba <do...@it...> wrote: >> When using white over back color scheme the legend() is unreadable, with >> apparently hard-coded white legend background - or is there a way to set >> it in the rc file? >> > > Unfortunately no. > I recommend you to manually change the color of the legend frame. > > l = plt.legend() > l.legendPatch.set_fc(plt.rcParams["axes.facecolor"]) > > I'm not very kin to introduce a new rc param for this. I think it is > good enough to have the legend background to follow the color of the > axes, as above. I'll try to commit the relevant change soon. > But any other suggestion will be welcomed. Hmmm, that property really deserves its own rc param, but if you do not like it, it should at least be somewhere automatically set to the current background color to be resistant against people like me ;) I would be happy to have such a fix... Thanks, Dominik > > Regards, > > -JJ > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAktLfhwACgkQ/EBMh9bUuzKcTACglg3AmZ8PYFztHoQKeMTe+Elj KrcAnRi8FCAOpY9Pe96+0MQPyTZ7cnQ4 =MknU -----END PGP SIGNATURE----- |
From: Jae-Joon L. <lee...@gm...> - 2010-01-11 20:12:19
|
On Mon, Jan 11, 2010 at 2:38 PM, Dominik Szczerba <do...@it...> wrote: > Hmmm, that property really deserves its own rc param, but if you do not > like it, it should at least be somewhere automatically set to the > current background color to be resistant against people like me ;) I > would be happy to have such a fix... > I just committed a change that makes the face- and edgecolor of the legend patch to match those of the axes patch. The reason I'm not very kin to introduce such new rc parameters is partly that, we actually needs a lot of rc parameters, not just the facecolor of the legend parch. What about the edgecolor of the legend patch, or the linewidth? Or the color of the legend text. What about the colors of the parch around the annotation text? I don't think it is desirable to add a new rc parameter for every property that needs to be customized. In my personal opinion, one of the the best way to customize the plot is to have something like CSS that supports inheritance of properties. So, I'm inclined to leave it as is. But other developers may have different thoughts. Regards, -JJ |