Hi @JeffYoung,
repository already cloned. I’m fighting now with build dependencies.
Has somebody a hint about “Cannot find wxPython.h” for a passionate OpenSUSE user
wxWidgets 3.0.4 produces
Could NOT find wxWidgets: Found unsuitable version “…”, but required is at
least “3.0.2.0” (found
-L/usr/lib64;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_baseu_xml-3.0;-lwx_gtk2u_stc-3.0)
Call Stack (most recent call first):
But after upgrade it to 3.1.3, another unsolvable issue
have python-wxWidgets-3_0-devel with /usr/include/wx-3.0/wx/wxPython/wxPython.h
but wxWidgets-3_2-devel /usr/include/wx-3.1/…
When an include file is missing, usually the -dev or -devel package needs to be installed. Probably this one or a more recent version:
$ zypper info python-wxWidgets-3_0-devel
Loading repository data...
Reading installed packages...
Information for package python-wxWidgets-3_0-devel:
---------------------------------------------------
Repository : Main Repository
Name : python-wxWidgets-3_0-devel
Version : 3.0.2.0-lp151.3.3
Arch : x86_64
Vendor : openSUSE
Installed Size : 2.6 MiB
Installed : No
Status : not installed
Source package : python-wxWidgets-3_0-3.0.2.0-lp151.3.3.src
Summary : Everything needed for development with wxPython
Description :
wxWidgets is a free C++ library for cross-platform GUI development.
With wxWidgets, you can create applications for different GUIs (GTK+,
Motif, MS Windows, MacOS X, Windows CE, GPE) from the same source code.
This package contains all files needed for developing with Python
bindings for wxGTK.
Do not use wx 3.1.x unless you really know what you are doing. It has many quirks that we are not fully supporting yet, and also makes incompatible changes occasionally (which we are in the process of fixing).
Additionaly, wxPython does not support wx 3.1.x, only 3.0.x.
Update.
This black margin for negative plot aims the visibility of element from “Edge.Cuts” like orientation marks in pictures of initial posting.
The problem is that we advise to paint inverse all elements in all layers. Actually the Edge.Cuts elements are “outline” and have to be just visible, nothing more.
They have to be black on white paper, or inverse to background if we would like to paint some area above “inline” (e.g. save etch and keep copper or vice versa).
Still thinking of minimal invasive solution.
BR
Alex
You started with a function to invert the black / white, apparently for negative film photoresist, which seemed to work perfectly, looking at your first screenshots.
And then you’ve changed it into something that does not invert anything on the board at all and just does something weird with the borders outside of the the PCB, which are not very important anyway.
not quite so.
Look at negative in the first posting in thread. The entire outline is inverted and behavior cannot be changed.
I would like to avoid that. At home conditions (and that what PDF/SVG plotting is for) I cannot span the photoresist foil clear to the PCB boundary. To get acceptable result even with laminating, I have to go over the border for ~5 mm. I’m using negative photoresist foil. The area covered by opaque will be etched away. And main concern is to avoid that. That’s what I’ll use most of the time.
.
The next picture just shows, that somebody willing to etch everything upon, can still do that and even can control how far he can do that.
Example with 5mm (the range is 0-20mm).
By the way it’s also working for positive photoresist. You can force a knockout area here. Example with 3mm.
I would repeat that this has a meaning only for hobbyists, trying to save etch material and occasionally the planet ;-). Developing the board for mass-production you will never bother yourself with such details. In fact it even does not make any sense to create negative plot for you.