This function is unused, and looks similar to the tree builder above, so it
might likely be left over from a refactoring effort.
---
.../netlist_exporters/netlist_exporter_generic.cpp | 73 --
.../netlist_exporters/netlist_exporter_generic.h | 7 ---
2 files changed, 80
I split this from the net-ties, etc RFC because its drifting off topic
from that discussion.
I am not sure I understand the rationale to "It should also
be limited to passing information to external tools such as simulators
and scripts such as Tom's proposal"?
Both the Footprint and the
I'm 300% in favor of this proposal, an it makes sense to store the
dimensions in the key_value pairs. From a user's perspective, they can
grab a premade symbol with default values populated in those fields,
place in the schematic and edit if necessary. for selecting the
"autogenerated flag" what
On 04.05.2016 16:48, Wayne Stambaugh wrote:
> How are you saving this auto generate flag and width/length parameters
> in the schematic? If you are using component fields or text that's
> fine. However, please keep in mind that using component fields and text
> is for passing information to
I had originally thought that was the idea with the 4.x series, but I might be
wrong.
On Wed, May 04, 2016 at 11:10:46AM -0600, Duane Johnson wrote:
> Might it be worth making a specific (intermediate) release whose purpose is
> to make it the last support for "legacy" canvas?
>
> On Wed, May 4,
Might it be worth making a specific (intermediate) release whose purpose is
to make it the last support for "legacy" canvas?
On Wed, May 4, 2016 at 9:19 AM, Chris Pavlina
wrote:
> While I understand your point, and I think I agree with it (though I'm
> almost
> on the
An alternative interface could be to optionally accept % as a unit in fields
for values with a clear relationship to another value, as the fields already do
accept units like in and mm. I kind of like the idea, but I wonder how
intuitive that would be - it works fine if you know it's there, but
While I understand your point, and I think I agree with it (though I'm almost
on the fence), I wonder if I should explain - I think the argument for removing
legacy sooner rather than later is that by removing the crutch of "eh, we can
just use legacy for that for now", we will encourage
Removing the legacy canvas cannot be done until there is an acceptable
solution for users who do not have usable opengl on their systems. The
Cairo canvas is not usable even on the fastest system I've have access
to. Until either Cairo gets a significant speed boost, opengl becomes
usable on all
The use of fields for arbitrary data is indeed powerful. It should also
be limited to passing information to external tools such as simulators
and scripts such as Tom's proposal. Anything that is supported as a
feature in KiCad should be part of the schematic file format and fully
supported by
How are you saving this auto generate flag and width/length parameters
in the schematic? If you are using component fields or text that's
fine. However, please keep in mind that using component fields and text
is for passing information to third party tools that are not part of
kicad. If we are
On 5/4/2016 5:20 AM, Maciej Sumiński wrote:
> On 05/03/2016 04:48 PM, Wayne Stambaugh wrote:
> [snip]
>> Not quite yet. See attached screen shot on latest msys2/mingw32. The
>> Cairo version is 1.15.2. I suppose it could be the graphics drivers on
>> my work laptop (it's one of the Intel HD
Le 04/05/2016 à 12:23, Maciej Sumiński a écrit :
> On 05/04/2016 11:45 AM, jp charras wrote:
>> Le 04/05/2016 à 11:20, Maciej Sumiński a écrit :
>>> On 05/03/2016 04:48 PM, Wayne Stambaugh wrote:
>>> [snip]
Not quite yet. See attached screen shot on latest msys2/mingw32. The
Cairo
2016-05-04 13:56 egunean, jp charras-(e)k idatzi du:
Le 04/05/2016 à 13:29, i...@elektroquark.com a écrit :
2016-05-04 13:03 egunean, jp charras-(e)k idatzi du:
Le 04/05/2016 à 12:45, i...@elektroquark.com a écrit :
Hello:
In the Pad Properties window, Round Rectangle properties, there is
Le 04/05/2016 à 13:29, i...@elektroquark.com a écrit :
> 2016-05-04 13:03 egunean, jp charras-(e)k idatzi du:
>> Le 04/05/2016 à 12:45, i...@elektroquark.com a écrit :
>>> Hello:
>>>
>>> In the Pad Properties window, Round Rectangle properties, there is the
>>> "Corner size" option. It
>>> shows
2016-05-04 13:03 egunean, jp charras-(e)k idatzi du:
Le 04/05/2016 à 12:45, i...@elektroquark.com a écrit :
Hello:
In the Pad Properties window, Round Rectangle properties, there is the
"Corner size" option. It
shows the calculated "Corner radius" as information.
Using IPC rules as
Le 04/05/2016 à 12:45, i...@elektroquark.com a écrit :
> Hello:
>
> In the Pad Properties window, Round Rectangle properties, there is the
> "Corner size" option. It
> shows the calculated "Corner radius" as information.
>
> Using IPC rules as guidelines, the maximum corner radius must be 25%
Hello:
In the Pad Properties window, Round Rectangle properties, there is the
"Corner size" option. It shows the calculated "Corner radius" as
information.
Using IPC rules as guidelines, the maximum corner radius must be 25% of
the pad width, with a maximum of 0.25 mm. If the pad is big
On 05/04/2016 11:45 AM, jp charras wrote:
> Le 04/05/2016 à 11:20, Maciej Sumiński a écrit :
>> On 05/03/2016 04:48 PM, Wayne Stambaugh wrote:
>> [snip]
>>> Not quite yet. See attached screen shot on latest msys2/mingw32. The
>>> Cairo version is 1.15.2. I suppose it could be the graphics
Le 04/05/2016 à 11:20, Maciej Sumiński a écrit :
> On 05/03/2016 04:48 PM, Wayne Stambaugh wrote:
> [snip]
>> Not quite yet. See attached screen shot on latest msys2/mingw32. The
>> Cairo version is 1.15.2. I suppose it could be the graphics drivers on
>> my work laptop (it's one of the Intel
On 05/03/2016 04:48 PM, Wayne Stambaugh wrote:
[snip]
> Not quite yet. See attached screen shot on latest msys2/mingw32. The
> Cairo version is 1.15.2. I suppose it could be the graphics drivers on
> my work laptop (it's one of the Intel HD graphics chips). I'll test it
> on my home system
On 05/04/2016 10:09 AM, Mário Luzeiro wrote:
> Hi Orson,
>
> I understand, but my question was, since that check is inside the
> "BeginUpdate" I am supposing that you will do in any case every time that
> redraw update: i.e in this case you will call GL functions and in the worst
> case when
Apparently wxLogInfo() has changed its behavior and instead of writing
to console, now it shows a window. I have just removed the related code,
because if the required version is not supported, the user will get an
appropriate error message anyway (revision 6771).
Regards,
Orson
On 05/03/2016
Hi Orson,
I understand, but my question was, since that check is inside the "BeginUpdate"
I am supposing that you will do in any case every time that redraw update: i.e
in this case you will call GL functions and in the worst case when the windows
is not displayed and you have no context.
For
Hi Mario,
wxWidgets will trigger an assert in Linux if you try to set OpenGL
context when the parent window is not yet visible. It may happen only
when a window is created upon pcbnew launch, but anyway it is enough to
require such condition there. It is also necessary to set the right
context if
25 matches
Mail list logo