-
Notifications
You must be signed in to change notification settings - Fork 317
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
Writing to pgfAxis environment from other function than drawAxes() #35
Comments
Just made a hack in the savToFile() function for testing;
Suggestions for improvement are welcome. :) |
I don't understand the issue -- you wanna append something to the options of the current enviroment and it doesn't work? |
I wanted to write some options under
where *bla is written from the drawAxes() function and -new_bla from any other function. I.e. if I want to add the z-limits for a 3D plot, they have to be placed as options in the axis environment, and not as options in the surf environment (\addplot3[surf]) . However, I when in drawSurface() I couldn't find a way to directly access the axis environment instead of the surface which I was plotting; hence the hack I mentioned. But it works as it is now, but as mentioned, not the cleanest solution. Should be easy to fix once I understand how to append the new options directly to the axis environment (env.options in drawAxes()). |
Ah okay. Well, that had worked before but broke at some point such that, for example, stacked bar plots (which need 'ybar stacked' in the containing axes environment) didn't work anymore. |
In drawAxes() this is written:
which makes me believe that I can update the content (m2t.currentHandles.pgfAxis.options) from another nested function before the content is printed to the actual file.
Thus, if I in f.ex drawLine() want to append something, I could write:
But after trying for a while now it's obvious I'm missing out on something; the options are indeed updated in the struct, but not printed to the file.
So the question is; what am I missing here?
The text was updated successfully, but these errors were encountered: