Not asking for this to be committed, I know we're in feature freeze, but
hopefully I can slip this in after the release. Try it out - this patch
enables eeschema to automatically place and rotate fields around a
component. It's quite a time-saver when trying to put a schematic
together, since t
On Tue, Jun 16, 2015 at 8:33 AM, Tomasz Wlostowski <
tomasz.wlostow...@cern.ch> wrote:
> On 14.06.2015 13:35, jp charras wrote:
> > Le 14/06/2015 12:01, Tomasz Wlostowski a écrit :
> >> On 14.06.2015 02:35, Cirilo Bernardo wrote:
> >>> 7. STEP: (future plans) the plugin will only provide an Export
On 14.06.2015 13:35, jp charras wrote:
> Le 14/06/2015 12:01, Tomasz Wlostowski a écrit :
>> On 14.06.2015 02:35, Cirilo Bernardo wrote:
>>> 7. STEP: (future plans) the plugin will only provide an Export
>>
>> I'd also like to add STEP visualization in the near future (post-stable ofc)
>>
>> Tom
>>
Hi,
> On 15 Jun 2015, at 23:41, Nick Østergaard wrote:
>
> 2015-06-15 23:38 GMT+02:00 Nick Østergaard :
>> 2015-06-15 23:04 GMT+02:00 Bernhard Stegmaier :
>>> From other build systems I know something like
>>> ---.patch
>>>
>>> So, something like
>>> wxWidgets-3.0.2-001-wxDataViewCtrl.patch
>
2015-06-15 23:38 GMT+02:00 Nick Østergaard :
> 2015-06-15 23:04 GMT+02:00 Bernhard Stegmaier :
>> From other build systems I know something like
>> ---.patch
>>
>> So, something like
>> wxWidgets-3.0.2-001-wxDataViewCtrl.patch
>>
>> Do we want to add more patches for open bugs in wxWidgets goin
2015-06-15 23:04 GMT+02:00 Bernhard Stegmaier :
> From other build systems I know something like
> ---.patch
>
> So, something like
> wxWidgets-3.0.2-001-wxDataViewCtrl.patch
>
> Do we want to add more patches for open bugs in wxWidgets going forward to
> the stable release?
> At least for OS X
From other build systems I know something like
---.patch
So, something like
wxWidgets-3.0.2-001-wxDataViewCtrl.patch
Do we want to add more patches for open bugs in wxWidgets going forward to the
stable release?
At least for OS X there is one open issue in 3.0.2 that you cannot open other
f
I agree they will be short lived--on the other hand it looks like many of
the bugs between us and stable reside at least partially in wxwidgets.
I am fine pulling them out of kicad completely and pointing folks at the
kicad depbuilder project, whatever form that may take.
Adam Wolf
On Jun 15, 201
I'm OK with that idea. You could either come up with a naming scheme or
segregate them into subfolders by platfrom and/or the dependency that
they get applied to. Please keep in mind that it will probably be short
lived. I was originally planning on moving the patches into the cmake
dependency b
As far as I can see they are
wxwidgets-_macosx_.patch except for onw which
as a big W as the second w.
2015-06-15 22:45 GMT+02:00 Adam Wolf :
> I'd gladly do *.patch, but not every patch in the patches directory is for
> wx, and probably not all of them are for OSX...
>
> On Jun 15, 2015 3:43 PM,
I'd gladly do *.patch, but not every patch in the patches directory is for
wx, and probably not all of them are for OSX...
On Jun 15, 2015 3:43 PM, "Nick Østergaard" wrote:
> *.patch ?
>
> 2015-06-15 22:35 GMT+02:00 Adam Wolf :
> > I will make this update in the builder scripts before tonight's b
*.patch ?
2015-06-15 22:35 GMT+02:00 Adam Wolf :
> I will make this update in the builder scripts before tonight's builds.
>
> I wonder if we can set up a filename convention for wx patches so they can
> be automatically applied. Anyone opposed to that idea? I get that we're
> going to be mainta
I will make this update in the builder scripts before tonight's builds.
I wonder if we can set up a filename convention for wx patches so they can
be automatically applied. Anyone opposed to that idea? I get that we're
going to be maintaining this out-of-tree for after the stable release, but
we
Patch committed in product branch r5755. Thanks Bernhard.
I guess our OSX package builder script(s) will need to apply this patch
to wxWidgets for our OSX bundles.
On 6/14/2015 3:41 PM, Bernhard Stegmaier wrote:
> Hi,
>
> FYI… I guess this is only OS X related.
>
> Yesterday I wanted to use th
Hey Martin,
Your patch does not seem to work on windows. When I try to open a new
project from kicad, the file open dialog still points to the kicad
executable path. In my case it's c:\mingw\bin. The Eeschema change
seems to work as expected. Is it possible the path is getting changed
in kicad
I like it too.
Jean-Paul,
AC9GH
> On Jun 15, 2015, at 9:54 AM, Adam Wolf wrote:
>
> I like this change.
>
> Adam Wolf
>
> On Mon, Jun 15, 2015 at 8:29 AM, Wayne Stambaugh wrote:
> Does anyone else have any comments on this change. It makes sense to me
> that on a new or empty project that t
I agree strongly with Nick. A DXF import for the PCB outline is a must have,
not just a nice to have.
During my professional life, I always pushed the PCB design center to import
the PCB outline from the mechanical design.
My $0.02,
Jean-Paul
AC9GH
> On Jun 15, 2015, at 3:54 AM, Nick Østergaard
Can we Please, Please, Please stop using two different kinds of builds?
I can't even begin to describe how tiresome and infuriating it is to try
to help someone with a crash and find out that the backtraces are
completely useless. Especially with Heisenbugs that stop happening when
you get the
Hey Bernhard,
I'll tag it as 3.0.2 since that's what OSX package builders should be
using. It may apply further back but I'll leave that as an exercise for
the developer.
Cheers,
Wayne
On 6/15/2015 1:46 PM, Bernhard Stegmaier wrote:
> Hi Wayne,
>
> I did it against a ~4 weeks old head of 3.0
Hi Wayne,
I did it against a ~4 weeks old head of 3.0 branch (so something like
pre-3.0.3), there are no changes since 3.0.2 in that areas.
I did a quick check on the main branch and the bad pieces of code are just the
same, so it should apply as well there.
Regards
Bernhard
> On 15 Jun 2015
Yep, that’s exactly the crash that I debugged.
It is a simple "null-pointer not checked” issue… which in this case is present
at many places in the OS X wxWidgets code.
Regards,
Bernhard
> On 15 Jun 2015, at 18:48, Andy Peters wrote:
>
>>
>> On Jun 14, 2015, at 12:41 PM, Bernhard Stegmaier
On 6/15/2015 12:29 PM, jp charras wrote:
> Le 15/06/2015 16:27, Maciej Sumiński a écrit :
>> On 03/30/2015 12:00 AM, Tomasz Wlostowski wrote:
>>> Hi Wayne,
>>>
>>> Some time ago I modified a bit the REPORTER class: added message
>>> severity levels & a wxHtmlView widget to filter/display them
>>>
Your patch has been committed to the product branch r5754. Thank you
for you contribution to KiCad,
Cheers,
Wayne
On 6/15/2015 12:34 PM, Martin d'Allens wrote:
> Sorry about the braces, here is a correct version.
>
> I don't think this is platform specific, but it might. Or it could
> depend
> On Jun 14, 2015, at 12:41 PM, Bernhard Stegmaier
> wrote:
>
> Hi,
>
> FYI… I guess this is only OS X related.
>
> Yesterday I wanted to use the Pin Table for the first time and it always
> crashes the Library Editor.
> After some debugging I am pretty sure that this is a bug in the OS X
>
On 6/15/2015 12:34 PM, Martin d'Allens wrote:
> Sorry about the braces, here is a correct version.
>
> I don't think this is platform specific, but it might. Or it could
> depend on wxWidgets's version.
> The behaviour I am addressing is not related to selecting an item in the
> list.
> When you o
Sorry about the braces, here is a correct version.
I don't think this is platform specific, but it might. Or it could depend
on wxWidgets's version.
The behaviour I am addressing is not related to selecting an item in the
list.
When you open the "Search" dialog, SetSelection( 0 ) fills the combobo
On Mon, Jun 15, 2015 at 06:29:29PM +0200, jp charras wrote:
> [[snip]]
>
> keywords like UNDEFINED, INFO, WARNING , ERROR are widely used, the
> risk of collision is high.
> Usually I use something like:
> RPT_UNDEFINED, RPT_INFO , RPT_WARNING , RPT_ERROR
> to avoid this risk.
What about namespac
Le 15/06/2015 16:27, Maciej Sumiński a écrit :
> On 03/30/2015 12:00 AM, Tomasz Wlostowski wrote:
>> Hi Wayne,
>>
>> Some time ago I modified a bit the REPORTER class: added message
>> severity levels & a wxHtmlView widget to filter/display them
>> (see attached drawing showing the new report pan
Bernhard,
Which version of wxWidgets is this patch against?
Thanks,
Wayne
On 6/14/2015 3:41 PM, Bernhard Stegmaier wrote:
> Hi,
>
> FYI… I guess this is only OS X related.
>
> Yesterday I wanted to use the Pin Table for the first time and it always
> crashes the Library Editor.
> After some d
Another improvement to the pin/entry targets: if a bus entry is drawn between
two WIRES (not a wire and a bus, or two buses), it looks like it's connecting
the wires together, but doesn't actually represent a connection. This patch
makes it display as dangling in that case, to make it clear to the
Patch committed in product branch r5752.
Thanks,
Wayne
On 6/14/2015 3:27 PM, Chris Pavlina wrote:
> This patch displays pin and bus entry targets while they are being
> moved, as they are also dangling then (even though the dangling status
> has not been updated). This seems to make the interf
Hi,
Over the past weekend I saw a forum question/discussion re. the DXF
import for complex board shapes (particularly elliptical shapes). A
quick test with a elliptical shape indicated that it did not work properly.
I thought it would be fun to dig into that and found that typically
these sh
I like this change.
Adam Wolf
On Mon, Jun 15, 2015 at 8:29 AM, Wayne Stambaugh
wrote:
> Does anyone else have any comments on this change. It makes sense to me
> that on a new or empty project that the project path gets set to the
> user's home path. I see in the patch that it is fixed in kic
Does anyone else have any comments on this change. It makes sense to me
that on a new or empty project that the project path gets set to the
user's home path. I see in the patch that it is fixed in kicad and
eeschema. It might be a good idea to see if this behavior exists in
pcbnew as well and f
Your patch doesn't seem to make any difference on windows builds. With
or without your patch, the first item in the list is selected. Does
this fix a platform specific problem in your case.
Also, please read the KiCad coding policy and fix your code formatting.
http://ci.kicad-pcb.org/job/kicad
I am not quite sure where you are going with this mail, but I agree
that DXF import is a good way to get complex board shapes in pcbnew.
The drawing tools are sort of limited at the time of writing.
But often when you need a complex board shape it is because you are
constrained by the end product
36 matches
Mail list logo
