Re: [Kicad-developers] KiCad Janitor moves

On 12/12/18 12:25 AM, Seth Hillbrand wrote: > Am 2018-12-11 12:16, schrieb Maciej Sumiński: >> Recently KiCad Janitor had been rather unreliable, mostly due to my >> capricious Internet connection, so a few minutes ago he has got a new >> home at one of CERN servers. It used

[Kicad-developers] KiCad Janitor moves

Recently KiCad Janitor had been rather unreliable, mostly due to my capricious Internet connection, so a few minutes ago he has got a new home at one of CERN servers. It used to work as a webhook, but in order to improve robustness I have switched it to polling (updates every 2 minutes). I expect

Re: [Kicad-developers] [PATCH] Numeric evaluator tests + unary "+"

Hi John, Thank you for the patches, I have just merged them. I particularly appreciate the unit tests, well done! Cheers, Orson On 11/28/18 5:03 PM, John Beard wrote: > Hi, > > Here are some patches for the numeric evaluator. > > There are three parts: > * Add tests and test current behaviour

Re: [Kicad-developers] Dialog field validation on KillFocus

On 11/29/18 2:36 PM, Jeff Young wrote: > While most UI guidelines suggest validating on field exit, it’s not without > cost. In particular, on GTK we can’t tell the difference between a KillFocus > from clicking the OK button (when validation should be run) and a KillFocus > from clicking

Re: [Kicad-developers] Adding global mouse shortcuts in GAL tool framework

Hi John, One possible way of solving the problem is to change the m_defaultHotkey in TOOL_ACTION class to a TOOL_EVENT field which says what triggers the action. Then ACTION_MANAGER instead of comparing hotkeys should run TOOL_EVENT::Matches() to check whether a processed TOOL_EVENT is supposed

Re: [Kicad-developers] warning: enum constant in boolean context in dialog_print_generic.cpp

Hi Andrew, Good catch, thank you! I have just pushed your patch to the master branch. Regards, Orson On 11/7/18 6:16 AM, Andrew Lutsenko wrote: > Hi Orson and KiCad devs, > > During rebuilding current nightly I noticed this warning and decided to > look into it. > >

Re: [Kicad-developers] [PATCH] Verify wxPython.h exists.

Hi Wayne, I have eventually checked the patch on Linux and Windows 7 as well and it works as advertised, so I pushed it. Thank you for your contribution to KiCad;) Cheers, Orson On 10/29/18 1:33 PM, Maciej Sumiński wrote: > Hi Wayne, > > KiCad with your patch applied builds fine

Re: [Kicad-developers] eeschema depends on libngspice.so instead of libngspice.so.0?

On 10/30/18 6:57 AM, Carsten Schoenert wrote: > Hello Orson, > > Am 29.10.18 um 21:06 schrieb Maciej Suminski: >>> works for me with current HEAD from today within Debian testing. >>> >> I should have said it earlier: one of the goals is to make dh_shlibdeps >> happy, but I do not use Debian so I

Re: [Kicad-developers] [PATCH] Verify wxPython.h exists.

Hi Wayne, KiCad with your patch applied builds fine on macOS 10.13.6, so it looks like you got the paths right. Cheers, Orson On 10/22/18 11:11 PM, Wayne Stambaugh wrote: > I created a patch to fix bug report 1785663. It works on linux and > windows msys2 builds. On these platforms wxPython.h

Re: [Kicad-developers] eeschema depends on libngspice.so instead of libngspice.so.0?

Hi Carsten, On 10/27/18 11:50 AM, Carsten Schoenert wrote: [snip] > I'd really appreciate if the situation could be improved here somewhere > in the future! Can you check if the attached patch solves the problem? It still does not recognize the right libngspice file under Windows, but I need to

Re: [Kicad-developers] eeschema depends on libngspice.so instead of libngspice.so.0?

Hi Wayne, On 10/27/18 11:08 PM, Wayne Stambaugh wrote: [snip] > Me too. This is why I had reservations about Stefan's patch. It is a > temporary fix at best. As soon as the libngspice so version number > changes, we will be in trouble. Even worse when one disto is still > using 0 and another

