[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #4159

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

[Kicad-developers] UTF-8 change please test on Windows/Mac

Hi All- Our UTF-8 routines are mildly fragile and didn't play nicely with higher-order unicode sequences [1] causing a segfault for anything larger than 16-bits. I've pushed a fix that changes how wchar_t* characters are assigned to the UTF8 class. This is a band-aid fix as it doesn't address

Re: [Kicad-developers] [PATCH] Add preferences dialog hotkey

Am Di., 16. Okt. 2018 um 15:37 Uhr schrieb hauptmech : > > This highlights the need for platform specific hotkey config files on > install rather than relying on a single hard coded default. Nothing says > cross-platform amateur hour more than having the software not be integrated > with your

Re: [Kicad-developers] [PATCH] Add preferences dialog hotkey

This highlights the need for platform specific hotkey config files on install rather than relying on a single hard coded default. Nothing says cross-platform amateur hour more than having the software not be integrated with your platform at all. On 17/10/2018 11:00 AM, John Beard wrote:

Re: [Kicad-developers] Edit text and graphic properties behavior

Hi Simon, I think one of the original justifications of dyn_cast<> was that it was faster. Do I have that wrong, or do we not believe it to be material? (Other than that I’d love to get rid of it. It’s bitten me more than once.) Cheers, Jeff. > On 16 Oct 2018, at 17:38, Simon Richter

Re: [Kicad-developers] [PATCH] Add preferences dialog hotkey

Hi, I'd suggest perhaps Ctrl-Shift-P, which is used by Inkscape. P with various modifiers is fairly common shortcut for preferences: https://defkey.com/search?irq=Preferences I feel like Ctrl-, might be useful as paired hotkey with Ctrl-. (eg increase/decrease)? Cheers, John On 16 October

Re: [Kicad-developers] PART_DRAW_OPTIONS redundancy?

Hi Simon, Looks correct to me. Drawing visible fields and hidden fields are independently controllable, so one’s not just the inverse of the other. Cheers, Jeff. > On 16 Oct 2018, at 19:53, Simon Richter wrote: > > Hi, > > eeschema/class_libentry.cpp, line 414ff: > >if(

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Thanks, Mark. I’ve merged a fix. Cheers, Jeff. > On 16 Oct 2018, at 21:07, mdoes...@xs4all.nl wrote: > > Found another bug. When importing sheet pins, the pin can be placed and > is visible during placement. Once placed it is no-longer visible. When I > quit eeschema and start it with the

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Found another bug. When importing sheet pins, the pin can be placed and is visible during placement. Once placed it is no-longer visible. When I quit eeschema and start it with the same file, the sheet label is visible and right where I left it. regards, Mark.

[Kicad-developers] PART_DRAW_OPTIONS redundancy?

Hi, eeschema/class_libentry.cpp, line 414ff: if( field.IsVisible() && !aOpts.draw_visible_fields ) continue; if( !field.IsVisible() && !aOpts.draw_hidden_fields ) continue; Is this art, or can it be removed? Simon

Re: [Kicad-developers] Edit text and graphic properties behavior

Hi, On 10/16/2018 06:19 PM, Wayne Stambaugh wrote: >> The “Footprint graphic items” bug was a dyn_cast when a dynamic_cast was >> needed (dyn_cast doesn’t handle inheritance). > Do you want me to file a bug report on this or are you going to fix it > right away? I have a patch that eliminates

Re: [Kicad-developers] Edit text and graphic properties behavior

It just occurred to me that it doesn’t need to be exclusive: we can update a user-field with text “%V" when either Other footprint fields or Footprint values is chosen. > On 16 Oct 2018, at 17:31, Wayne Stambaugh wrote: > > Hey Jeff, > > Awesome! Thanks for the quick fix. > > Cheers, > >

Re: [Kicad-developers] Edit text and graphic properties behavior

Seems reasonable to me. On 10/16/2018 12:45 PM, Jeff Young wrote: > It just occurred to me that it doesn’t need to be exclusive: we can > update a user-field with text “%V" when /either/ Other footprint > fields /or/ Footprint values is chosen. > > >> On 16 Oct 2018, at 17:31, Wayne Stambaugh >

Re: [Kicad-developers] Edit text and graphic properties behavior

Hey Jeff, Awesome! Thanks for the quick fix. Cheers, Wayne On 10/16/2018 12:30 PM, Jeff Young wrote: > Hi Wayne, > > Already fixed. > > Cheers, > Jeff. > > >> On 16 Oct 2018, at 17:19, Wayne Stambaugh wrote: >> >> Jeff, >> >> On 10/16/2018 12:06 PM, Jeff Young wrote: >>> The “Footprint

Re: [Kicad-developers] Edit text and graphic properties behavior

Hi Wayne, Already fixed. Cheers, Jeff. > On 16 Oct 2018, at 17:19, Wayne Stambaugh wrote: > > Jeff, > > On 10/16/2018 12:06 PM, Jeff Young wrote: >> The “Footprint graphic items” bug was a dyn_cast when a dynamic_cast was >> needed (dyn_cast doesn’t handle inheritance). > > Do you want me

[Kicad-developers] Edit text and graphic properties behavior

I'm not sure I using this correctly so before I file a bug report against it, I have some questions about the edit text and graphic properties behavior in pcbnew. When changing footprint text sizes using the set to layer default values option, the fields on silkscreen layers are updated as

Re: [Kicad-developers] Edit text and graphic properties behavior

Jeff, On 10/16/2018 12:06 PM, Jeff Young wrote: > The “Footprint graphic items” bug was a dyn_cast when a dynamic_cast was > needed (dyn_cast doesn’t handle inheritance). Do you want me to file a bug report on this or are you going to fix it right away? > > I can’t reproduce the “Other

Re: [Kicad-developers] Edit text and graphic properties behavior

The “Footprint graphic items” bug was a dyn_cast when a dynamic_cast was needed (dyn_cast doesn’t handle inheritance). I can’t reproduce the “Other footprint fields” on fab layers problem. Cheers, Jeff. As an aside, would you expect a footprint field with the text %R to get updated with

Re: [Kicad-developers] Edit text and graphic properties behavior

Hi Wayne, Set to Layer Defaults should set the fields on the fab layer to the values in the “Other Layers” row. Similarly, Set to Layer Defaults of footprint graphic items should set the silkscreen layer graphic items to the values in the “Silk Layers” row. I’ll see if it’s working in a

Re: [Kicad-developers] 5.0.1 release status.

Hello. I found the next bug #1798124 Исходное сообщение От: Wayne Stambaugh Дата: 16.10.18 16:49 (GMT+03:00) Кому: kicad-developers@lists.launchpad.net Тема: Re: [Kicad-developers] 5.0.1 release status. Hi Jean-Samuel, It looks like you will have cherry pick commit

Re: [Kicad-developers] Zone selection

On Tue, Oct 16, 2018, 3:43 AM Jeff Young wrote: > While I’m a big fan of the new zone selection stuff, I did run into quite > a bit of trouble with it over the weekend while working on a board with a > ground-plane. I did notice that every time I *actually* wanted to edit > the zone I set zone

Re: [Kicad-developers] Zone selection

Good call. -S On Tue, Oct 16, 2018, 3:43 AM Jeff Young wrote: > While I’m a big fan of the new zone selection stuff, I did run into quite > a bit of trouble with it over the weekend while working on a board with a > ground-plane. I did notice that every time I *actually* wanted to edit > the

Re: [Kicad-developers] [PATCH] Fuzzable PCB parsing test harness

Hi Wayne, I think I might have fixed the ordering in the link libraries (at least, it now builds on Jenkins). This is just the first patch to focus on the build error, I'll rebase the other docs stuff later if/when it works. Cheers, John On Fri, Oct 12, 2018 at 7:58 PM Wayne Stambaugh wrote:

Re: [Kicad-developers] 5.0.1 release status.

Hi Jean-Samuel, It looks like you will have cherry pick commit 9a3cfb857 from the development branch to build on any version of Ubuntu that uses boost prior to version 1.59. I've attached a copy of the patch so you do not have to cherry pick it yourself. I think I was the responsible for

Re: [Kicad-developers] 5.0.1 release status.

Hi Wayne, Yes the bug #1785377 affect also this release. Did I need to plan a workarround to allow this build ? Regards, Le 15/10/2018 à 23:37, John Beard a écrit : > Hi Wayne, > > There was a commit on master made for this purpose: 9a3cfb857. The > function is to remove a failing test and

Re: [Kicad-developers] Missing zone segments

ti 16. lokak. 2018 klo 12.39 Jeff Young (j...@rokeby.ie) kirjoitti: > Note that we could also free up space by going to the new Net Selector. > It’s filter is less powerful than the one in the Zone Settings dialog, but > is it powerful enough? (To be honest I’ve never used the filtering options

[Kicad-developers] Zone selection

While I’m a big fan of the new zone selection stuff, I did run into quite a bit of trouble with it over the weekend while working on a board with a ground-plane. I did notice that every time I actually wanted to edit the zone I set zone display to filled, while the rest of the time I had it

Re: [Kicad-developers] Missing zone segments

Hi Seth, I think that’s two different questions. The old method had the segment count per-zone, as it was highly dependant on the radius of the fillet (or the radius of any board edge the zone ran in to). The new method doesn’t have to deal with that — it solely controls speed vs.