Re: [Kicad-developers] eeschema regression

Hi Oliver- I've had similar issues. If you can, would you mind testing the attached patch on Windows? It offloads the library processing to a thread that runs when the schematic loads or the library table changes. It isn't ready for merge consideration yet because I'm not convinced that the

[Kicad-developers] eeschema regression

I think that there has been a functional regression in a recent build, relating to placing symbols in eeschema. Previously, the libraries were loaded once when the schematic was opened. now, the entire symbol library set is re-loaded every time you select "Place Symbol". This brings up the

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

Holy crap this is dope. I wanted to do something along similar lines a long time ago, but I've never had nearly enough time for it. I would use this stuff SO much. I love that you demoed it on the project I REALLY wish it existed for :D On Thu, Dec 14, 2017 at 04:15:34AM +, Jon Evans wrote:

Re: [Kicad-developers] [PATCH] Wire-bus entry dangling points

Interesting, when I added this feature a couple years ago I explicitly made it display the ends in this case to indicate an "error". I had no idea it was intended that bus entries be used in this way. I wish we could come up with a redesign of the bus entries that isn't visually ambiguous with

Re: [Kicad-developers] macOS 3d-viewer improvements

Bernhard, Your patch set fails to build on Linux (Debian testing) with the following build errors: In file included from /home/wayne/src/kicad/kicad-trunk/common/gal/hidpi_gl_canvas.cpp:27:0: /home/wayne/src/kicad/kicad-trunk/include/gal/hidpi_gl_canvas.h:45:22: error: ‘wxGLAttributes’ does not

Re: [Kicad-developers] [PATCH] Add double-click handling to disambiguation menu

Seth, I was thinking about Seth's macos opengl touch tapping patch but I now realize that your patch is only relevant to the legacy canvas. In any event, I merged your patch. Keep up the great work! Thanks, Wayne On 12/15/2017 12:34 PM, Seth Hillbrand wrote: > Wayne- > > Just one.  They are

[Kicad-developers] [PATCH] Wire-bus entry dangling points

The attached patch adjusts how dangling ends are shown for wire-bus entries to correct the behavior Nick reported. Previously, wire-bus entries were shown as dangling if there was a wire or a bus at both ends. This broke in the case of the Coldfire demo where a bus was drawn over a wire and

Re: [Kicad-developers] P-Cad patch

Are any questions? В Четверг, 14 дек. 2017 в 9:38 П. П., Eldar Khayrullin написал: Link to my previous mail https://lists.launchpad.net/kicad-developers/msg32410.html В Четверг, 14 дек. 2017 в 9:00 П. П., Maciej Suminski написал: Thank you

Re: [Kicad-developers] [PATCH] Add double-click handling to disambiguation menu

Wayne- Just one. They are both the same patch (I resent one for Jeff). It should be ready for merging, provided no one has objections. -S On Fri, Dec 15, 2017 at 9:27 AM, Wayne Stambaugh wrote: > I'm I safe in assuming that both of these patches are ready to be merged

Re: [Kicad-developers] [PATCH] Add double-click handling to disambiguation menu

I'm I safe in assuming that both of these patches are ready to be merged or is more testing required? On 12/15/2017 12:19 PM, Jeff Young wrote: > Hi Seth, > > Yep, works fine for tap and double-tap on OSX. > > Cheers, > Jeff. > >> On 15 Dec 2017, at 16:29, Seth Hillbrand

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

Le 15/12/2017 à 18:16, Andy Peters a écrit : > >> On Dec 13, 2017, at 9:15 PM, Jon Evans wrote: >> >> Hi all, >> >> As some of you know, I've been working on some new features for Eeschema >> that expand the capabilities of buses. >> These features are not yet complete, but

Re: [Kicad-developers] [PATCH] Add double-click handling to disambiguation menu

Hi Seth, Yep, works fine for tap and double-tap on OSX. Cheers, Jeff. > On 15 Dec 2017, at 16:29, Seth Hillbrand wrote: > > Hi Jeff- > > Here is the patch from the original e-mail. > > Best- > Seth > > On Fri, Dec 15, 2017 at 3:35 AM, Jeff Young

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

Yes, buses can travel through hierarchy just like nets -- hierarchical sheet pins and ports can carry buses or nets, no need for a new type of label. In my branch I am currently changing the color of hierarchical ports/pins that connect buses (to the same color as bus wires) -Jon On Fri, Dec 15,

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

> On Dec 13, 2017, at 9:15 PM, Jon Evans wrote: > > Hi all, > > As some of you know, I've been working on some new features for Eeschema that > expand the capabilities of buses. > These features are not yet complete, but I wanted to share my progress to get > early

Re: [Kicad-developers] [PATCH] Correct bus junction behavior

It doesn't but I'll see about fixing that separately. I don't think that's a recent issue. I checked back 1yr and see the same thing, so I think that issue has been around since ed0f17e (2015). Let me know if you've seen it working correctly more recently. -S On Fri, Dec 15, 2017 at 4:28 AM,

Re: [Kicad-developers] New records with zone filling.

Hi And NEXT! I am going to improve pcbnew connectivity. I am just tired that waiting in big boards when routed or dragged. Especially when tracks are added full off my new track features (teardrops, t-junctions, fillet junctions and rounded track corners). Old algorithm just worked quite fine.

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