Re: [Kicad-developers] [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears

On 10/26/18 2:29 AM, Tomasz Wlostowski wrote: [snip] > I made a variant of the dialog that (hopefully) is easier to understand. > This raises another question: do we have any means of reporting bugs > without forcing the users to register on launchpad, for example a public > Kicad bug email (e.g.

Re: [Kicad-developers] 5.1

On 10/25/18 2:23 AM, Seth Hillbrand wrote: > Am 2018-10-24 17:20, schrieb Maciej Suminski: >> Actually I was pretty sure that my approach is bullet-proof, but perhaps >> I do not get where the trap is hidden. As far as I understand, Seth >> experienced problems when pcbnew (wxWidgets/gtk2) loaded

Re: [Kicad-developers] [RFC] wxPhoenix support

I have briefly tested the branch with Phoenix/Python3/GTK3 and wxPython/Python2/GTK3 on Linux - no problems observed so far. Well done, thank you Thomas! Cheers, Orson On 10/23/18 3:56 PM, Thomas Pointhuber wrote: > Hi Wayne, > > The console crash is already fixed in the merge request: >

Re: [Kicad-developers] 5.1

On 10/23/18 3:00 PM, Seth Hillbrand wrote: > The issues were asserts, missing icons and a crash on exit.  I tracked > it down to a wx module that was loaded by pip in my user cache from when > I was testing gtk3 builds.  Yay, python.  Removing it cleared all issues. Indeed it sounds like

Re: [Kicad-developers] 5.1

Hi Seth, On 10/22/18 11:50 PM, Seth Hillbrand wrote: > Hi Orson- > > This looks very nice.  It works well for me with scripting off on Debian > Stretch.  I had some issues with scripting on that I haven't encountered > with the master branch but I suspect that this is a gtk2/3 issue because > I

Re: [Kicad-developers] ideas to improve patch and CI integration

Hi Thomas, I like Gitlab, but it is a matter of taste and obviously the final word belongs to Wayne. I think the main problem would be to transfer the bug tracker and decide what to do regarding the mailing list. Another point is a plan for a case when Gitlab turns evil. Currently they offer

Re: [Kicad-developers] 5.1

On 10/17/18 8:30 PM, Wayne Stambaugh wrote: > Now that the Eeschema gal code has been merged into the development > branch and things seem reasonably stable, we need to start thinking > about the 5.1 release. I would like to merge Thomas' python 3 code and > Orson's cairo print code as soon as

Re: [Kicad-developers] 5.1

On 10/18/18 9:48 PM, s...@hillbrand.org wrote: > Hi Wayne- > > We should probably start moving the default build on some Linuxes over > to gtk3 as the gtk2/3 conflicts were one of the prime drivers to the > GAL-legacy switch in eeschema.  This requires turning on > -DUSE_WX_GRAPHICS_CONTEXT as

Re: [Kicad-developers] Janitor cleanup

Hi Seth, I have just executed the script. FYI: 81 bugs fixed in 5.0.1, well done! Cheers, Orson On 10/9/18 8:29 PM, Seth Hillbrand wrote: > Hi Orson- > > Do you have the janitor script that you used to bulk-mark the fixed bugs > for 5.0? If so, would it be possible to re-run that for 5.0.1? >

Re: [Kicad-developers] Cairo printing

Hi Jean-Pierre, On 10/9/18 12:04 PM, jp charras wrote: [snip] > Hi Orson, > > The transparency issue (specific to Cairo render) is a minor issue (see > attached picture, especially the oval pad) on screen, but could be more > annoying on printed documents. Agreed, colors in printouts need to be

Re: [Kicad-developers] Cairo printing

Hi Simon, On 10/8/18 3:19 PM, Simon Richter wrote: > Hi, > > On 10/08/2018 08:59 AM, Maciej Sumiński wrote: > >> The only reasonable way to make wxDC and Cairo compatible is via >> wxGraphicsContext, as it uses Cairo underneath. > > wxDC also uses Cairo intern

Re: [Kicad-developers] Cairo printing

Hi Jean-Pierre, On 10/8/18 3:08 PM, jp charras wrote: [snip] > Hi Orson, > Very good job. > > I tested the Cairo printing both on Windows and Linux. > > No problem on Linux. > On Windows, I have strange artifacts (see attached picture) in print > preview. > (more strange, if a zone outline

Re: [Kicad-developers] Cairo printing

Hi Zoltan, Good catch, I have just fixed the problem in cairo_printing branch. Regards, Orson On 10/8/18 10:49 AM, zgyarm...@zgyarmati.de wrote: > Dear Maciej, > > i checked out and compiled your branch, it builds properly (Ubuntu 18.04, > x86_64), but when i tested the print functionality, i

Re: [Kicad-developers] Cairo printing

On 10/7/18 10:05 PM, Wayne Stambaugh wrote: [snip] > This makes me nervous. The gdiplus library brings wxGraphicsContext > into play on windows. Something from wxGraphicsContext is being pulled > into the kicad build which can be enabled by configuring builds with > -DUSE_WX_GRAPHICS_CONTEXT=ON.

[Kicad-developers] Cairo printing

I have finished printing code refactor to take advantage of GAL in pcbnew and gerbview [1]. This branch together with GALified eeschema should cure GTK3-related headaches and lead us straight to 5.1. In the meantime I will also try to port eeschema to the new printing system for the sake of

Re: [Kicad-developers] [PATCH] Fix focus bug and possible race-condition for path deletion

Thank you Thomas, I have just pushed your patch to the master branch. Cheers, Orson On 09/02/2018 08:59 PM, Thomas Pointhuber wrote: > Ping: please review and merge this little patch > > On 30.08.18 14:23, Thomas Pointhuber wrote: >> Hi, >> >> a small follow-up patch for >>

Re: [Kicad-developers] SPICE models and library symbols

Hi Nhat, There are fields dedicated to Spice model definitions, try to set a model with the Spice Model editor dialog (in the Component Properties dialog [1]) and notice that new fields will appear. Cheers, Orson 1. http://docs.kicad-pcb.org/5.0.0/en/eeschema.html#_assigning_models On

Re: [Kicad-developers] MacOS build issue with new geometry tests

Hi John, Thanks for the patch. I have had the same problem compiling KiCad with clang and I confirm that the proposed fix solves the problem, so I merged it. Cheers, Orson On 07/29/2018 05:34 PM, John Beard wrote: > Hi Adam, > > Sorry, this in my stuff - I though that was a way to get PI

Re: [Kicad-developers] Fix CMakeLists.txt

Hi Marcus, Actually my memory has let my down this time. I have just checked the patch on msys2 and it worked as expected, so I recommitted the original version. Sorry for the noise. Cheers, Orson On 07/26/2018 11:36 PM, Aimylios wrote: > Hi Orson, > > thank you for taking the time to review

Re: [Kicad-developers] Branches

On 07/25/2018 11:23 AM, Carsten Schoenert wrote: > Hello Orson, > > Am 25.07.18 um 15:53 schrieb Maciej Sumiński: > ... >> It has been discussed in this thread already, but I will repeat: the >> main problem now is that we need to apply patches to both master

Re: [Kicad-developers] Branches

On 07/25/2018 04:28 AM, Carsten Schoenert wrote: > Am 24.07.18 um 15:01 schrieb Maciej Sumiński: >> At the moment the master branch contains all commits from 5.1 and a few >> more. It might be the right moment to drop 5.1 branch. > > This depends on the achievements which

Re: [Kicad-developers] Hotkeys in GAL

Hi John, On 07/24/2018 07:21 PM, John Beard wrote: > Hi, > > I have a few questions about hotkeys in GAL tools: > > 1) Is there are reason so many GAL tools don't get hotkeys? > > Very many TOOL_ACTIONS have a hotkey set to '0'. Most others that do > have a hotkey have a LegacyHotkey

Re: [Kicad-developers] Adding "Apply" to the 3D viewer display options dialog

Select the Apply button you want to handle, and in the Object Properties panel, Events tab - add an event handler. It will be added to the generated *_BASE class and all you need to do is override it. Cheers, Orson On 07/24/2018 09:10 AM, David Griffith wrote: > > I'm at a loss to figure out

Re: [Kicad-developers] Branches

...and also rename it to 5.1-dev (no rc yet). On 07/24/2018 09:47 AM, Jeff Young wrote: > +1 > >> On 24 Jul 2018, at 08:01, Maciej Sumiński wrote: >> >> At the moment the master branch contains all commits from 5.1 and a few >> more. It might be the right moment to

Re: [Kicad-developers] Branches

At the moment the master branch contains all commits from 5.1 and a few more. It might be the right moment to drop 5.1 branch. Cheers, Orson On 07/20/2018 11:14 AM, Maciej Sumiński wrote: > We already have slightly diverged the branches, I think it shows that it > is hard to mainta

Re: [Kicad-developers] KIDIALOG broken

Hi Wayne, On 07/23/2018 05:40 PM, Wayne Stambaugh wrote: > In the process of fixing this bug > https://bugs.launchpad.net/kicad/+bug/1782708 I discovered that the > KIDIALOG object called when editing an externally defined environment > variable will completely lock up kicad on windows. Clicking

Re: [Kicad-developers] Branches

We already have slightly diverged the branches, I think it shows that it is hard to maintain two branches with cherry-picking. Details below: Commits present in master, but not in 5.1: commit c585964da98269db2cabf06daafb0b11cae3a4ec fix coding style issues. commit

Re: [Kicad-developers] Janitor commits missing

Some new issues popped up when I added support for multiple branches in the Janitor script. I hope the problems are fixed now, sorry for the inconvenience. Cheers, Orson On 07/17/2018 07:10 PM, Seth Hillbrand wrote: > ​Hi Orson- > > I'm seeing Jeff's cherry-picked commits being processed by

Re: [Kicad-developers] Branches

It will be a huge motivation for us to fix GTK3 problems as soon as possible. I assume you mean to drop the current master branch (or rename to 6.0?) and make 5.1 the new master branch? On 07/19/2018 05:19 PM, Wayne Stambaugh wrote: > You are preaching to the choir. I did most of the maintenance

Re: [Kicad-developers] 5.1 branch

;> are implemented, with the symbol preview widgets & library browser >> remaining. >> >> >>> I'm assuming the printing is a v6 goal. >> >> Orson made quite a lot of progress with Cairo printing. IIRC it can make >> it to the 5.1. >> &g

[Kicad-developers] Branches

I wonder if there is a point in keeping 5.1 and master branches separated. In 5.1 there is a lot of new code that will need patches, and they need to be applied to both branches now. If we keep adding more features to the master branch, then at one point the branch may diverge significantly enough

Re: [Kicad-developers] Signed Installers

Hi Simon, The installer works well, no warnings observed here. Do you think you could create one for 5.0.0 stable and upload it to windows/stable directory? Cheers, Orson On 07/19/2018 01:17 AM, Simon Richter wrote: > Hi, > > I've just rebuilt the latest MSYS2 nightly and the rc3 package in >

Re: [Kicad-developers] Stable 5 release.

Tell me if I am wrong, but I start to believe we are going to publish v5 this Friday. Is there anything missing I could help with? Do we have the website updates ready? Cheers, Orson On 07/11/2018 08:49 PM, Wayne Stambaugh wrote: > Are there any critical bugs remaining to be fixed for the stable

Re: [Kicad-developers] Janitor commits missing

It should work fine now. After I had ran the clean-up script, the credentials file was overwritten by another user, depriving the web server access rights. Fortunately there is no ban for massive bug status update. Cheers, Orson On 07/18/2018 08:51 AM, Maciej Sumiński wrote: > Hi Seth, >

Re: [Kicad-developers] Janitor commits missing

Hi Seth, I have noticed it too. There is no special treatment for cherry-pick commits, the only thing Janitor cares about is 'Fixes' line. I checked the logs and apparently Janitor is unable to log in to Launchpad. I hope that the recent bug statuses clean up has not granted him a ban for

Re: [Kicad-developers] 5.1 branch

o broken. A simple workaround is to remove printing completely and request users to use PDF plotting. Cheers, Orson > On 7/16/2018 11:15 AM, Maciej Sumiński wrote: >> Tom has already prepared a proof-of-concept eeschema with GAL rendering, >> which still uses the legacy tools. I have so

[Kicad-developers] How sophisticated is the bug closure script?

On 07/15/2018 11:20 PM, Jeff Young wrote: > Hi Orson, > > I was asking about the Fix Committed -> Fix Released script (assuming it is a > script), rather than the *** -> Fix Committed script. Frankly, I could not recall how we have updated the bug statuses after the previous release. This time

Re: [Kicad-developers] 5.1 branch

sed which would not be correct. > > On 7/16/2018 11:08 AM, Maciej Sumiński wrote: >> It is terribly tedious to go through the bug list and change statuses >> one by one, so I offer to help with the bug report status fiddling. We >> may employ Janitor, but I guess it would be better

Re: [Kicad-developers] 5.1 branch

Tom has already prepared a proof-of-concept eeschema with GAL rendering, which still uses the legacy tools. I have some promising results switching the printing system to Cairo GAL. Obviously we will face some unexpected obstacles, but I have high hopes. Cheers, Orson On 07/16/2018 03:40 PM,

Re: [Kicad-developers] 5.1 branch

It is terribly tedious to go through the bug list and change statuses one by one, so I offer to help with the bug report status fiddling. We may employ Janitor, but I guess it would be better to execute a simple script to change Fix Committed->Fix Released whenever we release a new version.

Re: [Kicad-developers] New Kicad Features

Hi Tom, You can see our plan in the v6 roadmap [1], but the only related topic is the board stack up editor, which appears to be a prerequisite for the mentioned features. Obviously, it does not mean we are limited by the roadmap, but we need additional contributors for that to happen. We are

Re: [Kicad-developers] Build failed in Jenkins: kicad-qa #4256

For the record: the issue has been already fixed by Jean-Pierre and was not really related to the documentation fixes. Thank you! Cheers, Orson On 06/12/2018 04:28 PM, Miguel Angel Ajo wrote: > See > > Changes: > >

Re: [Kicad-developers] Janitor needs a kick

Whoops! Apparently trying to change status of a non-existent bug report drove him insane. He has already taken his pills, everything should be back to normal soon. Sorry for the mess. Cheers, Orson On 06/13/2018 02:48 AM, Seth Hillbrand wrote: > I don't think it was my formatting but the last

Re: [Kicad-developers] [PATCH] Fix -Wparentheses warning in track_cleaner.cpp

Hi John, Thank you for the patch, I have just pushed it to the master branch. Cheers, Orson On 06/12/2018 12:16 PM, John Beard wrote: > Hi, > > This is a very simple patch to address a -Wparentheses warning in > pcbnew/track_cleaner.cpp. > > It was "wxBusyCursor( dummy );", it is now

Re: [Kicad-developers] Help finding routing option

Hi Seth, Your head is fine, do not worry. You will find the option in the PnS right click context menu: Select Track/Via Width->Use Netclass Value (I have just realized that the former should be called "Select Track/Via Size). Grepping for ID_POPUP_PCB_SELECT_USE_NETCLASS_VALUES will get you the

Re: [Kicad-developers] [PATCH] Fix 'catching polymorphic type by value' warnings

Thank you John, I have just pushed your patch. Cheers, Orson On 06/05/2018 10:02 AM, John Beard wrote: > Hi, > > Sorry, I missed one out in kicad/import_project.cpp > > Cheers, > > John > > On Tue, Jun 5, 2018 at 8:43 AM, John Beard wrote: > >> Hi, >> >> Small patch to fix some warnings

Re: [Kicad-developers] Proposal to remove Default Pad Properties in 6.0

Hi Jeff, I think this is yet another problem where Object Inspector comes to rescue. There are more dialogs to execute massive object modification that could be easily handled with OI, so hopefully we can get rid of them in the future. Cheers, Orson On 05/31/2018 02:35 PM, Jeff Young wrote: >

Re: [Kicad-developers] [PATCH] Symbol Library Editor: syncing state of search tree tool button with search tree panel

Well spotted! Thank you for the patch, I have just pushed it to the master branch. Regards, Orson On 05/30/2018 04:04 PM, Константин Барановский wrote: > Button "Toggle the search tree" from left toolbar of Symbol Library > Editor does not show actual state of visibility of the search tree >

Re: [Kicad-developers] partially untranslated strings in simulation dialog

Thank you Marco, I have just pushed your patch. Regards, Orson On 05/28/2018 11:37 AM, Marco Ciampa wrote: > On Mon, May 28, 2018 at 07:55:16AM +0200, Carsten Schoenert wrote: >> Hello Marco, >> >> Am 27.05.2018 um 12:10 schrieb Marco Ciampa: No apologies needed at all, Maciej! But I

Re: [Kicad-developers] partially untranslated strings in simulation dialog

Hi Marco, It should be fixed now, apologies for missing these strings until now. Cheers, Orson On 05/25/2018 11:15 AM, Marco Ciampa wrote: > Hi dev, > I am sorry for boring you all (as usual) with trivial (i18n) things. > Launching the Spice Simulator dialog I just noted a few untranslated >

Re: [Kicad-developers] Footprint Library Wizard removal

24/05/2018 à 10:19, Maciej Sumiński a écrit : >>> Attached a revised patch set, as the previous one looked ugly on Windows >>> (and fine on Linux). >> >> Thanks Orson. >> >> The look of this dialog is much better now. >> >> Just two remarks about t

Re: [Kicad-developers] More default fields in schematic

One more field that could become predefined and receive a special meaning is 'Mounted' or similar. This will come handy when we decide to support assembly variants and will let us add a visual distinction between mounted and not mounted components if we want it. The remaining fields is a matter

Re: [Kicad-developers] Indeterministic netlist export for multiunit components

(or perhaps even try and group units by matching >> their fields). But that carries enough risk to relegate it to 6.0 along >> with the undo stuff. >> >> Cheers, >> Jeff. >> >> >>> On 18 May 2018, at 12:16, Sergey A. Borshch <sb...@users.sour

Re: [Kicad-developers] 5.0 RC2 / release status

Hi Jon, Welcome back! There was one very serious issue [1] blocking RC2, but fortunately it was fixed yesterday. Looking at the to-do list for v5 [2], there are three minor issues and two more serious bugs that may need some extra data from the reporters. It would be great to have the former two

[Kicad-developers] Indeterministic netlist export for multiunit components

Hi, Recently I have found out that the netlist exporter uses an algorithm that for multiunit components uses non empty field values from the last processed unit [1]. The problem is that the processing order depends on the order of the units in the item list, so completely random. Instead, I

Re: [Kicad-developers] Another dialog preview

Nice, this is how a modern settings dialog should look like! Cheers, Orson On 05/17/2018 04:41 PM, Jeff Young wrote: > Just thought I’d share something from my 6.0 tree: > > > > > > > > > ___ > Mailing list:

Re: [Kicad-developers] Track & via clearances only in Legacy...

maybe it has something to do with a hidpi screen >> which I assume Jeff is using and the line thickness used for the drawing? >> >> 2018-04-25 8:32 GMT+02:00 Maciej Sumiński <maciej.sumin...@cern.ch >> <mailto:maciej.sumin...@cern.ch>>: >> Hi Jeff, >> >

Re: [Kicad-developers] Track & via clearances only in Legacy...

Hi Jeff, Are these options broken on macOS? I see clearance lines displayed for all items (pads, tracks, vias) in GAL. example: https://imgur.com/a/LtFtWgR Cheers, Orson On 04/24/2018 08:50 PM, Jeff Young wrote: > I just discovered that “Show track clearances” and “Show track clearances >

Re: [Kicad-developers] Windows builds broken?

Sincere apologies. As far as I can see, Jean-Pierre has already pushed a fix. Orson On 04/24/2018 03:22 PM, Wayne Stambaugh wrote: > Is anyone else have issues with broken windows builds? I'm getting this > error after pulling the latest changes: > >

Re: [Kicad-developers] [RFC] Remove bus joining behavior from KiCad after 5.0 release

Hi Reece, Have a look at an earlier message regarding bus upgrades [1]. Cheers, Orson 1. https://lists.launchpad.net/kicad-developers/msg32423.html On 04/20/2018 05:15 PM, Reece R. Pollack wrote: > Let's not forget the pending wishlist item Bug #1419146 >

Re: [Kicad-developers] [RFC] Remove bus joining behavior from KiCad after 5.0 release

I agree this a slightly confusing feature, which requires reading the user manual to discover. I vote for removal, but we need a clever migration plan to do so. I am not sure how easy would it be to implement it, but how about the following automatic fix: - determine the superset of connected

Re: [Kicad-developers] Serious Lib cache issue, and fix in commit 2974a2c10

, cache library symbol names look just like > LIB_IDs using the LIB_NICKNAME:SYMBOL_NAME format. > > Cheers, > > Wayne > > On 4/16/2018 9:03 AM, Maciej Sumiński wrote: >> Hi Jean-Pierre, >> >> I understand the patch and thank you for the fix, but appa

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Hi Jeff, Are you referring to lp:#1761378 [1] and lp:#1763223 [2] or there are more bugs? If you have the commits already published somewhere, would you give links to them? It is easier to evaluate an approach while looking at related code. Cheers, Orson 1.

Re: [Kicad-developers] Serious Lib cache issue, and fix in commit 2974a2c10

Hi Jean-Pierre, I understand the patch and thank you for the fix, but apparently I do not have enough knowledge about caching in eeschema to comment on the approach. Frankly, I was a bit surprised to find out that colons are permitted in symbol names stored in a cache library. Regards, Orson On

Re: [Kicad-developers] Spaces in library nicknames

file format. Once they are in place, I will remove the spaces > restriction. > > Cheers, > > Wayne > > On 04/13/2018 05:45 AM, Maciej Sumiński wrote: >> Another question is whether spaces are considered valid in library item >> names (symbols/footprints). Should both logical

Re: [Kicad-developers] Spaces in library nicknames

Another question is whether spaces are considered valid in library item names (symbols/footprints). Should both logical library names and library items permit the same character set? Seems reasonable to me, but I need to be sure. Cheers, Orson On 04/13/2018 11:36 AM, Maciej Sumiński wrote: >

[Kicad-developers] Spaces in library nicknames

I have just noticed that one cannot use spaces in symbol library nicknames [1], whereas they are valid for footprint library nicknames [2]. I suppose it should be unified and moved to a function (static method in LIB_ID?) to avoid valid characters sets diversion. I will fix it, but I need to know

Re: [Kicad-developers] wxPython-gtk3 woes

It seems the easy solution to me too. I just wonder how many people rely on the Python shell or GUIs done with wxPython. On 04/10/2018 01:32 PM, Jeff Young wrote: > I never got KICAD_SCRIPTING_WXPYTHON to work on my Mac, and I can’t say I’ve > missed it. > >> On 10 Apr 2018, a

[Kicad-developers] wxPython-gtk3 woes

Apparently mixing wxWidgets-gtk2 and wxPython-gtk3 [1] is not only an Arch issue anymore, as the upcoming Ubuntu release (bionic) also provides wxPython package built against gtk3 [package: 2, bug report: 3]. There are two things we can do to fix the problem for v5: - Backport python-wxgtk3.0

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Hi Jean-Samuel, I suppose most people on the dev mailing list compile KiCad themselves, but I am pretty sure the users would appreciate the possibility of having two KiCad versions installed. If you think the package is ready to be tested by a wider group, how about announcing it on the

Re: [Kicad-developers] rc2

On 04/03/2018 01:20 PM, Tomasz Wlostowski wrote: > On 03/04/18 13:17, Nick Østergaard wrote: >> I think we should not disable the github plugin, but we may need to >> remove it from the wizard in a way that does not emphasize that this is >> the way to go. Maybe it is ok to remove it completely

Re: [Kicad-developers] Spice simulation on macOS

value : 1.0e+00 > > No. of Data Rows : 61 > > I get nice plots when adding a signal. > > Cheers, > Jeff. > > >> On 26 Mar 2018, at 12:30, Maciej Sumiński <maciej.sumin...@cern.ch> wrote: >> >> Would someone running nightlies on macOS test

[Kicad-developers] Spice simulation on macOS

Would someone running nightlies on macOS test the Spice simulator? In particular, please simulate demos/simulation/sallen_key from our bundled demos and see if you get warnings "Unknown model type spice2poly - ignored". Testing both a self-built nightly and our official package [1] would be

Re: [Kicad-developers] [PATCH] Don't create an extra segment at the end of closed SHAPE_LINE_CHAIN

Hi Jon, If we decide to handle this special case, then we need to account for the point count as well. Otherwise it may lead to situations when the number of points is higher than the number of segments. Please see the attached patch (particularly 0002). I think these changes might be committed

Re: [Kicad-developers] compil warning in eagle plugin.

Hi Jean-Pierre, I have just fixed it. Fortunately, 'radius' is used in a while loop that requires the preceding if clause to be true. 'Radius' is initialized in the mentioned if clause body, so it should never run with an uninitialized value. Regards, Orson On 03/14/2018 03:21 PM, jp charras

Re: [Kicad-developers] Need guidance/hints on accessing list of available pcbnew footprints from python

Hi Miles, Have you seen FOOTPRINT_VIEWER_FRAME::ReCreateFootprintList() (pcbnew/footprint_viewer_frame.cpp)? It might be the easiest way to go. Perhaps it could be wrapped in a function provided by the scripting interface. I could not find 'includefallback' option you have mentioned, would you

Re: [Kicad-developers] Deletion in plugins causing trouble

ectator, so there's a lot I don't know. > > > > > > On Fri, Mar 2, 2018 at 2:47 PM, Wayne Stambaugh <stambau...@gmail.com> > wrote: > >> LOL, I just replied to Miles. Thanks Orson for helping out! >> >> On 3/2/2018 8:36 AM, Maciej Sumiński wrote: &

Re: [Kicad-developers] Deletion in plugins causing trouble

ad the arguments from the previous thread but I'm not convinced. > I'm also just a kicad spectator, so there's a lot I don't know. > > > > > > On Fri, Mar 2, 2018 at 2:47 PM, Wayne Stambaugh <stambau...@gmail.com> > wrote: > >> LOL, I just replied t

Re: [Kicad-developers] Handling invalid characters in symbol/component LIB_IDs

On 03/06/2018 07:34 PM, Wayne Stambaugh wrote: > Orson, > > On 3/6/2018 8:55 AM, Maciej Sumiński wrote: >> I am trying to find a reasonable way to handle symbol and components >> with invalid characters in their LIB_IDs (see bug report #1752419 [1]). >> While now

Re: [Kicad-developers] Zone filling problems

Hi Steven, Good catch, thank you for the report. It should be already fixed (a3562b35 and later). Regards, Orson On 03/07/2018 06:28 AM, Strontium wrote: > Sorry for posting this, AND also posting a bug report, but i know you > guys are close to releasing a V5 and i have been testing RC2 from >

Re: [Kicad-developers] Handling invalid characters in symbol/component LIB_IDs

). Normally you can use slash.lib, but if you want to check what happens in case of a conflict, then use the other one. On 03/06/2018 02:55 PM, Maciej Sumiński wrote: > I am trying to find a reasonable way to handle symbol and components > with invalid characters in their LIB_IDs (see bug report #1752

[Kicad-developers] Handling invalid characters in symbol/component LIB_IDs

I am trying to find a reasonable way to handle symbol and components with invalid characters in their LIB_IDs (see bug report #1752419 [1]). While now it is impossible to create such LIB_IDs, we need to handle documents that had been created before the restriction was introduced. LIB_IDs in

Re: [Kicad-developers] Mac HighDPI performance

Wayne, According to our plan, eeschema GALification is one of the major points of v6 roadmap. We plan to start it early, but I think it is better to begin with the schematic model refactor, as GAL and Tool Framework heavily rely on that. Doing things in reverse order means we will have more code

Re: [Kicad-developers] Deletion in plugins causing trouble

Hi Miles, I suppose the silence in the thread indicates there are not many developers knowing the Python scripting interface inside out. Since you are both studying the scripting interface and developing own scripts, it is quite possible you are the most competent person to give us an advice on

Re: [Kicad-developers] [PATCH] Restore some missing visibility items from board file

Thank you Andrzej, I have just merged your patch. Cheers, Orson On 03/02/2018 01:52 AM, Andrzej Wolski wrote: > I'm resending a patch from this thread: > https://lists.launchpad.net/kicad-developers/msg34285.html > > I believe it should go into rc2? > > State of some recently added checkboxes

Re: [Kicad-developers] New lead developers

Congratulations fellow developers! You have received well deserved promotions, and I am glad to see your names in the kicad-product-committers group. Keep on rocking! Cheers, Orson On 03/01/2018 08:15 PM, Wayne Stambaugh wrote: > I am pleased to announce the promotion of three developers to the

Re: [Kicad-developers] [PATCH] Avoid shadowed variable

Thank you Simon, I have just merged your patch. Cheers, Orson On 02/28/2018 09:50 AM, Simon Richter wrote: > --- > pcbnew/dialogs/dialog_plot.cpp | 1 - > 1 file changed, 1 deletion(-) > > > > ___ > Mailing list:

Re: [Kicad-developers] [PATCH] Various GerbView fixes

For the record: merged. On 02/28/2018 03:33 AM, Jon Evans wrote: > Hi all, > > Attached are three patches to fix a few issues noted by JP and Clemens. > These need to be applied after my patches from yesterday which are not yet > merged. > > Best, > Jon > > > >

Re: [Kicad-developers] [PATCH] GerbView performance: in-place layer reordering for X2 sorting

For the record: merged. On 02/27/2018 03:15 AM, Jon Evans wrote: > Hi all, > > A few more GerbView patches for tonight. > > The larger one should get some testing if possible before merging -- last > time I tried something like this, JP said it killed performance on Windows. > On my Linux

  1   2   3   4   5   6   7   8   9   >