matplotlib-users Mailing List for matplotlib

The behavior of the '.' marker seems anomalous, very different between 
gtkAgg and postscript backends, and not very useful:
1) With both backends, only the markeredgewidth property, not the 
markersize property has an effect on the size. More consistent with 
Matlab, and I suspect with what other users would expect, would be to 
have the markersize property control the size, as it does for all the 
other markers.
2) With Agg, trying to use markeredgewidth to make the size larger 
produces odd symbols.
3) With postscript, markeredgewidth=20, for example, does make a large 
circular dot.
What I would prefer for all backends would be for '.' size to be 
controlled by markersize; the differences between 'o' and '.', as in 
Matlab, would be that the actual size of the dot would be a fraction of 
what is given in markersize (so that with a single markersize, there is 
a clear distinction between a dot and a filled circle), and the dot 
would have no edge.
I suppose an alternative viewpoint is that a dot really should be a 
single pixel, so one shouldn't adjust its size; but this goes against 
the basic idea of having a plotting library in which the result depends 
as little as possible on the output hardware.
Some backend dependence might be needed: for bitmapped output, one might 
specify that the dot marker should always include one full pixel, so 
that dots don't fade away in thumbnails, for example.
Comments?
Eric

Hi all,
I get errors when building matplotlib with VC++ 6.00 see below.
I read the bit about being masochistic in doing this, however,
I am endeavouring to integrate Matplotlib into a wxWidgets
App and I need debug mode to enable me to get it to work.
So far I have used VC++ 6.00 to compile wxWidgets, wxPython,
Numarray and Numeric in debug mode and it is just Matplotlib
to go now.
Failure details
System is Win XP pro SP1,
Python-2.4.1.
Matplotlib is either matplotlib-0.83.2 or checkout from cvs.
Command line is python setup.py build --debug
running build_ext
building 'matplotlib._agg' extension
creating build\temp.win32-2.4
creating build\temp.win32-2.4\Debug
creating build\temp.win32-2.4\Debug\src
creating build\temp.win32-2.4\Debug\agg23
creating build\temp.win32-2.4\Debug\agg23\src
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo /Od 
/MDd ......
agg.cxx
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo /Od 
/MDd ......
agg_trans_affine.cpp
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo /Od 
/MDd ......
agg_path_storage.cpp
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo /Od 
/MDd ......
agg_bezier_arc.cpp
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo /Od 
/MDd ......
agg_vcgen_dash.cpp
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo /Od 
/MDd ......
agg_vcgen_stroke.cpp
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo /Od 
/MDd ......
agg_rasterizer_scanline_aa.cpp
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo /Od 
/MDd ......
agg_curves.cpp
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\link.exe
 /DLL /nologo /INCREMENTAL:no /pdb:None /DEBUG
 /LIBPATH:e:\Python241\libs
 /LIBPATH:e:\Python241\PCBuild stdc++.lib m.lib
 /EXPORT:init_agg build\temp.win32-2.4\Debug\src/agg.obj
 build\temp.win32-2.4\Debug\agg23/src/agg_trans_affine.obj
 build\temp.win32-2.4\Debug\agg23/src/agg_path_storage.obj
 build\temp.win32-2.4\Debug\agg23/src/agg_bezier_arc.obj
 build\temp.win32-2.4\Debug\agg23/src/agg_vcgen_dash.obj
 build\temp.win32-2.4\Debug\agg23/src/agg_vcgen_stroke.obj
 build\temp.win32-2.4\Debug\agg23/src/agg_rasterizer_scanline_aa.obj
 build\temp.win32-2.4\Debug\agg23/src/agg_curves.obj
 /OUT:build\lib.win32-2.4\matplotlib\_agg_d.pyd
 /IMPLIB:build\temp.win32-2.4\Debug\src\_agg_d.lib
LINK : fatal error LNK1181: cannot open input file "stdc++.lib"
note: cl.exe line above are truncated by me.
I can get around this link error by commenting out all references
to stdc++ in setup_ext.py ie #module.libraries.extend(['stdc++', 'm'])
Am I correct in doing this?
I then get the following error compiling _na_transforms.cpp
running build_ext
building 'matplotlib._na_transforms' extension
E:\ProgramFiles\Microsoft Visual Studio\VC98\BIN\cl.exe
 /c /nologo /Od /MDd /W3 /GX /Z7 /D_DEBUG
 -Isrc -I. -I -Ie:\Python241\include -Ie:\Python241\PC
 /TpE:\Python241\Lib\site-packages\matplotlib-cvs\src\_na_transforms.cpp
 /Fobuild\temp.win32-2.4\Debug\src/_na_transforms.obj -DNUMARRAY=1
_na_transforms.cpp
.\CXX/Objects.hxx(9) : fatal error C1083: Cannot open include file: 
'Python.h': No such file or directory
This error seems to be due to the part of the cl command line
containing "-Isrc -I. -I -Ie:\Python241\include -Ie:\Python241\PC"
and in particular the bit "-I"
Changing the line
"include_dirs = ['src', '.']+numarray_inc_dirs,"
to
"include_dirs = ['e:\Python241\include', 'src', '.']+numarray_inc_dirs,"
It seems that the -I not having a directory path is a problem.
I then get similar errors later building the other modules.
I would appreciate it if somebody more knowledgeable in Disutils
could point me in the right direction towards finding this problem.
Also what does 'win32_static' mean?
Thanks in anticipation,
Noel Diviney
-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/