Hi Simon,
Shame on me, thank you for catching this. I have just applied your patch
to the master branch.
Regards,
Orson
On 09/16/2016 07:54 AM, Simon Richter wrote:
> ---
> pcbnew/class_board_connected_item.cpp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
>
>
Le 15/09/2016 à 14:55, Oliver Walters a écrit :
> Ok, round two!
>
> 1. I have fixed the issue relating to comma-separated decimals.
>
> 2. Boolean values now use the wxGridCellBoolRenderer which means they always
> display as checkboxes
>
> Here is an example of the boolean values rendering
Hi Cirilo,
IMO the b) is most important for the users that want to use the features
without having knowledge of how the things really work and want something that
"it just works". (special good for sharing without copy many files)
but as Maurice point, the a) inline feature is a more wised way
Hi all,
If ever anyone implement a new form, please have an eye on, and mind on, that
the new form also will need a 3DViewer implementation.
It may be just a need to convert it with segm approximation (if its not already
come as segments from pcbnew board).
Cheers,
Mario Luzeiro
On 9/16/2016 2:13 PM, Michael Steinberg wrote:
> Hello Wayne,
>
>> Yet. I'm sure they are going to have to implement it at some point.
>> You can always write your own swig wrapper something like this:
>> http://stackoverflow.com/questions/27693812/how-to-handle-unique-ptrs-with-swig
>>
> They
* Remove support for building the Bitmap lib standalone,
which has been broken since the switch from svn.
Signed-off-by: Niki Guldbrand
---
bitmaps_png/CMakeLists.txt | 17 -
1 file changed, 17 deletions(-)
diff --git a/bitmaps_png/CMakeLists.txt
Patch committed. Thank you for your contribution to KiCad.
On 9/15/2016 6:54 PM, Niki Guldbrand wrote:
>
> * Remove the obsolete bzr rules file.
>
> Signed-off-by: Niki Guldbrand
> ---
> rules | 27 ---
> 1 file changed, 27 deletions(-)
>
2016-09-15 20:33 GMT+02:00 Wayne Stambaugh :
> On 9/15/2016 1:39 PM, Nick Østergaard wrote:
>> Hi
>>
>> I was going to submit a patch to update the short description for the
>> various folders in the the root of the kicad source repo, but I am a
>> bit confused to what to
On 9/16/2016 1:07 PM, Bernhard Stegmaier wrote:
> Question for me is if we shouldn’t just fork wxWidgets on github and
> maintain a separate kicad branch there (I started this already for myself).
> Would get rid of all the nasty patching and everybody willing to build
> on his own could use this
Patch committed. Thanks Nick.
On 9/16/2016 4:12 PM, Nick Østergaard wrote:
> 2016-09-15 20:33 GMT+02:00 Wayne Stambaugh :
>> On 9/15/2016 1:39 PM, Nick Østergaard wrote:
>>> Hi
>>>
>>> I was going to submit a patch to update the short description for the
>>> various folders
If no one else objects, I'll commit the patch.
On 9/16/2016 11:14 AM, Adam Wolf wrote:
> Sorry, I used the wrong email address before and my email didn't go through.
>
> I think this is correct, and I would like all the patches to be in the
> same format. Nick and Simon and I are working on
After having messed up my first emailed patch due to missing this
email, would it not be better to add a .gitconfig to the project tree
which includes this helper script by default?
On Fri, Aug 12, 2016 at 9:36 PM, Maciej Sumiński
wrote:
> On 08/11/2016 08:28 PM, Wayne
OK, with the feedback from Maurice and Mario I have retained the Inline{}
option but
changed the behavior:
+ If "Copy 3D model files" is activated then Inline{} is used, otherwise a
monolithic
file is written. This removes the previous behavior that absolute paths can
be used in
Inline{}; the
Fixes: lp:1559103
---
patches/wxwidgets-3.0.2_macosx_unicode_pasteboard.patch | 16
1 file changed, 16 insertions(+)
create mode 100644 patches/wxwidgets-3.0.2_macosx_unicode_pasteboard.patch
diff --git a/patches/wxwidgets-3.0.2_macosx_unicode_pasteboard.patch
gitconfig is not loaded by git for security unless you explicitly tell it to.
i.e. a user still has to run
git config --local include.path ../.gitconfig
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
Awesome! This has been driving some people crazy on the bug tracker.
On Fri, Sep 16, 2016 at 6:25 PM, Simon Wells wrote:
>
> Fixes: lp:1559103
> ---
> patches/wxwidgets-3.0.2_macosx_unicode_pasteboard.patch | 16
>
> 1 file changed, 16 insertions(+)
>
In addition to that, the error in the approximation can be made as small as
we wish and it's not difficult to achieve <1 micron error if you really want
Gerber outputs to be that precise. This is "approximation" in the
mathematical
sense and not in the general use of the language, so we control
Your patch has been pushed to master. Thank you for your contribution
to KiCad.
Cheers,
Wayne
On 9/13/2016 4:29 PM, Niki Guldbrand wrote:
>
> * Using CMAKE_INSTALL_PREFIX in KICAD_* install paths is redundant,
> because they are allready relative to CMAKE_INSTALL_PREFIX when no
> absolute
What was mentiomed was to approximate for example beziers with arcs. That
would still be accurate when exported to gerbers, because one could use
arcs which are supported in gerbers IIRC.
Den 16/09/2016 15.34 skrev "Wayne Stambaugh" :
> I would like to see arc support in
I would like to see arc support in copper layers as well but we need to
approach this carefully. One thing KiCad has been pretty good at is not
producing broken gerber files. A lot of code would have to be written
to support this fully. When I here words like "approximate", it makes
me nervous.
Sorry, I used the wrong email address before and my email didn't go through.
I think this is correct, and I would like all the patches to be in the same
format. Nick and Simon and I are working on revamping the OS X packaging
scripts so that we get signing and a bunch of improvements from the
Hello all,
when activating python bindings on my msvc build with a few refactor
commits applied, it came to my attention that SWIG simply does not
support std::unique_ptr.
With this message I want to ask what is the common view whether it is
okay to have SWIG thumbscrew the project's source
Would one of our osx devs please comment on this? I don't know if this
patch makes sense. I'll fix the path issue in compiling.md.
@Collin, please format your patches using git format-patch. It makes
life easier for devs to commit your patches.
On 9/15/2016 6:21 AM, Collin Anderson wrote:
>
2016-09-16 18:08 GMT+02:00 Tomasz Wlostowski :
> On 16.09.2016 18:01, Michael Steinberg wrote:
>> Hello all,
>>
>> when activating python bindings on my msvc build with a few refactor
>> commits applied, it came to my attention that SWIG simply does not
>> support
On 9/16/2016 12:01 PM, Michael Steinberg wrote:
> Hello all,
>
> when activating python bindings on my msvc build with a few refactor
> commits applied, it came to my attention that SWIG simply does not
> support std::unique_ptr.
Yet. I'm sure they are going to have to implement it at some
Hello Wayne,
Yet. I'm sure they are going to have to implement it at some point.
You can always write your own swig wrapper something like this:
http://stackoverflow.com/questions/27693812/how-to-handle-unique-ptrs-with-swig
They had 5+ years to add support, they didn't. So I wouldn't count
On Fri, Sep 16, 2016 at 08:13:13PM +0200, Michael Steinberg wrote:
> Hello Wayne,
>
> >Yet. I'm sure they are going to have to implement it at some point.
> >You can always write your own swig wrapper something like this:
>
27 matches
Mail list logo