Attached is a trivial patch that puts a check mark on the check-box of
"No copper pour" when a new "Keepout Area Properties" dialog window is
popped up.
The problem:
With pcbnew, when a new keepout zone was created, the dialog window of
"Keepout Area Properties" popped up. This dialog
Here is a bug tacker for the bug:
https://bugs.launchpad.net/kicad/+bug/1683297
This is observed from the latest ( git SHA1 ID:
01f5a129a317522f544e8bf75f4f36668dae1681) build of the master branch,
running in Ubuntu 16.04.
This can be verified by creating a copper zone, and then creating a
a écrit :
On Sun, Apr 16, 2017 at 04:05:10PM +0200, jp charras wrote:
Le 16/04/2017 à 08:38, Joseph Chen a écrit :
Does someone here know how to make this work?
With pcbnew's "footprint properties" dialogue window, the ESC and ENTER keys
are not functioning as
defaults as wit
On 04/16/2017 10:36 AM, jp charras wrote:
Den 16/04/2017 09.39 skrev "Joseph Chen" <joseph.che...@yahoo.com
<mailto:joseph.che...@yahoo.com>>:
Just built kicad from the latest master branch and noticed that pcbnew's
drag zone outlines are
no longer workin
Just built kicad from the latest master branch and noticed that pcbnew's
drag zone outlines are no longer working for me.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe :
Does someone here know how to make this work?
With pcbnew's "footprint properties" dialogue window, the ESC and ENTER
keys are not functioning as defaults as with the "pad properties"
dialogue window.
This inconsistency is a bit of annoying and definite slows me down
during PCB layout.
I
On 03/11/2017 12:58 PM, Tomasz Wlostowski wrote:
On 13.02.2017 01:59, Andy Peters wrote:
I route the signals and run the DRC, and for every corner in the trace
pairs, I get an ErrType(x): “Two Track Ends Too Close” complaint.
Sometimes it’s ErrType(16), sometimes it’s ErrType(17), the rest
--Joe Chen
On 2/20/2017 2:50 AM, Joseph Chen wrote:
Is it a know issue?
Just compiled the latest and found "Save and Exit" is no longer saving
the changes of not using the rescued parts. The net effect is that a
new start keeps popping up "Rescue Helper" asking if to rescued th
Attached is a patch for rearranging part editor icon positions.
The changes were made to rearrange the positions of the first 5 icons in
the part editor so that they are consistent with footprint editor.
--Joe Chen
>From c450e877e65a57a95733f0ff93f53fc281b8e999 Mon Sep 17 00:00:00 2001
object to new library tool bar buttons so they are also
consistent between the two editors.
On 2/20/2017 1:11 AM, Joseph Chen wrote:
The attached patch is a very trivial change for swapping an icon order
inside eeschema's part editor. This change will make the part editor to
be consistent
;
5. Click "OK" again for "No Symbols were rescued" window
6. Immediately, Click "File->Close", and Click "Save and Exist"
7. Exit "kicad"
Now start over from Step 1, the latest kicad will keep popping up the
window from Step 3. And this is no
Is it a know issue?
Just compiled the latest and found "Save and Exit" is no longer saving
the changes of not using the rescued parts. The net effect is that a
new start keeps popping up "Rescue Helper" asking if to rescued the old
parts from the old cache library.
Here is the version
The attached patch is a very trivial change for swapping an icon order
inside eeschema's part editor. This change will make the part editor to
be consistent with the footprint editor's icon order.
The issue, no mater how trivial it may be to other user, is that when
editing a part, you need
On 11/27/2016 11:44 PM, Nick Østergaard wrote:
2016-11-28 0:01 GMT+01:00 Joseph Chen <joseph.che...@yahoo.com>:
As I see it, KiCAD now is using a backward schema in versioning, after
converted to GIT repo.
As most of you guys already know it, GIT has a command "git descr
As I see it, KiCAD now is using a backward schema in versioning, after
converted to GIT repo.
As most of you guys already know it, GIT has a command "git describe
--dirty" for outputting a precise trackable version info. So regardless
of branches, the version string should be set by the
I recently started seeing lots of lines of printed texts on the terminal
where kicad is started in Linux, and a quick grep shows the following
line does the printouts:
pcbnew/router/pns_line_placer.cpp:1046:printf("H-net %d\n",
aHead.Net());
It seems to be a debug output line. Is this
For Linux, Boost 1.59 seems working fine, at least for me for over a
month now. I've been using Boost 1.59 compiled from the source on my
Ubuntu 15.04, and Kicad's been building and running OK for a while with me.
--JC
On 10/19/2015 08:45 AM, Wayne Stambaugh wrote:
Boost 1.59 was just
On 09/25/2015 10:25 AM, jp charras wrote:
Le 25/09/2015 07:36, Joseph Chen a écrit :
Hi @JP,
Have you got a chance to review this submitted patch?
--JC
Yes, I had a look at the patch.
Currently, it creates to many false detections:
- It does not see the fact a local label is connected
Hi @JP,
Have you got a chance to review this submitted patch?
--JC
On 09/14/2015 10:58 PM, Joseph Chen wrote:
@JP,
Attached you can find the patch file for the improvement of optional
ERC's detecting local labels.
Short description:
With this patch, there is an added extra check
tched"
local labels.
I also attached a new test schematic tar ball that can be used for
testing the patch functions.
Thank you for all your valuable comments and insights.
I would appreciate anyone could test this patch out and provide comments
and inputs.
--JC
On 09/14/2015 03:30 AM,
9-13 20:05 GMT+02:00 Wayne Stambaugh <stambau...@gmail.com>:
Joseph,
I committed your patch in the product branch r6191. Thank you for you
contribution to KiCad.
Cheers,
Wayne
On 9/13/2015 12:50 AM, Joseph Chen wrote:
@Wayne & @Nick,
Attached you can find the new patch file th
On 09/13/2015 01:36 PM, Wayne Stambaugh wrote:
The docs in lp:~kicad-developers/kicad/doc are obsolete. The latest
docs are on github and are rebuilt whenever changes are made to the git
repo and should be downloaded from there.
It looks like your original problem is that you either did not
@Wayne,
Your email server rejected this email that has a tar ball of kicad
schematic files.
Hope others who can get the attached tar ball try it out with the ERC
and report the findings back here.
--Joe
On 09/13/2015 10:17 PM, Joseph Chen wrote:
@Wayne and @JP,
Could try ERC
Is this a known issue or just me?
With running KiCAD on my linux, I have long noticed that the "help
documents" are not accessible by the running "KiCAD". I recently found
a work-around to make them work for me. The work-around is to create
some symbolic links as shown here (if your email
we make every effort to keep the product branch as stable as possible so
that developers and users are willing to keep testing it.
Cheers,
Wayne
On 9/11/2015 3:58 AM, Joseph Chen wrote:
> @JP and @Wayne,
>
> Would you take a patch for fixing this ERC'
just those two points, I think it is fine to merge it.
2015-09-11 10:16 GMT+02:00 Joseph Chen <joseph.che...@yahoo.com>:
Hi Nick,
I very much like the true BZR version number that is produced by your script
when compiling from the git mirror source. This is very helpful when
tracking the match
@JP and @Wayne,
Would you take a patch for fixing this ERC's not detecting local labels?
I know we were reminded not to, but I believe this fix should be in the
stable release. See my explanation below.
On 09/01/2015 12:09 AM, jp charras wrote:
Le 01/09/2015 04:59, Joseph Chen a écrit
w if it should be committed.
Thanks,
Wayne
On 8/30/2015 4:24 PM, Joseph Chen wrote:
Please review and apply the attached patch file of CreateGitVersion.cmake.
*Issue to be fixed: a False BZR version number**
*
The details:
After cloning the repo of git-source-mirror, and working in my own local
branc
Please review and apply the attached patch file of CreateGitVersion.cmake.
*Issue to be fixed: a False BZR version number**
*
The details:
After cloning the repo of git-source-mirror, and working in my own local
branch, and committing a X times, the BZR version-number that is
generated by file
This is a resubmitting of a patch file (attached) that fixes the issue
of [Bug 1487945]. This time it it more coding style compliant as
suggested in other developer's comments.
The fix passed tests on Ubuntu 15.04, based off KiCAD BZR 6133
--Joe
-- Here is the copy paste of the patch
.
The wxString line should probably also have a space in betweent he two
end parenthesis, but I am not sure.
And will add the space as you suggested.
--Joe
I have not reviewed the patch further than that, FWIW.
2015-08-27 7:37 GMT+02:00 Joseph Chen joseph.che...@yahoo.com:
I am submitting a patch
I am submitting a patch file (attached as well) that enables the
eeschema ERC to generate errors for any and all unmatched global labels.
This patch resolves the issue that I reported in [Bug 1487945].
I have tested the patch on Ubuntu 15.04 and it passed all my test cases
The patch is based
Can someone point me to a good instruction of building KiCAD from the
git mirror source? And What I missed that is resulting some errors
shown below?
BTW, my same ubuntu has been working with kicad-install.sh, but I just
started trying the git source tree building.
With the git source
Does anyone know the possible causes for my following run-time errors?
These are happening from my KiCAD BZR 6112 of self-compiled on Ubuntu 15.04:
All KiCad --install-or-update steps completed, you are up to date.
jchen@thermaltake:~$ kicad
(kicad:5297): Gtk-CRITICAL **:
output.
I saw stuff like in many other applications too.
Mario
From: Kicad-developers
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of
Maciej Sumiński [maciej.sumin...@cern.ch]
Sent: 22 August 2015 13:52
To: Joseph Chen; kicad
I had that problem, too.
The problem went away after I (1) installed libwxwebgtk-dev first, (2) and then
downloaded the source of wxWidget-3.0.2 (google it will find it) and recompiled
it with these steps:
$ cd wxwidget-3.0.2
$ ./configure --prefix=/usr$ make$ sudo make install$ cd
$ rm -rf
to the deb package install. Thank you for your
contribution to kicad.
Kind Regards,
Wayne
On 10/14/2014 8:57 PM, Joseph Chen wrote:
Here is the patch (attached as well) for enhancing kicad-install.sh
handling of two error situations with Debian/Ubuntu:
1. The prerequisites are installed
the deb file from a newer verison of ubuntu.
So that could probably also be used. I have not tested it my self yet.
There exists some PPA for wx3, but this was missing wxgtk or wxpython,
I don't exactly remember.
Nick
2014-10-17 6:43 GMT+02:00 Joseph Chen joseph.che...@yahoo.com:
Hi Wayne
of the installation script.
I hope the patch can be integrated back to the main branch. But if you decide
not to do it, it's perfectly OK with me.
--Joe
On Thursday, October 16, 2014 12:06 PM, Wayne Stambaugh
stambau...@verizon.net wrote:
On 10/15/2014 9:25 PM, Joseph Chen wrote:
Hi Wayne
to the list of prerequisite packages. I thought that
was what needed fixing or am I not understanding the original issue?
Wayne
On 10/14/2014 8:57 PM, Joseph Chen wrote:
Here is the patch (attached as well) for enhancing kicad-install.sh
handling of two error situations with Debian/Ubuntu:
1
I have emailed out a patch for kicad-install.sh, which will fix the problem
you encountered.
--Joe
On Monday, October 13, 2014 12:14 AM, Benoît Roehr
benoit.roehr...@gmail.com wrote:
Finally succesfully build kicad on a all fresh Ubuntu 14.04 yesterday.
apt-get build-dep kicad
Sure will do.
On Monday, October 13, 2014 10:40 AM, Wayne Stambaugh
stambau...@verizon.net wrote:
If you can modify the script properly, please do so and send a patch to
the mailing list. Thank you for your help.
Cheers,
Wayne
On 10/12/2014 10:26 PM, Joseph Chen wrote:
If you
If you want me to, I can help with modifying the script to enhance the two
error handling and testing it with Ubuntu 14.04.
On Sunday, October 12, 2014 3:55 PM, Wayne Stambaugh
stambau...@verizon.net wrote:
On 10/12/2014 1:49 PM, Mark Roszko wrote:
He wasn't commenting about
I have been using kicad-install.sh script to install kicad in a few of
Ubuntu-14.04, and have found the script needs more error hadnling. Here are
some areas:
1. install_prerequisites()This function is using a single command apt-get
install for ALL of the software packages. It would work
Thank you Wayne!
--Joe
On Sunday, September 28, 2014 6:40 PM, Wayne Stambaugh
stambau...@verizon.net wrote:
Fixed in commit r5154. Please let me know if you find any other issues
other than the fact that your distro may not have packaged wx3 yet.
On 9/27/2014 2:07 AM, Joseph
I was able to build kicad from this new revision, after some troubles with my
Ubuntu.
But I had to modify kicad-install.sh so it could keep going forward to a
completion or stop when an error happened. Otherwise, the build script just
checkout source, installed a bunch of libray files and doc
46 matches
Mail list logo
