Skip to content

Marker disappears with markerfacecolor='None' when saving as eps file #11832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
arbolis opened this issue Aug 9, 2018 · 1 comment
Closed
Milestone

Comments

@arbolis
Copy link

arbolis commented Aug 9, 2018

Bug report

Markers disappear if I use markerfacecolor='None', when saving as eps file. if I save as png file, they are correctly displayed.
Note that markeredgewidth is correctly set to a non zero value and markeredgecolor is correctly set to a color. As I said, the figure is correctly produced when saved as png, so it should really work similarly for eps figure, but it doesn't.

Code for reproduction

I'm too lazy for a complete reproducible example. But here are the relevant lines.

axe.plot(x, y, linestyle = '-', linewidth=0.5, marker = 's', markeredgewidth = 0.5, label='something', c
    lip_on= False, markersize = '3',markerfacecolor='None', markeredgecolor='green', color='green')

plt.savefig('another_name_come_on_not_this_again.png', format='png', dpi=400)
plt.savefig('another_name_come_on_not_this_again.eps', format='eps', dpi=400)

Only the line is displayed. No marker.

Expected outcome

As said above, the edges of the makers should be displayed, as in the case when the picture is saved as png. But they aren't.

Matplotlib version

  • Operating system: GNU/Arch Linux.
  • Matplotlib version: 2.2.2.
  • Matplotlib backend (print(matplotlib.get_backend())): Qt5Agg
  • Python version: 3.7.0.
@tacaswell
Copy link
Member

Thanks for reporting this. You were only two calls to np.random.rand away from a reproducible example!

This is a duplicate of #11372 and #10921 which was fixed on master via #10935 and backported to 2.2.x via #10937.

2.2.3 and 3.0rc1 (which should be tagged any day now) will have this fix.

@tacaswell tacaswell added this to the v2.2.3 milestone Aug 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants