This is a nice tool; I had one of my own but never nearly as extensive as this one. Unfortunately, there seems to be an issue with variable names that are also function names. I couldn't solve it, maybe you could...
If, for example, you write
S = struct('sigma',0.25);
on the command prompt, you have that sigma is 0.25. However, if you wrap this into function test.m (not a script, a function) then you have this oddity:
Name Size Bytes Class Attributes
S 1x1 184 struct
sigma 1x1 8 double
??? Error using ==> sigma at 83
Not enough input arguments.
Error in ==> test at 5
where Matlab tries to call a function called sigma!?
A minor thing though... Under my installation, the private/ghostscript.m function had a minor bug that resulted in the whole function being whipped out and replaced by solely the 'gs' path. Just in case it happens to anyone else, here is a simple patch:
The function is magnificent.
Except that sometimes for me a problem arises when exporting!
In loglog plot, the label ticks are not written correctly, I mean they should be something like 10^(2), but they are 100.
Strange is that this only happens for y-axis and x-axis is fine!
I looked it up a lot in the internet, but could not find the solution. I have not been able to resolve it by changing tickmode to manual or etc.
Any other solution?
20 Oct 2014
Exports figures nicely to a number of vector & bitmap formats.
I encountered a similar issue as described by Emma. However, it works fine for linewidths>0.75 pt, but for smaller linewidths the lines seem to be set to 0.75 pt when exporting, i.e. when exporting lines of 0.5 pt width (or any value<0.75), it will export them as 0.75 pt, when exporting lines with 1 pt width (or any value >0.75 pt) it exports them with the correct width.
The problem does not occur in R2014a.