matplotlib-devel Mailing List for matplotlib (Page 10)

Erik Tollerud wrote:
> No one thinks this is worth committing to SVN? I find myself using it
> quite a bit in my own work - different fields have different ideas
> about the "right" way to draw a histogram, so it's good to have
> options, I think...
> 
> On Wed, Apr 2, 2008 at 4:39 PM, Erik Tollerud <eri...@gm...> wrote:
>> I've made some alterations to the hist() function in axes.py (attached
>> is a diff against the current SVN version). I've added the capability
>> to use the same interface to make outline histograms instead of bar
>> histograms (and a third option for outlines with fill - note that this
>> is NOT the same as calling it twice with the other two, as the widths
>> are slightly different). There's a slight compatibility issue in that
>> as it stands in that the returned tuple now has 4 values (I added a
>> list of the lines that are generated if the steps command is used),
>> but I can't really imagine how that could break anything but the
>> poorest-written code... Anyone think this is worth committing to SVN?
>>
>> (One thing that bothers me a little is the part of the code that adds
>> the last two edges to the histogram - the problem is that if you have
>> a line size greater than 1, the outline overshoots the rest of the
>> outline by a very tiny bit... if anyone knows how to cut off the upper
>> row of pixels to make it flush with the rest of the outline... it's
>> perfectly usable as-is, though - that's just a tiny little aesthetic
>> quibble)
>>
>> --
>> Erik Tollerud
>> Graduate Student
>> Center For Cosmology
>> Department of Physics and Astronomy
>> 4155B Frederick Reines Hall
>> University of California, Irvine
>> Office Phone: (949)824-2996
>> Cell: (651)307-9409
>> eto...@uc...
>>
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save 100ドル. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Hi Erik,
 thanks for the reminder. If no one else does ... I will have a look 
at your patch. Would be a good idea to provide an adequate example, but 
that should be no problem.
 Manuel

No one thinks this is worth committing to SVN? I find myself using it
quite a bit in my own work - different fields have different ideas
about the "right" way to draw a histogram, so it's good to have
options, I think...
On Wed, Apr 2, 2008 at 4:39 PM, Erik Tollerud <eri...@gm...> wrote:
> I've made some alterations to the hist() function in axes.py (attached
> is a diff against the current SVN version). I've added the capability
> to use the same interface to make outline histograms instead of bar
> histograms (and a third option for outlines with fill - note that this
> is NOT the same as calling it twice with the other two, as the widths
> are slightly different). There's a slight compatibility issue in that
> as it stands in that the returned tuple now has 4 values (I added a
> list of the lines that are generated if the steps command is used),
> but I can't really imagine how that could break anything but the
> poorest-written code... Anyone think this is worth committing to SVN?
>
> (One thing that bothers me a little is the part of the code that adds
> the last two edges to the histogram - the problem is that if you have
> a line size greater than 1, the outline overshoots the rest of the
> outline by a very tiny bit... if anyone knows how to cut off the upper
> row of pixels to make it flush with the rest of the outline... it's
> perfectly usable as-is, though - that's just a tiny little aesthetic
> quibble)
>
> --
> Erik Tollerud
> Graduate Student
> Center For Cosmology
> Department of Physics and Astronomy
> 4155B Frederick Reines Hall
> University of California, Irvine
> Office Phone: (949)824-2996
> Cell: (651)307-9409
> eto...@uc...
>