I just finished testing it on windows 7. I don't know if it's better or
worse just different. I'm don't have a strong opinion one way or
another but I would still like to hear from some osx devs to get their
input.
On 12/15/2015 9:33 AM, Chris Pavlina wrote:
> If it counts for anything, I vote
Hi Maurice,
That worked for me on OSX 10.9.5 now with native dialog. Thanks!
Jose
On Tue, Dec 15, 2015 at 10:56 AM easyw wrote:
> Hi Jose,
>
> here is the solution for OSX:
>
> 1) add
> import PySide
>just before (line 48 of StepUp tools 1.3.2.8)
> from PySide import
On 15.12.2015 16:52, Wayne Stambaugh wrote:
> Sorry I didn't respond to this sooner but I've been busy. I'm not
> thrilled with this idea. I know it solves the immediate problem but it
> is an incomplete solution.
Hi Wayne,
I surely agree that changing just the net propagation algorithm is not
Thank you for your positive feedback!
I'm going to update the repo :)
Maurice
On 15/12/2015 18.57, Jose A. Saumell wrote:
Hi Maurice,
That worked for me on OSX 10.9.5 now with native dialog. Thanks!
Jose
On Tue, Dec 15, 2015 at 10:56 AM easyw >
I have tested it on OSX with before and after here
http://s14.postimg.org/gf0kty89t/Untitled_1.png
I would prefer to see the top toolbar no longer based on the AUI as i think
it is unnecessary for that particular toolbar as it is not really one that
needs to be docked and undocked.
It this was
Sorry I didn't respond to this sooner but I've been busy. I'm not
thrilled with this idea. I know it solves the immediate problem but it
is an incomplete solution. I would rather we do a complete free via
implementation and not introduce a stop gap measure into Pcbnew. We've
discussed the idea
Le 15/12/2015 18:44, Tomasz Wlostowski a écrit :
> On 15.12.2015 16:52, Wayne Stambaugh wrote:
>> Sorry I didn't respond to this sooner but I've been busy. I'm not
>> thrilled with this idea. I know it solves the immediate problem but it
>> is an incomplete solution.
>
> Hi Wayne,
>
> I surely
Hi,
Here, the new version of the patch without internationalization.
Regards,
Fabien M
>From ae21504d94ade99f5e6fe40930de8765cb54623d Mon Sep 17 00:00:00 2001
From: Fabien Marteau
Date: Tue, 15 Dec 2015 09:55:00 +0100
Subject: [PATCH] Some spelling fixies in
Hi,
Yes I do. But its a bit beyond the scope of this enhancement. However
with this base enhancement in place, doing that should be easier.
For me, one of the biggest problems with the python scripting in KiCad,
isn't that its not powerful enough, its that its largely undocumented.
My
Hi Steven,
do you think it would be useful/possible to add a way to launch a macro
like in FreeCAD, choosing from a list?
https://bugs.launchpad.net/kicad/+bug/1526064
"Ability to assign shortcuts to run a specific script or adding toolbar
buttons would be great!"
thank you for your
I attach an enhanced patch to the python shell.
This one is a bigger change than the previous patch. But it moves the
code to the point where the whole shell is contained as an external
python file, which makes it a lot easier to develop and enhance.
Explanation of the changes:
- I created
Hi,
I've seen yesterday that the information about Kicad on Wikipedia was
quite outdated (The EDA comparison page). I've updated the 4.0.0 release
information but there could be space for some improvement. As I don't
count myself as a KiCad expert, maybe you guys can update some
information
Thanks for the commit JP, it was also on my todo list for a long time!
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help :
#6377 changed a bit in the vicinity of this patch, so here's an updated one to
preempt any merge conflicts.
On Sun, Dec 13, 2015 at 12:53:53PM -0500, Chris Pavlina wrote:
> Okay, here's a patch to make the autoplacement grid for fields flexible,
> so fields are positioned sanely when they have
On 15.12.2015 19:09, jp charras wrote:
> Le 15/12/2015 18:44, Tomasz Wlostowski a écrit :
>> On 15.12.2015 16:52, Wayne Stambaugh wrote:
>>> Sorry I didn't respond to this sooner but I've been busy. I'm not
>>> thrilled with this idea. I know it solves the immediate problem but it
>>> is an
http://s14.postimg.org/rnvw70sr5/Screen_Shot_2015_12_16_at_08_02_19.png
Here is the main toolbar not as AUI on osx, as can be seen this uses the
native OSX toolbar so fits in better with other applications, The gradients
mainly seem to come from the AUI toolkit.
On Wed, Dec 16, 2015 at 6:08 AM,
Would have been nice, though, if the couple "miscellaneous" changes in
that commit were done in _separate_ commits and _described_ rather than
being silent. Would have been less of a WTF for me when something
supposedly only touching pcbnew failed to merge in a branch only
touching eeschema,
Hi Wayne,
thank you very much for your efforts. I'm guessing that this is not an easy
topic and takes thus more time.
Hopefully a good solution can be found this way.
Maybe it makes then sense to announce this change on the KiCad homepage, I
could also imagine to add a definition of the
Hi Wayne & Jean-Pierre,
please consider also my implementation, I've announced this already (April/August 2015) on the mailing list:
https://lists.launchpad.net/kicad-developers/msg19584.html
Now is the stable release finished and we can talk about this.
I'm using there pads for
On 12/15/2015 4:48 PM, Jon Neal wrote:
> It looks nicer in some ways, but I don't think I completely like it.
>
> Two comments I have:
> 1. A little bit of whitespace in between each color block would make it
> look even nicer I think.
I don't like the square run on color buttons either. I
I would prefer to see all the applications get a native toolbar for their
main toolbar, I have only hacked it on in the kicad manager currently to
see whether it was popular at all. if not then i won't bother, however i
don't believe the dark patch to remove the gradient works very well on OSX
Which top toolbar, kicad, eeschema, pcbnew?
On 12/15/2015 12:08 PM, Simon Wells wrote:
> I have tested it on OSX with before and after here
>
> http://s14.postimg.org/gf0kty89t/Untitled_1.png
>
> I would prefer to see the top toolbar no longer based on the AUI as i
> think it is unnecessary for
On 12/15/2015 5:13 PM, "Torsten Hüter" wrote:
>
> Hi Wayne,
>
> thank you very much for your efforts. I'm guessing that this is not an easy
> topic and takes thus more time.
> Hopefully a good solution can be found this way.
As soon as I hear back from the FSF, I will forward the license to
On 12/15/2015 12:44 PM, Tomasz Wlostowski wrote:
> On 15.12.2015 16:52, Wayne Stambaugh wrote:
>> Sorry I didn't respond to this sooner but I've been busy. I'm not
>> thrilled with this idea. I know it solves the immediate problem but it
>> is an incomplete solution.
>
> Hi Wayne,
>
> I surely
Hi folks,
I've added 3D per-vertex normal calculations to the 3D model plugins
but I'm calculating bad figures as seen in the *.wrl file below and a
corresponding render from view3dscene:
https://drive.google.com/file/d/0By_XTJN-s8aXX3pCeFhWbTZNYWs/view?usp=sharing
Hi Windsor,
Thank you for the patch, I like the results. Personally, I would love to
have it merged, but we need to check if it does not break anything on
other platforms first.
Regards,
Orson
On 12/14/2015 04:42 AM, Windsor Schmidt wrote:
> Hi everyone,
>
> This is my first post to the list,
Hi Jose,
here is the solution for OSX:
1) add
import PySide
just before (line 48 of StepUp tools 1.3.2.8)
from PySide import QtGui, QtCore
2) and change
name=QtGui.QFileDialog.getOpenFileName(self, "Open File...",
last_file_path, "kicad module files (*.kicad_mod)")[0]
(line 629,630 of
I am doing some modifications to the layer widget and was wanting some
comments. Part of this is making it so that if you LEFT click on the colour
button you get the colour selection dialog. Currently i believe this is
very broken as you should not have a wxButton that does not behave as
expected
It looks nicer in some ways, but I don't think I completely like it.
Two comments I have:
1. A little bit of whitespace in between each color block would make it
look even nicer I think.
2. From this picture it is way, way less obvious that you can click on the
color blocks to change their color.
Hi Wayne, Everyone,
This is the process now. If you have a fill zone, and you start to lay
a track within it, KiCad will assign that track/via to the net of the
zone of the layer you are on. AND, as a board Designer, that's exactly
what you would expect. But then, following this design
Yikes, guys, I have a repeatable crash in the EEschema library editor with
4.0.0 (downloaded from kicad-pcb.org) in OS X 10.11.2.
I cloned a part, and I went to edit it. I was able to change a couple of
the fields, but when I went to change the footprint in the Field
Properties dialog, Kicad
Yes, this is a known issue. Please try a nightly from 12/13 or later to
confirm it fixes the issue for you too.
Adam Wolf
On Tue, Dec 15, 2015 at 8:20 PM, wrote:
> > Yikes, guys, I have a repeatable crash in the EEschema library editor
> with
> > 4.0.0 (downloaded from
Great. Sorry about this.
The fix will be in 4.0.1, any, erm, um, day now? Soon!
Adam Wolf
On Tue, Dec 15, 2015 at 9:45 PM, wrote:
> > Yes, this is a known issue. Please try a nightly from 12/13 or later to
> > confirm it fixes the issue for you too.
> >
> > Adam Wolf
>
>
If it counts for anything, I vote for this patch too. It's not /just/ an
improvement for dark themes, I think it looks way nicer and more
professional for the light themes too. I'd love to clean up those lumpy
gradients :)
Unfortunately I don't have any other platforms at hand to test it on :(
34 matches
Mail list logo