It would be awesome if it were possible to control the linewidth of the hatch effect, for example in fill_between. It is now only possible to set the linewidth parameter, but that also gives the filled area a border, which can be undesired. Is it possible to allow for a dictionary to be passed to a "hatch_kwargs" parameter, that allows you to set the linewidth, hatch-style and possibly other things?
@jkokorian Want to take a crack at add that feature? This might not be the gentlest introduction to the library but might be fun!
The code for the hatch width for AGG is now in src/_backend_agg.h (as it is templated c++). I think that the way you would have to get the new information in would be to add it to the graphicsContextBase.
This is also a change that would have to be made across all of the backends.
I will definitely take a crack, but chances are I will get hopelessly stuck. I'm a reasonably accomplished python and c# programmer, but I haven't got much c++ experience...
Mmm, I looked at it quickly but it might be slightly out of my depth. I will have a go anyway, but I might need some tutoring. This is basically the first time I try to mess with the internals of a module that is not 'pure-python'...
As @tacaswell suggested, there's sort of two sides to this. One is creating the API and storage to store the new value (hatch width) with the artist. The other is updating all of the backends to obey it. Most of the backends are in Python, but the Agg one will require a little C++. I can help with the Agg stuff, but can't realistically find the time to tackle the whole thing.
@jkokorian Tutoring/mentoring new contributors in one of the roles of project maintainers. We are all very time-bound so the more people working on the code the better 😃
Activity
tacaswell commented on Jan 22, 2015
@jkokorian Want to take a crack at add that feature? This might not be the gentlest introduction to the library but might be fun!
The code for the hatch width for AGG is now in src/_backend_agg.h (as it is templated c++). I think that the way you would have to get the new information in would be to add it to the graphicsContextBase.
This is also a change that would have to be made across all of the backends.
jkokorian commented on Jan 22, 2015
I will definitely take a crack, but chances are I will get hopelessly stuck. I'm a reasonably accomplished python and c# programmer, but I haven't got much c++ experience...
Like you said, it might be fun!
jkokorian commented on Jan 23, 2015
Mmm, I looked at it quickly but it might be slightly out of my depth. I will have a go anyway, but I might need some tutoring. This is basically the first time I try to mess with the internals of a module that is not 'pure-python'...
mdboom commented on Jan 23, 2015
As @tacaswell suggested, there's sort of two sides to this. One is creating the API and storage to store the new value (hatch width) with the artist. The other is updating all of the backends to obey it. Most of the backends are in Python, but the Agg one will require a little C++. I can help with the Agg stuff, but can't realistically find the time to tackle the whole thing.
tacaswell commented on Jan 23, 2015
@jkokorian Tutoring/mentoring new contributors in one of the roles of project maintainers. We are all very time-bound so the more people working on the code the better 😃
QuLogic commented on Nov 5, 2016
I believe this is fixed by #6198.
lzkelley commented on Jul 18, 2017
Am I correct that there's still no way to set hatch-linewidths for an individual plot object?