Thank you Rene!
What else needs to be done so we can get the packages built?
On 8/23/2017 6:51 PM, Rene Pöschl wrote:
> On 22/08/17 14:53, Wayne Stambaugh wrote:
>> Sorry about the delay but I was dealing with a family emergency all last
>> week. Now that I'm getting caught up I really need to
On 22/08/17 14:53, Wayne Stambaugh wrote:
Sorry about the delay but I was dealing with a family emergency all last
week. Now that I'm getting caught up I really need to get stable
version 4.0.7 released. Are there any outstanding issue remaining
before I make the release announcement? I'm
To clarify, I agree fully that critical functionality should be core. Extra
functionality could be available via an exposed scripting interface, which
I suppose is already available via the existing python framework.
On 23 Aug 2017 14:55, "Wayne Stambaugh" wrote:
> On
Hi Wayne,
Wayne Stambaugh writes:
> Rather than add a wxComboBox to the WX_UNIT_BINDER object, wouldn't be
> be cleaner to change wxTextCtrl* to wxTextEntry* which wxComboBox and
> wxTextCtrl (along with several others) are derived from?
Yes, of course, I will change
I didn't write that patch. It was Blair Bonnett.
I just took a look at the wxformbuilder github...its still using their
luamake abomination, ugh.
On Mon, Aug 21, 2017 at 3:12 PM, jp charras wrote:
> Le 15/09/2015 à 21:07, Mark Roszko a écrit :
>>
Better formatting:
How do you get PCB_EDIT_FRAME functions exposed to python?
I've been looking around the source code tosee how to expose them.
Specifically, PCB_EDIT_FRAME::syncLayerVisibilities, and other PCB_EDIT_FRAME
functions.
It looks like to me the definitions are in
pcbnew/pcbframe.cpp
How do you get PCB_EDIT_FRAME functions exposed to python?
I've been looking around the source code tosee how to expose them.
Specifically, PCB_EDIT_FRAME::syncLayerVisibilities, and other PCB_EDIT_FRAME
functions.
It looks like to me the definitions are inpcbnew/pcbframe.cppand the
To assist compilation of a set of rules, we might be able to use this link to
my effortson loading/saving an Eagle DRU file. I've listed all the settings
saved by the Eagledesign rule check dialog, and annotated the output file. I
list the equivalent DRU keywordwith its associated dialog entry
On 8/23/2017 8:49 AM, Tomasz Wlostowski wrote:
> On 23.08.2017 14:05, Wayne Stambaugh wrote:
>> This is the missing piece of the puzzle. We would need to create a
>> constraints manager to handle a list of constraints which could either
>> be an internally defined constraint or a custom python
On 23.08.2017 14:05, Wayne Stambaugh wrote:
> This is the missing piece of the puzzle. We would need to create a
> constraints manager to handle a list of constraints which could either
> be an internally defined constraint or a custom python constraint.
> Without a well defined interface, this
On 8/23/2017 7:32 AM, Oliver Walters wrote:
> Something I have been considering for a while - instead of hard coding
> complex DRC rules into base code, what if we developed a DRC API and
> write the rules in Python?
I can see using python for complex or custom constraints but not for
general
I have experience in python DRCs and have a background in ASIC layout software
and Design Rule Checks as well as a healthy experience in GIS and layer
manipulation..
I have started KiPadCheck exactly to fill in some missing (IMHO) DRC checks. It
might be a good as a base for further
On 8/22/2017 5:33 PM, Thomas Langås wrote:
> On Tue, Aug 22, 2017 at 9:36 PM, Wayne Stambaugh wrote:
>> I'm not opposed to this change. However, there are two schools of
>> thought when it comes to board layout: strict layout constraints and no
>> layout constraints. I
Something I have been considering for a while - instead of hard coding
complex DRC rules into base code, what if we developed a DRC API and write
the rules in Python?
Each rule could be a separate python file (similar to how footprint wizards
are done). Users could enable/disable each DRC and
If you're looking for good DFM manuals, check out protoexpress, otherwise
known as Sierra Circuits.
They're a professional board house in the USA with simple to complex board
design support including high speed interfaces, uvias, etc.
On Tue, Aug 22, 2017 at 2:33 PM, Thomas Langås
15 matches
Mail list logo