set the xlim will force the X-axis within 1-9, the line segment outside 1-9 hide, but it just hide not be clipped, I don't know how can i actually clip elements with axes extent.
I use Adobe Illustrator to open eps file.
You see it is fine,
But actually it is,
In sometimes, this characteristic is very useful, for example, if one use plt.show() to use the interactive mode, one can drag the canvas to left or to right to see the whole line in the range 0-10.
But in eps file, i do not think this characteristic reasonably, it typically increases the eps file size. Is it a method to change this behavior ?
Matplotlib: 1.5.X or 2.0.X
OS: Windows 10 or CentOS
On Mon, Jul 17, 2017 at 12:19 PM, Thomas A Caswell ***@***.*** > wrote:
That isn't quite how how the panning works; each time the plot updates it
is fully re-drawn.
Looking at the code (in matplotlib.backends.backend_
eps.RendererPS.draw_path at https://github.com/
matplotlib/matplotlib/blob/master/lib/matplotlib/
backends/backend_ps.py#L493 and https://github.com/matplotlib/
matplotlib/blob/master/lib/matplotlib/backends/backend_ps.py#L470 ) it
looks like it *should* be clipped before outputting to the eps file.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8901 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARy-AV4OtVcCE0w0hD_cIqp8DYkykHMks5sO4cpgaJpZM4OZdvj>
.
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
If I run this and open in evince, the lines are correctly clipped, but if I open it in Scribus, then they are not. This might be just a viewer problem, but perhaps there is some less-defined behaviour we are using that could be improved.
After a bit of review of what Scribus appears to do, and what is in the original report, we've come to the conclusion that this is expected behaviour. The line appears to be selected in the original post, so while it appears bigger, it is clipped to the Axes box, but just its data continues outside of it. However, testing confirms that the line data is cropped to the Figure bounds. While we could increase that cropping to the Axes itself, that won't necessarily save output size that much given the existing cropping. I think there's an existing issue already for better clipping (#9488 and similar), so we'll close this one.
Activity
tacaswell commented on Jul 17, 2017
That isn't quite how how the panning works; each time the plot updates it is fully re-drawn.
Looking at the code (in matplotlib.backends.backend_eps.RendererPS.draw_path at https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/backends/backend_ps.py#L493 and https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/backends/backend_ps.py#L470 ) it looks like it should be clipped before outputting to the eps file.
WeatherGod commented on Jul 17, 2017
tacaswell commented on Jul 20, 2017
The dash pattern is set on the graphic context and I am pretty sure I reproduced this with solid lines...
github-actions commented on Apr 15, 2023
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
QuLogic commented on Apr 19, 2023
If I run this and open in evince, the lines are correctly clipped, but if I open it in Scribus, then they are not. This might be just a viewer problem, but perhaps there is some less-defined behaviour we are using that could be improved.
QuLogic commented on Apr 20, 2023
After a bit of review of what Scribus appears to do, and what is in the original report, we've come to the conclusion that this is expected behaviour. The line appears to be selected in the original post, so while it appears bigger, it is clipped to the Axes box, but just its data continues outside of it. However, testing confirms that the line data is cropped to the Figure bounds. While we could increase that cropping to the Axes itself, that won't necessarily save output size that much given the existing cropping. I think there's an existing issue already for better clipping (#9488 and similar), so we'll close this one.