Hi Kevin, Are you thinking about when someone is editing the schematic later in eeschema, or when someone exports to a PDF or prints it? Both concerns have been raised and I think are valid. I like the idea of some kind of mouseover info, or showing the contents in the message panel (that one is

Re: [Kicad-developers] [PATCH] Add double-click handling to disambiguation menu

Hi Jeff- Here is the patch from the original e-mail. Best- Seth On Fri, Dec 15, 2017 at 3:35 AM, Jeff Young wrote: > Where can I find the patch (it wasn’t linked to either bug report > mentioned)? > > I want to make sure it doesn’t break trackpad double-tapping. > > Speaking

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

On 2017-12-13 11:15 PM, Jon Evans wrote: As some of you know, I've been working on some new features for Eeschema that expand the capabilities of buses. [snip] https://youtu.be/z6x0xiKgDIc Those are some interesting changes to working with buses. There is one documentation type problem I

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

Jon, I finally had time to watch your video. The new bus connection work looks great! Hopefully I'll be able to find some time in the not too distant future to take a look at the code. I'm really interested in the new real time connection algorithm. Keep up the great work. Cheers, Wayne On

Re: [Kicad-developers] [PATCH] Fix quotes in UI messages

Hi, >> This replaces all single and angle bracket quotes in UI messages with >> double quotes, for consistency. >> Sorry to all translators. > I merged your patch. If anyone feels like helping the translators out here: there are a number of translations that are now "fuzzy" because the

Re: [Kicad-developers] [PATCH] Fix quotes in UI messages

Simon, I merged your patch. Thanks, Wayne On 12/15/2017 6:37 AM, Simon Richter wrote: > > This replaces all single and angle bracket quotes in UI messages with > double quotes, for consistency. > > Sorry to all translators. > --- > bitmap2component/bitmap2cmp_gui.cpp| 8

Re: [Kicad-developers] for improving doc reports

On Fri, Dec 15, 2017 at 12:40:06PM +0100, Nick Østergaard wrote: > See inline comments. > > 2017-12-15 12:27 GMT+01:00 Marco Ciampa : > > > Hello devs! > > I would like to ask for a favour to improve the reports for errors in the > > docs. > > > > Since we have some CI engines

Re: [Kicad-developers] [PATCH] Correct bus junction behavior

I don't have the possibility to test this patch right now, but does it affect the way bus entries are managed? See the the IRQ- bus on the pins 87, 88, 89, 90, 91, 94 in the coldfire demo. Since recently the bus entries are rendered as not connected in both ends. 2017-12-15 0:24 GMT+01:00 Seth

Re: [Kicad-developers] Some thoughts on symbol remapping

On 12/14/2017 7:46 PM, Oliver Walters wrote: > I noticed that your symbol library table uses absolute paths rather than > using the SYMBOL_LIB_DIR path expansion.  This should not make any > difference as long as the path you used is the same path as old library > list look up

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

Hmm okay, we seem to differ in opinions once again. But you are right, nothing stops me from naming my aliases like that anyway. I have checked schematics for students, and I know that I  would be very confused if the aliases they have used did not immediatly pop up for me somehow. Be it

Re: [Kicad-developers] for improving doc reports

See inline comments. 2017-12-15 12:27 GMT+01:00 Marco Ciampa : > Hello devs! > I would like to ask for a favour to improve the reports for errors in the > docs. > > Since we have some CI engines in place for checking for correctness of > the doc source, I am here to ask for a

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

Le 15/12/2017 à 12:28, Jeff Young a écrit : > Yeah, definitely stay away from anything non-ASCII in the syntax, but the > narrower ellipsis character should be fine for display…. ... but not in plot files, as pdf files have a searchable text. Because Kicad is a internationalized tool, we avoid

Re: [Kicad-developers] [PATCH] Add double-click handling to disambiguation menu

Where can I find the patch (it wasn’t linked to either bug report mentioned)? I want to make sure it doesn’t break trackpad double-tapping. Speaking of which, tapping in general is broken in GAL (see https://bugs.launchpad.net/kicad/+bug/1737010). I submitted a patch with that bug; any chance

[Kicad-developers] for improving doc reports

Hello devs! I would like to ask for a favour to improve the reports for errors in the docs. Since we have some CI engines in place for checking for correctness of the doc source, I am here to ask for a little improvement. in http://docs.kicad-pcb.org/ now there is: - all the 4.0.X version of

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

Yeah, definitely stay away from anything non-ASCII in the syntax, but the narrower ellipsis character should be fine for display…. > On 15 Dec 2017, at 10:54, Marco Ciampa wrote: > > On Fri, Dec 15, 2017 at 11:38:00AM +0100, Clemens Koller wrote: >> On 2017-12-15 11:01,

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

On Fri, Dec 15, 2017 at 11:38:00AM +0100, Clemens Koller wrote: > On 2017-12-15 11:01, Marco Ciampa wrote: > > On Fri, Dec 15, 2017 at 10:54:01AM +0100, Clemens Koller wrote: > > > >> I was also considering the ellipsis '...' but in classical ASCII, they > >> are three characters wide, that's why

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

On 2017-12-15 11:01, Marco Ciampa wrote: > On Fri, Dec 15, 2017 at 10:54:01AM +0100, Clemens Koller wrote: > >> I was also considering the ellipsis '...' but in classical ASCII, they >> are three characters wide, that's why I ended up with .., + or * to keep >> it short. > > ... and the problem

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

On Fri, Dec 15, 2017 at 10:54:01AM +0100, Clemens Koller wrote: > I was also considering the ellipsis '...' but in classical ASCII, they > are three characters wide, that's why I ended up with .., + or * to keep > it short. ... and the problem with 3 chars is? > But since we arrived in Unicode,

Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

Hello! On 2017-12-14 14:08, Marco Ciampa wrote: >> But when you add aliases I run into troubles to keep things separate/clear: >> {RAM} appears to me as an unnamed bus containing the net RAM. WTF is that? >> MEMORY{RAM} appears as a bus named MEMORY containing the single net RAM. >> I would