matplotlib-users Mailing List for matplotlib

Hi
Hmmm now that you mention antialiasing ... I turned it off in my 
.matplotlibrc but my plots (GTKAgg on Linux) are still antialiased. I 
had the same problem on Win (TkAgg) but didn't bother too much. I 
remember that there was a discussion before about this. I'm using mpl 
0.81. Would upgrading fix this issue?
cheers,
steve
Robert Kern wrote:
> Steve Schmerler wrote:
> 
>> Hi
>>
>> Well this is kinda strange. I checked with gsview (on Win) and ggv and
>> gv on Linux. The 'mixed' points (4 and 5) _are_ purple/dark red while
>> the others are blue and (light)red.
> 
> 
> I blame antialiasing. Using Preview.app on OS X, when zoomed out, yes, I 
> can see that the middle points appear to be somewhat darker than the 
> "pure" red ones. Zooming in, however, I see little difference except for 
> a bit of fuzz. Using "DigitalColor Meter.app", I can verify that the 
> color of the middle crosses is indeed pure red with some purplish fuzz 
> at the edges. When zoomed out enough, all of the pixels are antialiased 
> fuzz and so it mixes both the top color and the bottom.
> 
> IOW, it's an issue with how the display program handles antialiasing of 
> overlaid colors, not the output generated by matplotlib.
> 

Steve Schmerler wrote:
> Hi
> 
> Well this is kinda strange. I checked with gsview (on Win) and ggv and
> gv on Linux. The 'mixed' points (4 and 5) _are_ purple/dark red while
> the others are blue and (light)red.
I blame antialiasing. Using Preview.app on OS X, when zoomed out, yes, I 
can see that the middle points appear to be somewhat darker than the 
"pure" red ones. Zooming in, however, I see little difference except for 
a bit of fuzz. Using "DigitalColor Meter.app", I can verify that the 
color of the middle crosses is indeed pure red with some purplish fuzz 
at the edges. When zoomed out enough, all of the pixels are antialiased 
fuzz and so it mixes both the top color and the bottom.
IOW, it's an issue with how the display program handles antialiasing of 
overlaid colors, not the output generated by matplotlib.
-- 
Robert Kern
rk...@uc...
"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
 -- Richard Harter

Hi
Well this is kinda strange. I checked with gsview (on Win) and ggv and
gv on Linux. The 'mixed' points (4 and 5) _are_ purple/dark red while
the others are blue and (light)red.
cheers,
steve
N. Volbers wrote:
> Steve Schmerler schrieb:
> 
>> Hi
>>
>> Here the test. As you can see the points 1,2,3 are red, 4 and 5 are 
>> purple and 6 and 7 are red.
>>
>>
> 
> Hello Steve,
> 
> I used ghostview (gv) on Linux to display the .eps and it looks 
> perfectly fine -- only blue and red crosses. Might this be a display 
> problem of your eps viewer?
> 
> Best regards,
> 
> Niklas.
> 
> 

Steve Schmerler schrieb:
> Hi
>
> Here the test. As you can see the points 1,2,3 are red, 4 and 5 are 
> purple and 6 and 7 are red.
>
>
Hello Steve,
I used ghostview (gv) on Linux to display the .eps and it looks 
perfectly fine -- only blue and red crosses. Might this be a display 
problem of your eps viewer?
Best regards,
Niklas.

On Wed, 2005年07月20日 at 20:27 -0700,
mat...@li... wrote:
> Hello everyone,
> 
> I just upgraded my matplotlib from 0.80 to to 0.83.1 and discovered a bug in the GTK backend. To be specific, the following code, beginning by line 171 in backend_gtk.py, is the problem:
> 
> 
> def motion_notify_event(self, widget, event):
> if event.is_hint:
> x, y, state = event.window.get_pointer()
> else:
> x = event.x
> y = event.y
> state = event.state
> 
> # flipy so y=0 is bottom of canvas
> y = self.figure.bbox.height() - y
> 
> if state:
> FigureCanvasBase.motion_notify_event(self, x, y)
> return True
> 
> 
> 
> Due to the 'if state' clause, the Canvas will only receive the 'motion_notify_event' if at the same time the mouse button is pressed. This has not been the case in previous version of matplotlib. There is e.g. no such distinction in backend_qt.py.
> 
> Regards,
> 
> Niklas Volbers.
I agree, the if clause should not be there, and have removed it from
cvs. If the state information is required it should be passed as an
argument to FigureCanvasBase.motion_notify_event() , like x and y are.
Regards
Steve
Send instant messages to your online friends http://au.messenger.yahoo.com