Re: [Kicad-developers] Ctrl-click to highlight in pcbnew missing?

Ctrl-click was made consistent with Pcbnew (and platform standards) for toggle selection. ` is now hooked up to highlight net. Cheers, Jeff. > On 10 Sep 2019, at 13:30, Tomasz Wlostowski wrote: > > Hi, > > Am I missing something or did Ctrl-click to highlight a net suddenly > stopped

Re: [Kicad-developers] Failing tests

Should be fixed now…. > On 10 Sep 2019, at 10:19, Simon Richter wrote: > > Hi, > > we have three new test failures[1] (same test, with different internal units): > > - Common.library.module.tests.Segment > > [Error] - check SegCollideCorrect( c.m_seg_a, c.m_seg_b, c.m_clearance, >

Re: [Kicad-developers] Allowable character set for symbols and footprints

Hi Evan, The code prohibits the following in filenames: \/:"<>| Note that the prohibited list does not include spaces. (In theory all the escaping bugs are now fixed.) Netnames (and therefore pin names and labels) don’t have filename constraints, so you can in theory use anything that’s not

Re: [Kicad-developers] Selection highlighting changes.

parently looks correct on Mac but is very >>> washed out under GTK3. I've added a conditional for the defaults that >>> sets GTK/MSW values to the ones that seem appropriate on GTK3. We may >>> want an additional default value for MSW if it similarly appears off. >>>

Re: [Kicad-developers] knowing last commit included in a nightly build?

Yeah, it would be -really- nice if we could fix this somehow. I’ve run into it many times. Cheers, Jeff. > On 5 Sep 2019, at 14:07, Jonatan Liljedahl wrote: > > On Thu, Sep 5, 2019 at 1:59 PM Nick Østergaard wrote: >> >> Does the sha listed in the version info from the runtime app not

Re: [Kicad-developers] Selection highlighting changes.

The colour is in Preferences now; see if it’s just too washed out on your monitor. > On 4 Sep 2019, at 22:35, Seth Hillbrand wrote: > > I'm working on one (slowly) but it hasn't been pushed. GTK3 in the master > branch looks normal for me. > > Does it look the same in OpenGL and Cairo? > >

Re: [Kicad-developers] Selection Highlighting

@Seth, can you post a video or some screen-shots? Cairo and a Retina display are pretty much a non-starter. Cheers, Jeff. > On 1 Sep 2019, at 17:13, Eeli Kaikkonen wrote: > > For everone's information - there was user discussion in the forum: >

Re: [Kicad-developers] Multiple delete in dialog_spice_model.cpp

Yeah, the guys that wrote the standard template library could have won awards in obfuscation. > On 30 Aug 2019, at 21:17, Seth Hillbrand wrote: > > On 2019-08-30 15:49, Sylwester Kocjan wrote: > >>m_schfields->erase( std::remove_if( >> m_schfields->begin(), m_schfields->end(),

Re: [Kicad-developers] Opinions on eeschema selection highlighting?

Looks good, Seth. I’m going to lighten the default a bit so that the text is easier to read. (The OSX default is a very light blue so I didn’t notice that the other platforms use a darker blue.) Cheers, Jeff. > On 27 Aug 2019, at 18:49, Seth Hillbrand wrote: > > On 2019-08-23 13

[Kicad-developers] Opinions on eeschema selection highlighting?

While I wasn’t too happy with it at first, the new selection highlighting has really grown on me. How do others feel about it? ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] [Patch] Clean up switch statement in pcbnew launcher

Hi Ian, I merged your patch. Thanks for your contribution! Cheers, Jeff. > On 14 Aug 2019, at 00:30, Ian McInerney wrote: > > The switch statement for choosing which frame to launch in Pcbnew had an > extra nested switch inside of it. It appears that the original performance > enhancement

Re: [Kicad-developers] [Patch] Unify close menu item creation for non-main windows

Hi Ian, I merged your patch. Thanks for your contribution! Cheers, Jeff. > On 14 Aug 2019, at 00:40, Ian McInerney wrote: > > Right now the addition of the Close item for the non-main windows is > scattered in the menu creation functions. This means it is easy to leave out > the

Re: [Kicad-developers] [RFC] Switch from SyncToolbars to wxUpdateUIEvent

er reason to do this for the ACTION_MENUs, so then we have a definite > class demarcation between a context menu and a normal menu. The context menu > would still inherit from the normal menu, but it would include the ability to > hide the items. > > -Ian > > On Tue, Au

Re: [Kicad-developers] [RFC] Switch from SyncToolbars to wxUpdateUIEvent

wxWidgets), so we will always need to handle that > ourselves and the Evaluate() command seems to be doing a decent job of it. > > -Ian > > On Mon, Aug 12, 2019 at 10:19 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: > Hi Ian, > > It sounds promising, but there ar

Re: [Kicad-developers] [RFC] Switch from SyncToolbars to wxUpdateUIEvent

Hi Ian, It sounds promising, but there are some potential pitfalls. wxWidgets only supports two bits: enabled and checked. CONDITIONAL_MENU supports 2-1/2: the enabled flag means visible if the is_context_menu flag is set. This is probably a subtlety that does us no good: it would be more

Re: [Kicad-developers] OSX: About menu option location

App menu. Cheers, Jeff. > On 10 Aug 2019, at 22:01, Ian McInerney wrote: > > Quick question: on Mac OS where is the About menu item showing up? Is it in > the app menu or in the help menu? > > I am trying to decipher some wxWidgets menu moving code, and they are less > than clear as to

[Kicad-developers] Folks doing their own Mac builds will want to fetch from our local wxWidgets branch...

… and rebuild wxWidgets. Cheers, Jeff. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Possible MSW-only fix for print bug

MSW and GTK? OSX is still on 3.0.4 (we have our own wxWidgets branch with a bunch of fixes in it). How hard was it to move to 3.1? > On 9 Aug 2019, at 13:26, Simon Richter wrote: > > Hi Jeff, > > On Fri, Aug 09, 2019 at 11:36:44AM +0100, Jeff Young wrote: > >> I’

[Kicad-developers] Possible MSW-only fix for print bug

I’ve merged a possible fix for https://bugs.launchpad.net/kicad/+bug/1464773, but it will only work on MSW until wxWidgets 3.1.1. Of course that means I can’t test it. Can someone give it a whirl and see if it works? Thanks, Jeff. ___ Mailing list:

Re: [Kicad-developers] Coding style question

When I worked at Frame a colleague advised me not to create Framegol. (That was back in the day when Pascal and C were considered Algol family languages.) I’ve always taken that to heart and so prefer std::shared_ptr, ugly as it is. Cheers, Jeff. > On 7 Aug 2019, at 23:18, Tomasz Wlostowski

Re: [Kicad-developers] GAL layer question

Yes, that’s another option. Eeschema doesn’t currently hide selected objects and create clones in the preview, but it could. Cheers, Jeff. > On 7 Aug 2019, at 23:15, Tomasz Wlostowski wrote: > > On 07/08/2019 19:45, Jeff Young wrote: >> Hi Orson, >> >> I w

Re: [Kicad-developers] GAL layer question

Hi Tom, I don’t know a thing about them but it’s probably time I bone up on this whole OpenGL thing anyway, so I’ll look into it. Cheers, Jeff. > On 7 Aug 2019, at 19:17, Tomasz Wlostowski wrote: > > On 07/08/2019 19:45, Jeff Young wrote: >> Hi Orson, >> >> I w

Re: [Kicad-developers] Anyone know where the sources to the simulation cursors are?

; Hi Jeff, > > I am afraid I have lost them in a hard drive crash. I should have > committed them to the repository, my bad. I have an idea how to quickly > convert them back to the original version. Are you still interested in > the sources? > > Cheers, > Orson > &

Re: [Kicad-developers] GAL layer question

the cached framebuffer might be reused for many frames when only > non-cached items are updated, but the drawback is that one cannot > interleave the rendering order. > > Is there a particular problem you are trying to solve? Perhaps it can be > implemented in another way. > &g

Re: [Kicad-developers] How to make single-plane .cpp from .png?

script — it’s easy enough to just copy/paste the text from the XBM file. Cheers, Jeff. > On 6 Aug 2019, at 11:39, Seth Hillbrand wrote: > > On 2019-08-05 15:22, Jeff Young wrote: >> Our PNG2cpp.cmake script makes a 3 or 4 plane (ie: colour) char array. >> wxWidgets’ w

Re: [Kicad-developers] [Patch] Move pcbnew layer toolbar icon values to member struct

Hi Ian, I’ve merged your patch. Thanks! Cheers, Jeff. > On 5 Aug 2019, at 09:13, Ian McInerney wrote: > > Here is an updated version of this patch that goes with the constexpr color > definitions instead of the initialize-on-first-use. > > -Ian > > On Mon, Aug 5, 2019 at 12:20 PM Ian

Re: [Kicad-developers] [Patch] Return event handled flag from dispatchHotkey

Hi Ian, I’ve merged your patch. Thanks! Cheers, Jeff. > On 5 Aug 2019, at 14:03, Ian McInerney wrote: > > This patch modifies the event dispatch in the tool manager to return whether > a hotkey has been handled with an action (instead of just returning true if > an action with the hotkey

Re: [Kicad-developers] How to make single-plane .cpp from .png?

some pretty ugly cursors. I think we’ll have to specify them as bitmaps. > On 5 Aug 2019, at 15:25, Jeff Young wrote: > > I also tried online converters for PNG -> XBM and directly from the source > (SVG -> XBM), but they all give me black images…. > > >> On 5

Re: [Kicad-developers] How to make single-plane .cpp from .png?

I also tried online converters for PNG -> XBM and directly from the source (SVG -> XBM), but they all give me black images…. > On 5 Aug 2019, at 15:15, Jeff Young wrote: > > I found doc on the colour modes; 0 is monochrome without alpha, 2 is RGB, 4 > is monochrome with a

Re: [Kicad-developers] How to make single-plane .cpp from .png?

I found doc on the colour modes; 0 is monochrome without alpha, 2 is RGB, 4 is monochrome with alpha and 6 is RGBA. So -c 0 should be correct. But it appears wxBitmap is expecting XBM data rather than PNG data. Hm….. > On 5 Aug 2019, at 14:46, Jeff Young wrote: > > pngcrush -

Re: [Kicad-developers] How to make single-plane .cpp from .png?

pngcrush -c 0 makes a single-plane char array, but it appears to be in a different order or something (the array is the right size, but produces a garbage cursor). Anyone know what the other colour modes are? (0, 2, 4, 6) > On 5 Aug 2019, at 13:22, Jeff Young wrote: > > Our PNG2

[Kicad-developers] How to make single-plane .cpp from .png?

Our PNG2cpp.cmake script makes a 3 or 4 plane (ie: colour) char array. wxWidgets’ wxBitmap() constructor needs a single plane char array. John Beard created a couple for the SPICE cursors, but I’m not sure how he did it. Thanks, Jeff. ___ Mailing

[Kicad-developers] Anyone know where the sources to the simulation cursors are?

___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Tool processing & RunHotKey return

ted key problem. This > >> doesn't seem like a good solution to the problem though, because it > >> causes more issues with other keys as well (for instance, if nothing is > >> assigned to shift+A, then it just runs the hotkey for A instead). > >

[Kicad-developers] GAL layer question

How do I interleave a GAL non-cached layer with cached layers? The selection shadow is currently non-cached, but because of that is always drawn behind device fills. Is there a way to put it between LAYER_DEVICE and LAYER_DEVICE_BACKGROUND (both of which are cached in OpenGL)?

Re: [Kicad-developers] 5.1.3 release

The release candidates would be a good idea if we think anyone would test them. The failure mode would be if all those willing to take the risk were only willing to take it in order to see the next major version (ie: were running the master nightlies). Another option would be to only

Re: [Kicad-developers] Eeschema selection

Hi Dino, I’m torn on having a colour config for it. On the one hand it might help some users who want to set a different colour, but on the other hand it won’t track any system mode changes (such as dark mode on OSX). The zoom level compensation was put in specifically to make things look

Re: [Kicad-developers] [Patch] Log traces for tool dispatch

Hi Ian, I merged your change. Thanks for your contribution! Cheers, Jeff. > On 31 Jul 2019, at 10:27, Ian McInerney wrote: > > Here is an updated patch. A recent commit made it not apply as cleanly as it > should (and this also adds a trace for the search minus the shift). > > -Ian > >

Re: [Kicad-developers] Eeschema selection

Hi JP, I’ve pushed another version which uses the platform selection colour (blue on OSX). Let me know how that looks on your machine. Cheers, Jeff. > On 30 Jul 2019, at 12:04, jp charras wrote: > > Le 30/07/2019 à 05:01, Jeff Young a écrit : >> Hi Nhat, >> >>

Re: [Kicad-developers] Eeschema selection

> can be many items under. > > On Mon, Jul 29, 2019 at 2:01 AM Jeff Young <mailto:j...@rokeby.ie>> wrote: > OK, I tried a bunch of things out. None of them were terribly satisfactory. > > Bolding sounded good, but turned out to be even less noticeable than the > brighteni

Re: [Kicad-developers] Eeschema selection

ld come up with (and it’s not great) is a “drop shadow” made with the item’s hue and a fixed saturation and lightness. Cheers, Jeff. > On 25 Jul 2019, at 23:11, Jeff Young wrote: > > Oh, hey, I like the bold idea. Did you try it out? (I can if not….) > >> On 25 Jul 2019, at

Re: [Kicad-developers] Tool processing & RunHotKey return

706.html PS: while I now know my way around it to a certain extent, I’m no expert on the event dispatching stuff. So healthy pinches of salt may be in order... > On 28 Jul 2019, at 06:27, jp charras wrote: > > Le 28/07/2019 à 02:22, Jeff Young a écrit : >> I think JP ran into t

Re: [Kicad-developers] Tool processing & RunHotKey return

I think JP ran into this earlier, so he might know more about it. Another issue might be that at the end of the tool loop the event will get skipped which will send it to wxWidgets for processing (at which point it will probably come back as a hotkey again). We might already have logic to deal

Re: [Kicad-developers] PCBNew Find and "match words"

t; Cheers, > > Wayne > > On 7/26/19 3:41 PM, Jeff Young wrote: >> I went with something similar to Seth’s proposal, only based on Eeschema’s >> find (so no regular expressions yet). >> >> Most of the workings are down in EDA_ITEM, so if we add regex matching we

Re: [Kicad-developers] PCBNew Find and "match words"

ote: > > On 2019-07-26 14:39, Jeff Young wrote: >> PCBNew’s current Find does a match against the whole string. I think >> it would be more intuitive with a ‘*’ in front and back of the search >> string (so that it finds partial matc

[Kicad-developers] PCBNew Find and "match words"

PCBNew’s current Find does a match against the whole string. I think it would be more intuitive with a ‘*’ in front and back of the search string (so that it finds partial matches). Any other opinions? ___ Mailing list:

[Kicad-developers] Chapter 53 in the glorious tale of wxWidgets event handling

There’s a bug that you can’t change layers while routing. Turns out it’s really that you can’t execute most hotkeys found on ed keys while running a tool. The problem is that wxEVT_CHAR_HOOK doesn’t do the key translation properly. wxEVT_CHAR does, but we only get to that if we skip the

Re: [Kicad-developers] 5.1.3 tagged

A “free” or “stitching” via (ie: one not connected to tracks), or one in the middle of a track? I don’t believe dragging of free vias ever worked (although it is fixed in 6.0). > On 26 Jul 2019, at 03:41, Dino Ghilardi wrote: > > On version tagged 5.1.3 I'm unable to drag vias with the "D"

Re: [Kicad-developers] Eeschema selection

Oh, hey, I like the bold idea. Did you try it out? (I can if not….) > On 25 Jul 2019, at 21:02, Seth Hillbrand wrote: > > On 2019-07-19 19:03, Jeff Young wrote: > >> I’ve been thinking of using the magenta colour for both net >> highlighting and cross-probing, and t

Re: [Kicad-developers] hotkeys behaviour changed recently?

03:15, Tomasz Wlostowski wrote: > > On 24/07/2019 19:28, Jeff Young wrote: >> Hi Tom, >> >> I’ll implement the preference if you’ll review my latest via push-n-shove >> stuff. ;) >> > Hi Jeff, > > Sure - do you mean the stitching via pushing

Re: [Kicad-developers] hotkeys behaviour changed recently?

Hi Wayne, I could make another run at it, but the first two implementations that didn’t work out were based on twin actions. I then gave up on them. Cheers, Jeff. > On 25 Jul 2019, at 07:32, Wayne Stambaugh wrote: > > On 7/25/19 5:15 AM, Tomasz Wlostowski wrote: >> On 24/07/2

Re: [Kicad-developers] hotkeys behaviour changed recently?

enable tool behavior is > implemented, everyone will be happy ;) > > On 7/24/2019 12:39 PM, Jeff Young wrote: >> Oh god, the feature from hell. It took me so many iterations to get the >> immediate mode to work that the preference fell off the radar. >> >> &g

Re: [Kicad-developers] hotkeys behaviour changed recently?

Oh god, the feature from hell. It took me so many iterations to get the immediate mode to work that the preference fell off the radar. > On 24 Jul 2019, at 09:04, Tomasz Wlostowski wrote: > > Hi Devs, > > I built today's master and to my surprise, pressing 'X' in pcbnew starts > immediately

Re: [Kicad-developers] fp-info-cache question

Hi Kevin, No this is just a cache of footprint library properties so that we can index and search footprints without loading them all into memory. It’s entirely for performance. Cheers, Jeff. > On 23 Jul 2019, at 15:35, Kevin Cozens wrote: > > On 2019-07-23 11:47 a.m., Seth Hillbrand

Re: [Kicad-developers] fp-info-cache question

n 2019-07-23 13:38, jp charras wrote: >>> Le 23/07/2019 à 19:22, Jeff Young a écrit : >>>> Hi Seth, >>>> >>>> I think that would work. And you’re right — there probably aren’t >>>> enough project libs to require a cache for them.

Re: [Kicad-developers] fp-info-cache question

Could we write the global cache in the user's config directory next to where > we write fp-lib-table? > > If we cache global, we might not need project-based caching. > > -Seth > > On 2019-07-23 11:39, Jeff Young wrote: >> Hi Rene, >> Separate global and local cache

Re: [Kicad-developers] fp-info-cache question

Hi Rene, Separate global and local caches would certainly be a refinement. It’s not free, though, as platforms differ on where an appropriate place to write a global cache is. And the code has to be able to combine the two (that might be easy or it might not — it’s been too long since I’ve

Re: [Kicad-developers] fp-info-cache question

Hi Seth, Just performance. IIRC MSW was the real laggard, but even my Mac was more like 7 seconds to 2. Cheers, Jeff. > On 22 Jul 2019, at 17:03, Seth Hillbrand wrote: > > Hi Folks, > > Odd question here but why do we have fp-info-cache? Was there a bug report > for these or just speed

Re: [Kicad-developers] MOD_VIRTUAL flag

> On 2019-07-22 15:10, Jeff Young wrote: >> I was thinking we’d handle it under: >> https://bugs.launchpad.net/kicad/+bug/980919 >>> On 22 Jul 2019, at 12:53, Seth Hillbrand wrote: >>> Hi Jeff and JP- >>> Should we consider a new flag for boar

Re: [Kicad-developers] MOD_VIRTUAL flag

mean "don't move > without warning" and don't delete automatically (as part of [1]) > > Best- > Seth > > [1] https://bugs.launchpad.net/kicad/+bug/1745627 > > On 2019-07-22 10:27, Jeff Young wrote: >> And just to add one more (which was the instance that prompted

Re: [Kicad-developers] MOD_VIRTUAL flag

sign that as a 3D shape to a > connector or a mounting hole of board 2. -very useful to check for mechanical > collisions-). > > Cheers, > Dino. > > > > ----- > On 22/07/19 09:02, jp charras wrote: >>

[Kicad-developers] MOD_VIRTUAL flag

This flag tells us that there’s no physical object for a pick-n-place machine. But is it also true that there’s no corresponding symbol in the schematic, or are there some virtual footprints that would have a symbol? What about some microwave elements, for instance? Do they have symbols?

Re: [Kicad-developers] [PATCH] Board statistics dialog

ee59f0c285cbe990cb7464e6f1da > > <https://github.com/jasuramme/kicad-source-mirror/commit/9d6061d5df63ee59f0c285cbe990cb7464e6f1da> > > Среда, 17 июля 2019, 23:56 +03:00 от Jeff Young : > > Hi Alex, > > I’m about to go on vacation myself so I’ll be on a plane all day tomorrow, >

Re: [Kicad-developers] Message Dialogs

+1 > On 20 Jul 2019, at 03:19, Ian McInerney wrote: > > There has been a brief discussion in this bug > (https://bugs.launchpad.net/kicad/+bug/1836498 > ) about removing the bold text > from the save dialogs, and instead having all the text as

[Kicad-developers] Eeschema selection

Brightening the selection in Pcbnew works well because the background is dark and most of the colours are reasonably dark, so there’s a good bit of room to make the difference between selected and not selected noticeable. This is less true in Eeschema, mainly because of the white background.

Re: [Kicad-developers] [PATCH] Board statistics dialog

om/jasuramme/kicad-source-mirror/commit/6ce77c20ff479f2fa4f1af9ba4e8d7f93d2ee1e5> > > > And patch in the attachment below. > > Best regards, > Alex > > Среда, 17 июля 2019, 15:18 +03:00 от Jeff Young : > > Hi Alex, > > No need for apologies. It’s a st

[Kicad-developers] Hotkeys show twice or none...

Hi JP, In commit 6388189f4837447fbf3aa71513f498ae387455ca you removed the page calls to TransferDataToWindow() to keep from getting duplicate hotkeys. Was that for GTK? If so, I’d guess that GTK calls TransferDataTowindow() recursively for child windows while MSW and OSX do not. (In any

Re: [Kicad-developers] [PATCH] Board statistics dialog

ON_CONDITIONS::ShowAlways ); > +inspectMenu->AddItem( PCB_ACTIONS::boardStatistics, > SELECTION_CONDITIONS::ShowAlways ); > > > > But I would leave whitespaces, for better code looking as all functions > around use it > > > > Понедельник, 8 июля 2019, 17:0

Re: [Kicad-developers] Rounded rectangles

Hi Seth, That change was intentional. The worry is that we could be sending our zone performance to hell without noticing. By making the default CHOP_ACUTE_CORNERS we can fix things that should be rounded, and other things will be performant. However, I can see that it does sort of depend on

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

/content.arduino.cc/assets/DUE-reference.zip > > On 2019-07-16 08:16, Jeff Young wrote: >> Hi Seth, >> I’m not seeing the same behaviour. Could you send me the Eagle file >> you were using for that screen-shot? >> Thanks, >> Jeff. >>> On 16 Ju

Re: [Kicad-developers] Build errors on linux

Ahh, cool. I assume gcc 6 is still new enough to support C++14? Cheers, Jeff. > On 16 Jul 2019, at 15:20, Simon Richter wrote: > > Hi Jeff, > > On Tue, Jul 16, 2019 at 03:13:43PM +0100, Jeff Young wrote: > >> Wow. I thought gcc was a “real” compiler. ;) > >

Re: [Kicad-developers] Build errors on linux

Wow. I thought gcc was a “real” compiler. ;) Change pushed. It’ll probably fix it, but then lldb handled it fine to start with so I can’t be sure. Cheers, Jeff. > On 16 Jul 2019, at 14:57, Dino Ghilardi wrote: > > I see that too (linux - Debian 9.9), same error got from line 455. > > I

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

Hi Seth, I’m not seeing the same behaviour. Could you send me the Eagle file you were using for that screen-shot? Thanks, Jeff. > On 16 Jul 2019, at 12:47, Jeff Young wrote: > > Actually, something fishy is going on with the MiterLimit. It should be > round

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

Actually, something fishy is going on with the MiterLimit. It should be rounding the fill, but not the outline (even in strategy (a))…. > On 16 Jul 2019, at 10:12, Jeff Young wrote: > > We need to go to strategy (b) to fix that (use the zone’s fillet radius to > round the corners

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

See the attached image. This corner is square in Eagle. It > can be very difficult to edit zones with a bunch of extra points, so I'd like > to avoid this if possible. > > Best- > Seth > > On 2019-07-15 06:04, Jeff Young wrote: >> Oh, good. Not sure how I mis

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

> using the edge of their line, which is curved to 1/2 the width. > > Best- > Seth > > [1] > https://git.launchpad.net/kicad/commit/?id=490c805319974ec84a8fbe8b10e9b59b9a3922a6 > > On 2019-07-14 16:13, Jeff Young wrote: >> Hi Seth, >> I’m still not follow

Re: [Kicad-developers] Reason for non-stroked zones?

9 à 22:14, Jeff Young a écrit : >> Hi JP, >> >> Why were the non-stroked zones implemented? Is it entirely for performance? >> >> Is the plan to make them default in 6.0? >> >> Thanks, >> Jeff. > > It is mainly to fix an issue for very la

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

which controls that. > On 14 Jul 2019, at 21:13, Jeff Young wrote: > > Hi Seth, > > I’m still not following this. When Eagle strokes the boundary, it does so > with a round pen (at least going by the pngs in the bug report). So all > corners have a radius of 1/2 the s

[Kicad-developers] Reason for non-stroked zones?

Hi JP, Why were the non-stroked zones implemented? Is it entirely for performance? Is the plan to make them default in 6.0? Thanks, Jeff. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

rted zones will no longer be correct. > > -Seth > > On 2019-07-14 14:22, Jeff Young wrote: >> Hi Seth, >> I looked at that bug report, and all the Eagle zones have rounded >> corners, not square. So I don’t think you were actually getting >> anything out of the

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

t think we were using that type of inflation anywhere else > (but that could have changed). If we are using that elsewhere, can you > verify that the change to clipper doesn't re-introduce > https://bugs.launchpad.net/kicad/+bug/1817312 ? > > Thanks- > Seth > > On 20

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

stroke). Cheers, Jeff. > On 14 Jul 2019, at 17:50, Seth Hillbrand wrote: > > On 2019-07-14 05:31, Jeff Young wrote: >> I made another optimisation, this time within the Clipper library. >> When the offset exceeds the MiterLimit it will perform jtRound instead >> of jtSq

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

are fixed in the new one and it’s faster). > On 13 Jul 2019, at 23:05, Jeff Young wrote: > > I found a bug in our interface to the Clipper lib, so the extra plotter > smoothing isn’t needed. (We were passing in delta as the MiterLimit, but > Clipper is expecting a scaling to apply

[Kicad-developers] Status of length-matching bug?

Hi Tom, It looks like you fixed: https://bugs.launchpad.net/kicad/+bug/1541070 but it was never closed. Did the fix get committed? Cheers, Jeff.___ Mailing list: https://launchpad.net/~kicad-developers

Re: [Kicad-developers] What's the state of the zone outline thickness stuff?

Jul 2019, at 01:21, Jeff Young wrote: > > I have a fix for adjacent zone fillet suppression, but it requires the newer > zero-width-stroked outlines. Are we going to be turning those on, or is it > only for people with performance problems? >

[Kicad-developers] What's the state of the zone outline thickness stuff?

I have a fix for adjacent zone fillet suppression, but it requires the newer zero-width-stroked outlines. Are we going to be turning those on, or is it only for people with performance problems? Cheers, Jeff. ___ Mailing list:

Re: [Kicad-developers] wxWidgets Event Tables or Bind and lambdas

r down the path. > > > I definitely agree some guidance on lambda formatting is in order, and also > some guidance about how to format them if they are inside a function call > (like the example above). > > -Ian > > On Fri, Jul 12, 2019 at 12:28 PM Jeff Young <mail

Re: [Kicad-developers] wxWidgets Event Tables or Bind and lambdas

We already have a lot of classes which use both. FWIW, the wxWidgets folks encourage Bind. As for lamdas, I think they’re pretty rare (for this use) in the code at present. But they do appear to result in a higher signal-to-noise ratio for very short handlers. While we’re on the subject, we

Re: [Kicad-developers] Arc Adjustment proposal

If you’re going to do everything in DXF, why have drawing tools at all? (And by corollary, if you’re going to have drawing tools then make them suitable for the task at hand.) Cheers, Jeff. > On 11 Jul 2019, at 17:16, easyw wrote: > > > On 07/11/2019 5:17 PM, Jeff Young wrot

Re: [Kicad-developers] Arc Adjustment proposal

Here’s a footprint I drew recently which was made much harder by Kicad’s focus on arc centre points: > On 11 Jul 2019, at 15:46, Eeli Kaikkonen wrote: > > > > to 11. heinäk. 2019 klo 15.43 easyw (ea...@katamail.com > ) kirjoitti: > > On 07/11/2019 1:21 PM,

Re: [Kicad-developers] Arc Adjustment proposal

Hi Eeli, Have you tried the new arc editing in the Symbol Editor? I think it’s much easier to use, and I think that’s the direction Seth is going for Pcbnew/FootprintEditor. Cheers, Jeff. > On 10 Jul 2019, at 21:52, Eeli Kaikkonen wrote: > > ke 10. heinäk. 2019 klo 20.26 Seth Hillbrand

Re: [Kicad-developers] Arc Adjustment proposal

+1 to start, end and +0 to whatever ... is. > On 10 Jul 2019, at 18:37, Larry Doolittle wrote: > > Jon - > > On Wed, Jul 10, 2019 at 01:29:11PM -0400, Jon Evans wrote: >> I am curious why start-midpoint-end is better than start-center-end, though. >> I think the latter is used more often

Re: [Kicad-developers] Compilation problems with types from pcb_lexer.h

Note that you can also cd include, and do a rm *_lexer.h. (Make sure you get the underscore in there as there’s also a “dsnlexer.h” that you don’t want to delete.) > On 10 Jul 2019, at 11:00, Andrew Lutsenko wrote: > > See https://lists.launchpad.net/kicad-developers/msg41433.html >

Re: [Kicad-developers] common/tool/tool_dispatcher needs fixing.

I’ve pushed some code (and put my fire-suit on). Cheers, Jeff. > On 9 Jul 2019, at 21:10, Jeff Young wrote: > > Hmm… now I know why it doesn’t indicate handled for other stuff: it’s > difficult to get that information back from the coroutine. But I think a bug > fix

Re: [Kicad-developers] common/tool/tool_dispatcher needs fixing.

Hmm… now I know why it doesn’t indicate handled for other stuff: it’s difficult to get that information back from the coroutine. But I think a bug fix I made earlier for the PassEvent stuff may give us a proxy for “handled”. > On 9 Jul 2019, at 21:07, Jeff Young wrote: > &

Re: [Kicad-developers] common/tool/tool_dispatcher needs fixing.

Hi JP, This code definitely seems to have evolved a bit over time. ProcessEvent() specifically returns true only if it was a hotkey that was handled, and not for anything else. But I can’t find any code that benefits from that, so I suspect it’s vestigial. I think the best thing to do is to

Re: [Kicad-developers] Compil issue due to commit 36f1d023

Oops, those were supposed to be tool IDs. I’ve pushed another commit. Let me know if it still doesn’t compile (the LLDB compiler is much more aggressive about auto-type-casting). > On 9 Jul 2019, at 16:44, jp charras wrote: > > This commit creates 2 similar issues: > the first issue is: > >

Re: [Kicad-developers] Strange program version numbering in KiCad

My brain can visually parse 5.99. I have to actually read the current tags and think about them before I can figure out what they represent. > On 8 Jul 2019, at 21:47, Nick Østergaard wrote: > > How is a number like 99 being any better than the latest release tag? > > On Mon, 8 Jul 2019 at

Re: [Kicad-developers] Strange program version numbering in KiCad

I find the current scheme confusing. I like the 5.99 idea…. Cheers, Jeff. > On 8 Jul 2019, at 20:03, Wayne Stambaugh wrote: > > On 7/8/19 2:58 PM, Kevin Cozens wrote: >> On 2019-07-08 2:38 p.m., Nick ??stergaard wrote: >>> @Kevin, And the version is not just the tag and number of commits,

Re: [Kicad-developers] Zone min-width isn't

just that > we should allow the spokes to be the same width as the minimum width. > > Jeff, is that correct? > > -Seth > > On 2019-07-08 09:40, Jeff Young wrote: >> We enforce minimum width by deflating the zone by 1/2-min-width, >> simplifying the po

<    1   2   3   4   5   6   7   8   9   10   >