Re: [Kicad-developers] Unlock text orientation flag for Reference/Value

Re-sending (I somehow hit reply instead of reply-all the first time ‘round). > On 16 Dec 2017, at 13:17, Jeff Young <j...@rokeby.ie> wrote: > > A global unlock text flag would be better. > > For something like audio gear with a right and left channel, you sometimes > wa

Re: [Kicad-developers] [PATCH] add helper to selecting graphic grid. Add 40 mils grid (approx. 1mm) to draw graphic items in mm

I’d rather have fewer app-defined grids and more user-defined ones. (Then you could do this on your own.) Cheers, Jeff. > On 16 Dec 2017, at 12:57, Eldar Khayrullin wrote: > > Are any opinions? > > В Суббота, 18 ноя. 2017 в 2:47 П. П., Eldar Khayrullin >

Re: [Kicad-developers] Getting patches committed

Hi Maciej, Thanks for the workaround for the progress dialog on OSX. The attached patch is a similar workaround but preserves more of the progress window functionality. Please have a look and let me know what you think. BTW, I’ve also noticed that the DRC window ends up behind the document

Re: [Kicad-developers] OSX progress dialog patch

I see Tomasz submitted a more platform-neutral version of this patch (which I’ve tested on OSX), so this one can now be ignored. (I’ve marked the bug as a duplicate.) Cheers, Jeff. > On 13 Dec 2017, at 15:54, Jeff Young <j...@rokeby.ie> wrote: > > <0001-A-different-wor

[Kicad-developers] DRC: two tracks end too close together

Every once and a while I’ll get a “two tracks end too close together” DRC error when the two segments in question are part of a single track. Wiggling the track (with a 45º drag) usually fixes the problem. Known issue, or should I log a bug? ___

[Kicad-developers] OSX progress dialog patch

(Resending with correct subject line.) > On 12 Dec 2017, at 22:53, Jeff Young <j...@rokeby.ie> wrote: > > Hi Maciej, > > Thanks for the workaround for the progress dialog on OSX. The attached patch > is a similar workaround but preserves more of the progress window

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

“Bus Group” sounds like a group of busses, rather than a bus composed of groups. People doing a layout might also be thinking in graphical terms when they see “Vector” (ie: the direction the bus goes in or something), rather than in mathematical notation terms. Can we just call everything a

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] [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

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 <seth.hillbr...@gmail.com> wrote: > > Hi Jeff- > > Here is the patch from the original e-mail. > > Best- > Seth > > On Fri, Dec 15, 2017 at

Re: [Kicad-developers] OSX progress dialog patch

0001-A-different-workaround-to-the-OSX-progress-dialog-is.patch Description: Binary data On 13 Dec 2017, at 15:00, Nick Østergaard <oe.n...@gmail.com> wrote:I don't see a patch attached to the forwarded email.2017-12-13 14:40 GMT+01:00 Jeff Young <j...@rokeby.ie>:(Resending with cor

[Kicad-developers] Code style question

#ifdef’s: indented with code, or hard to the left margin? (I’ve seen both styles in the code….) Thanks, Jeff. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] EESchema: regression in object moving?

build. Not only does it now build cleanly, but the bug is gone as well…. Cheers, Jeff. > On 17 Dec 2017, at 22:00, Jeff Young <j...@rokeby.ie> wrote: > > Has anyone noticed that dragging an object in EESchema doesn’t erase the old > images (it just smears the canvas each time

[Kicad-developers] EESchema: regression in object moving?

Has anyone noticed that dragging an object in EESchema doesn’t erase the old images (it just smears the canvas each time its redrawn during the drag operation)? ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

[Kicad-developers] Getting patches committed

Hi guys and gals, I’ve logged a few bugs that affect me and developed fixes for some of them[1]. After decades of svn and then a few years of retirement I don’t trust my git skills so I added the fixes as patches. What’s the process for getting them reviewed and committed? Thanks, Jeff.

[Kicad-developers] RegEx help

We have a couple of regular expressions of the form: wxRegEx re( ".*?\\$\\{(.+?)\\}.*?", wxRE_ADVANCED ); Now perhaps I’m too old to remember this stuff correctly, but .*? is redundant, isn’t it? And shouldn’t .+? just be .*? (And for that matter, shouldn’t it really be [^}]*?) Thanks,

[Kicad-developers] Recent dialog layout changes

Hi Wayne, I noticed you checked in some changes to fix dialog layout on Windows. The degree symbol was explained well enough in the comments, but for future reference what is the exact change required regarding the standard-dialog-button padding? Is it just adding a 5px margin to the

Re: [Kicad-developers] Recent dialog layout changes

wxFormbuilder is different enough to cause the entire > file to be replaced. > > Hopefully this answers your questions. > > Cheers, > > Wayne > > On 5/10/2018 7:22 AM, Jeff Young wrote: >> Hi Wayne, >> >> I noticed you checked in some chang

Re: [Kicad-developers] Recent dialog layout changes

Oh, and yes the diff issue was line-endings. I tried CLion’s visual diff tool and it worked fine. > On 10 May 2018, at 14:09, Jeff Young <j...@rokeby.ie> wrote: > > Thanks, Wayne. > > The Mac version has a lot of padding around the individual buttons in the > stan

Re: [Kicad-developers] Proposed Geographic PCB Re-Annotation for Kicad 6

Hi Brian, Re-annotation is usually done in Kicad from Eeschema rather than Pcbnew. The current annotation dialog supports two ordering mechanisms: "by x position" and "by y position". If I understand what you’ve done correctly it could be added as a third option “rules based sorting” (or

Re: [Kicad-developers] Proposed Geographic PCB Re-Annotation for Kicad 6

ated references back to the schematic from > the board editor. It's not a trivial change. > > Cheers, > > Wayne > > On 5/10/2018 1:54 PM, Jeff Young wrote: >> Hi Brian, >> >> Re-annotation is usually done in Kicad from Eeschema rather than Pcbnew. >>

Re: [Kicad-developers] Why do component location values not respect the grid origin?

So there’s no way to change the coordinates origin? (Even for display/editing purposes?) > On 13 May 2018, at 11:51, jp charras <jp.char...@wanadoo.fr> wrote: > > Le 13/05/2018 à 12:48, Jeff Young a écrit : >> For instance, if I have a component at (5,4) and I c

Re: [Kicad-developers] Why do component location values not respect the grid origin?

But that only helps for dragging, not typing in values, right? > On 13 May 2018, at 12:21, jp charras <jp.char...@wanadoo.fr> wrote: > > Le 13/05/2018 à 13:03, Jeff Young a écrit : >> So there’s no way to change the coordinates origin? (Even for >> display/editing pu

[Kicad-developers] Why do component location values not respect the grid origin?

For instance, if I have a component at (5,4) and I change the grid origin to (2,2) then I expect the component location to now be (3,2). But it’s still (5,4). Is there a reason for this? cf: https://bugs.launchpad.net/kicad/+bug/1770897 ___ Mailing

Re: [Kicad-developers] [PATCH] Add python apis: GetLogicalLibs, FootprintsInLib and FootprintInfo

Hi Miles, The only coding style issue I saw was that there should be blank lines above “if” statements. Oh, and there’s still a K brace. Search for "if ( footprint ) {“. (The brace should be down on its own line.) I didn’t correct these and merge your patch as I can’t get scripting to build

Re: [Kicad-developers] [RFC]: New non copper pad paste and mask clearances behavior V2

applied or not, and only the copper layers have "net pad clearance". > Anyways, the current text leads one to think that "net pad clearance" would > be used for non-copper pads. > > > Eeli Kaikkonen > > > 2018-05-06 1:38 GMT+03:00 Jeff Young <j...@rok

Re: [Kicad-developers] [RFC]: New non copper pad paste and mask clearances behavior V2

only check clearance between two items on the same copper layer, but that’s subtly different than “not on any copper layer”. Perhaps too subtle? > On 5 May 2018, at 20:19, Eeli Kaikkonen <eeli.kaikko...@gmail.com> wrote: > > > > 2018-05-03 23:39 GMT+03:00 Jeff Young <j..

Re: [Kicad-developers] RegEx help

p://docs.wxwidgets.org/3.0/overview_resyntax.html#overview_resyntax_matching>). > > There seems to be difference greedy vs non-greedy quantifiers! > > > Thanks, > Shiv > > > > On Sat, May 5, 2018 at 6:49 PM, Jeff Young <j...@rokeby.ie > <mailto:j...@r

Re: [Kicad-developers] RegEx help

sly pasted. That one means make the zero-or-one > quantifier non-greedy. > > On 5/5/2018 5:58 PM, Jeff Young wrote: >> Ahhh… I’m mixing up XPath and RegEx syntax. ‘?’ is zero-or-one in XPath, >> not RegEx. >> >> Thanks Shiv & Thomas. >> >> Ch

Re: [Kicad-developers] Another dialog preview

I should mention one caveat: there’s a lot of preferences-specific code for getting/setting the various properties (they’re not all tied directly to wxConfigBase items), which means the panel implementations depend on application-specific code. When the preferences dialog is opened it

[Kicad-developers] Length tuning hotkeys

The length tuning hotkeys (L for settings, 1 - 4 for increase/decrease spacing/amplitude) don’t work for me because the events are eaten by the status popup. I suspect this is an OSX-specific issue, but I just wanted to check before making the fix OSX-only. Steps: Create a diff pair. Route ->

Re: [Kicad-developers] FreeRouting

I think that would be great. It would certainly cut down on the number of bugs we get against it. But I must confess to not being party to most of the history of it…. > On 21 May 2018, at 17:09, Seth Hillbrand wrote: > > ​Hi Wayne- > > In

Re: [Kicad-developers] Window build error.

s and what > they were so I could go back an fix any broken 3D model definitions. > > On 5/21/2018 9:41 AM, Jeff Young wrote: >> Perhaps we should just change tracePathsAndFiles to a #define for now? >> >> >>> On 21 May 2018, at 14:09, Wayne Stambaugh <st

Re: [Kicad-developers] Window build error.

Perhaps we should just change tracePathsAndFiles to a #define for now? > On 21 May 2018, at 14:09, Wayne Stambaugh wrote: > > I'm getting the following link error on windows builds after commit > 10ec39a1. I looks like kicad2step is not being linked to the static >

Re: [Kicad-developers] Initial rc6 development.

+1. If we do a 5.1 (and I think we should), file format changes would be a better metric for ancillary additions. This is of course self-serving: I have a bunch of great dialog changes that could go in. ;) Cheers, Jeff. > On 21 May 2018, at 00:55, Seth Hillbrand

Re: [Kicad-developers] Call for Translators?

One of the reasons we left the Language menu in the main menus (instead of moving it to a dialog along with Icons in Menus, etc.) is for people using partly-translated versions where they may have to switch back and forth a lot. So I’d also tend to lean toward the “give them what we have” side

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

I think I like this new patch. It provides the /opportunity/ for uniformity, without getting in the way of those who want to go their own way. Do the BOM generators automatically output all default fields or only those with values? > On 22 May 2018, at 09:22, kristoffer ödmark

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

> It should output all fields defined in schematic symbols regardless if > each optional field is defined in every symbol. If they are outputting > anything other than that, I would consider this a bug. I had trouble parsing this. Are you saying that the list of output fields should be the

Re: [Kicad-developers] Unconnected vs unrouted

il.com> wrote: > > > ​Hi Jeff- > > I believe that this distinction has been removed for V5 with the new > connectivity algorithm (Tom, please correct me if I'm mistaken in this!) > > -S​ > > > Am So., 29. Apr. 2018 um 02:19 Uhr schrieb Jeff Young

Re: [Kicad-developers] Symbol field editor dialog improvements

Hi Ben, You probably saw my comments in the bug that 0002 has already been addressed. Could you change the opening and closing braces to be on their own line in 0001? (The rest matches our coding standard so I assume you found it, but if not:

[Kicad-developers] Name change in 6.0 pad properties

I’ve always found the name “Net pad clearance” odd in the pad properties dialog. I’m proposing to change it to “Copper clearance” to better match “Solder mask clearance” and “Solder paste clearance”. (As a side note I’m also changing “Thermal relief width” to “Thermal relief spoke width”, but

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

d does not enforce anything and comes in at a whooping >> 3-4 lines of patch in a single file. It will however add 3 lines to two >> dialogs (field editor and symbol editor) for new installations, which >> can be removed, with 6 clicks of the mouse in eeschema. >> >>

Re: [Kicad-developers] Name change in 6.0 pad properties

I think "Pad clearance" is even better. > On 23 May 2018, at 13:03, Wayne Stambaugh <stambau...@gmail.com> wrote: > > On 5/23/2018 5:36 AM, Jeff Young wrote: >> I’ve always found the name “Net pad clearance” odd in the pad properties >> dialog. >>

Re: [Kicad-developers] Symbol field editor dialog improvements

t code, or do you want me to change the existing algorithm? Cheers, Jeff. > On 24 May 2018, at 14:55, Ben Gamari <b...@smart-cactus.org> wrote: > > Jeff Young <j...@rokeby.ie> writes: > >> Hi Ben, >> >> You probably saw my comments in the bug that

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

You may want to test this just to be sure. We had a similar issue with > translating board layer names in the old board file format which created > a big headache when we implemented the current board file format. > > On 5/23/2018 4:43 AM, Jeff Young wrote: >> Reference/Value/F

Re: [Kicad-developers] Symbol field editor dialog improvements

Hi Ben, Here’s a thought: when you did a git format-patch did you specify —attach origin/master? > On 24 May 2018, at 16:02, Ben Gamari <b...@smart-cactus.org> wrote: > > Jeff Young <j...@rokeby.ie> writes: > >>> Hmm, I had used git format-patch. Is there s

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

Hi Orson, The problem should become less prevalent over time: for 6.0 I plan on fixing the multi-sheet undo issues so that we can update all units in unison. (Of course that still fails if you edit before annotating as we then don’t know which units go with which.) But I agree that anytime

Re: [Kicad-developers] Initial rc6 development.

I still think we should do the full canvas + toolset for 6.0… … or are we thinking we might port just the canvas change back to 5.0.1? >> … >> So my question is: >> It is possible to use the GAL itself (restricted to the graphic layer), and >> keep the current >> wxWidget management events in

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

don’t currently translate default fields. > On 22 May 2018, at 17:53, Wayne Stambaugh <stambau...@gmail.com> wrote: > > On 5/22/2018 12:43 PM, Jeff Young wrote: >>> It should output all fields defined in schematic symbols regardless if >>> each optional

Re: [Kicad-developers] A quick re-introduction

Welcome, Alexis. (Re-welcome?) Anyway, l look forward to you getting some more Kicad cycles in. Cheers, Jeff. > On 22 May 2018, at 17:15, Chris Pavlina wrote: > > Hi, > > Just thought I'd finally get around to getting this out since I'm en > route to Digi-Key to

Re: [Kicad-developers] Name change in 6.0 pad properties

Essentially pad to copper (which is where the original suggestion came from). Specifically pad to zone, pad to pad, pad to track, pad to via, and pad to text on copper layer. > On 23 May 2018, at 17:58, Clemens Koller <c...@embeon.de> wrote: > > On 2018-05-23 14:25, Jeff Yo

Re: [Kicad-developers] [ISSUE] shortcut not detected with DRC (filled zones case)

Click on that section of the Cu.B zone and select Properties. I’ll suspect you’ll find that it is not connected to any Vin nets and has therefore been connected to GND. If you manually set it to Vin it should disconnect from GND (but then you’ll probably get at least a warning about it being

Re: [Kicad-developers] [PATCH]fix library cache issue

Looks good, Damien. I’ve pushed it to master. Thanks for your contribution! Cheers, Jeff. > On 9 Jun 2018, at 09:21, Damien Espitallier > wrote: > > I have made another try. > > This time as the library timestamp is always use as library identifier, I add > it with hash of the library

Re: [Kicad-developers] [PATCH]fix library cache issue

Hi Damien, wxString pointer’s operator== does a string compare, so you don’t need to convert m_library from a wxString pointer to a wxString. The conversion is somewhat more expensive as it also copies the string. Probably not really an issue here, but I’d still rather see the minimal change

[Kicad-developers] Hotkeys issues

In a fresh build when launching PCBNew I get an assert about duplicate hotkeys definitions. I’ve also noticed some on the canvas; for instance when I do an ‘E’ over a footprint I get the Router Settings dialog rather than the Footprint Properties. Is this just my machine? Cheers, Jeff.

Re: [Kicad-developers] Hotkeys issues

It appears there is already a bug logged for it: https://bugs.launchpad.net/kicad/+bug/1776785 <https://bugs.launchpad.net/kicad/+bug/1776785> > On 14 Jun 2018, at 09:37, Jeff Young wrote: > > In a fresh build when launching PCBNew I get an assert about duplicate > h

Re: [Kicad-developers] Hotkeys issues

, > > It seems, that those duplicate hotkeys are in pcbnew/tools/drawing_tool.cpp > file. > > Heikki > > > > On Thu, Jun 14, 2018 at 12:16 PM, Jeff Young <mailto:j...@rokeby.ie>> wrote: > It appears there is already a bug logged for it: > > https://bu

Re: [Kicad-developers] eeschema GAL renderer (with old tools)

Awesome! > On 28 May 2018, at 22:43, Tomasz Wlostowski wrote: > > Hi all, > > This is to inform that I'm working on it (as the XOR-based rendering > doesn't work under GTK3). I wrote a hacked GAL canvas which uses the > legacy eeschema tool code. It's non-functional yet (editing-wise), but >

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

, it will fix the “silent” side-effect as a bonus. Then anything we do in 6.0 can be considered new features. > On 29 May 2018, at 20:55, Wayne Stambaugh wrote: > > On 5/29/2018 3:16 PM, Jeff Young wrote: >> And one more idea: “Default Field Names” would also be a reasonable thing to &g

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

a feature change to fix. > > [1]: https://git.launchpad.net/kicad/tree/eeschema/plugins/python_scripts > > On 5/29/2018 10:12 AM, Jeff Young wrote: >> Hi Reece, >> >> Was that generated with a recent build? Earlier versions of 5.0 >> certainly had that bug

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

named that earlier the translation keys might already be in the dictionaries. > On 29 May 2018, at 19:38, Jeff Young wrote: > > We really must choose a model. What we have is broken under either model. > > If they’re “default” fields, then they need to be there by default. That’s &g

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

And one more idea: “Default Field Names” would also be a reasonable thing to call these (so it’s clear that the /name/ is a default, not the /field/). > On 29 May 2018, at 19:56, Jeff Young wrote: > > Another way to fix the side-effect issue: > > 1) Go with the seed field mod

[Kicad-developers] Recent change to LayerIDs

Hi Seth, Your recent change to the assert in ToLAYER_ID() is going to cause issues. Was there some failure we weren’t catching? The reason we need it to be less restrictive is because the PCB background was put into the GAL range but is actually a board layer. I suppose we could check

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

We currently expose this in both Kicad and Modedit, but it’s not really what it says it is as newly created pads use the last set properties, not the default properties. It is used by Copy / Apply Pad Settings, but that’s a bit odd too as one would expect those to go through the clipboard.

Re: [Kicad-developers] [PATCH] Large board speed

Since you say it doesn’t impact DRC I assume you mean the status bar unconnected count rather than the DRC unconnected count. FWIW, we recently renamed the status bar on “unrouted” because it’s already known to be less accurate than the DRC unconnected count (even before any of Seth’s

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

> > Thanks! This is exactly what i was going for, non-intrusive >> > > oppurtunity >> > > for uniformity! >> > > >> > > I tested the bom2csv plugin, It did not include the empty fields. >> > > >> > > I also tested the bom_csv_s

Re: [Kicad-developers] Board settings in project file

15:20, jp charras wrote: > > Le 03/06/2018 à 15:40, Jeff Young a écrit : >> We store some of the board settings (such as line widths, text sizes, etc.) >> in the project file. >> >> Except that creating a new project, or a new board, doesn’t appear to use >&g

[Kicad-developers] Another problem with the generic (XML) netlist exporter

We currently export library components the same way we store them (ie: just the root, with a list of aliases). We do not output the alias descriptions, documentation links or footprint filters. The missing documentation links are OK since these are copied to the datasheet fields of the

[Kicad-developers] Board settings in project file

We store some of the board settings (such as line widths, text sizes, etc.) in the project file. Except that creating a new project, or a new board, doesn’t appear to use them (falling back to default values instead). The only way I can get them updated is via Preferences > Save Project

Re: [Kicad-developers] Another problem with the generic (XML) netlist exporter

Forgot the bug reference: https://bugs.launchpad.net/bugs/1774358 <https://bugs.launchpad.net/bugs/1774358> > On 3 Jun 2018, at 18:08, Jeff Young wrote: > > That when folks produce a BOM including descriptions all aliased parts have > the wrong descriptions. > > (I

Re: [Kicad-developers] Another problem with the generic (XML) netlist exporter

Another option would be to amend the element in the : > On 3 Jun 2018, at 21:52, Jeff Young wrote: > > Hi JP, > > What are you considering the “description” in that? > > Here’s what I’m seeing (interesting bits highlighted in red): > > > ECC83 >

Re: [Kicad-developers] Another problem with the generic (XML) netlist exporter

> Le 03/06/2018 à 18:10, Jeff Young a écrit : >> We currently export library components the same way we store them (ie: just >> the root, with a list of aliases). >> >> We do not output the alias descriptions, documentation links or footprint >> filters. The m

Re: [Kicad-developers] Another problem with the generic (XML) netlist exporter

eads the (single) description. > On 3 Jun 2018, at 19:12, jp charras wrote: > > Le 03/06/2018 à 19:08, Jeff Young a écrit : >> That when folks produce a BOM including descriptions all aliased parts have >> the wrong descriptions. > > Are you sure? Have you tested

Re: [Kicad-developers] Another problem with the generic (XML) netlist exporter

Well, the BOM generators we ship with the product output the (other) description field as well. I’ll go with the less-invasive approach of adding an attribute to the element. Cheers, Jeff. > On 4 Jun 2018, at 11:56, jp charras wrote: > > Le 03/06/2018 à 22:52, Jeff Young a écrit :

Re: [Kicad-developers] [PATCH] Fix crash on footprint filter tab

Thanks for your contribution to Kicad, Damien! (It actually counted double. I at first misunderstood your report and found another bug deleting something else with nothing selected.) I’ll merge your patch momentarily…. Cheers, Jeff. > On 5 Jun 2018, at 22:40, Damien Espitallier > wrote: >

Re: [Kicad-developers] Update Field Values feature

Hi Reid, Bug, I’m afraid. I’ve logged it as https://bugs.launchpad.net/kicad/+bug/1778826 . Cheers, Jeff. > On 26 Jun 2018, at 15:50, Reid Landsrud wrote: > > The Update Field Values feature may have some unintended behavior. > > When using

[Kicad-developers] Requesting feedback regarding "Update Footprints" menu item

See https://forum.kicad.info/t/issue-updating-footprint-in-v5/10536/5 .___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net

Re: [Kicad-developers] KiCad failing to build on linux.

My bad. I accidentally reverted a file doing my checkin. Fixing now…. > On 1 May 2018, at 21:56, Wayne Stambaugh wrote: > > I'm seeing this build error: > > /home/wayne/src/kicad-trunk/common/footprint_info.cpp: In static member > function ‘static FOOTPRINT_LIST*

[Kicad-developers] Layers widget font scaling

If your screen reports a height of 900 pixels or less we scale the system-default fontsize for PCB_EDIT_FRAME (but not FOOTPRINT_EDIT_FRAME). This results in poor readability on at least some MSW systems (https://bugs.launchpad.net/kicad/+bug/1767965) and for those with ageing eyesight (i.e.

Re: [Kicad-developers] Layers widget font scaling

yne Stambaugh <stambau...@gmail.com> wrote: > > On 5/2/2018 8:11 AM, jp charras wrote: >> Le 02/05/2018 à 11:03, Jeff Young a écrit : >>> If your screen reports a height of 900 pixels or less we scale the >>> system-default fontsize for PCB_EDIT_FRAME (but not FOOTP

Re: [Kicad-developers] Requesting feedback regarding "Update Footprints" menu item

library" and "change > footprint". This seems clear to me but then again, I'm not new to board > layout software so maybe this is just a rookie mistake. > > Cheers, > > Wayne > > On 5/1/2018 5:14 PM, Jeff Young wrote: &

Re: [Kicad-developers] [RFC]: New non copper pad paste and mask clearances behavior (was: What are the smallest values for pad paste and mask clearances)

Personally I think this is one of those times to be pragmatic. Yes, the patch changes the interpretation of existing files (which in principle is a bad thing), but we’re willing to live with it in this case. I don’t have much of an opinion on the exact algorithm we should use. Cheers, Jeff.

Re: [Kicad-developers] [PATCH] At very first launch, old settings/config does not exist

I downloaded this patch and did a “git am patch_name” and got: Patch format detection failed. However, a “git patch patch_name” work fine, and I’ve used “git am” before with success. (I also had this problem earlier with a bunch of Simon's patches, so it’s unlikely it’s specific to this

Re: [Kicad-developers] [PATCH] At very first launch, old settings/config does not exist

k to see if the > first line of the commit comment is the subject of the email and not in > the body. > > Cheers, > > Wayne > > On 5/1/2018 9:08 AM, Jeff Young wrote: >> I downloaded this patch and did a “git am patch_name” and got: >> >>Patch format det

Re: [Kicad-developers] [PATCH] Adjust Menubar of 3D Viewer to common style

I like removing them. I always found it odd that they were in a menu structure. > On 3 May 2018, at 15:58, Wayne Stambaugh wrote: > > Hi Thomas, > > The first patch is fine. Removing all of the settings from the > preferences menu that are in the configuration options

Re: [Kicad-developers] [RFC]: New non copper pad paste and mask clearances behavior V2

I’m happy to clean up the dialog if JP wants to check in what he has. Just let me know…. > On 3 May 2018, at 19:54, Eeli Kaikkonen wrote: > > The feature seems to work well, clearances don't have effect on a board or in > the gerbers with paste or mask pads. > >

[Kicad-developers] Unconnected vs unrouted

There was a discussion on the forum regarding the difference between the status line “Unconnected” count (which is actually a count of non-zero-lenght ratsnest lines) and the DRC Unconnected (which is a much more thorough and accurate count) [1]. PC Wiz suggested naming them differently so

Re: [Kicad-developers] Patches consistency

;> https://github.com/phracker/MacOSX-SDKs/releases >> <https://github.com/phracker/MacOSX-SDKs/releases> >> and add this option >> >> ../configure \ >> [skip] >>--with-macosx-sdk=$MACOS_SDK_PATH \ >> [skip] >> >> >> -- >>

Re: [Kicad-developers] Patches consistency

tree. But that, and the mix of patch formats would all be moot if we have a branch.) > On 30 Dec 2017, at 11:42, Jeff Young <j...@rokeby.ie> wrote: > > Hi Anton, > > The staticbox_tabbing patch is one of the git patches. Use: > > git apply > path-

Re: [Kicad-developers] Patches consistency

Some of them are already up-stream, but we would have to move to wxWidgets 3.1 (when it comes out in a month or so) to get them. The wxWidgets folks won’t back-port header changes, for instance. I don’t know how many of the existing patches are in 3.0.3, but I don’t think very many (IIRC only

Re: [Kicad-developers] Default Canvas for v5

+1. (I used legacy for 6 months because I thought the only difference was in rendering. I didn’t realise all the tools were different too….) Cheers, Jeff. > On 30 Dec 2017, at 21:13, Chris Pavlina wrote: > > Pleeease! > > It makes no sense to use a canvas we

Re: [Kicad-developers] About icons of Sch Library Editor and PCB Library Editor

I also preferred the old icons. > On 31 Dec 2017, at 09:30, Eldar Khayrullin wrote: > > Hello. > I don't understand why this app icons were changed. > Previous icons were more clear, simple and laconic. > Now icons are hard to perception. > Are any opinion? >

Re: [Kicad-developers] Default Canvas for v5

+1 to the startup dialog idea. I think we also need to set reasonable transparencies in the layers so that it looks more like the default legacy canvas. > On 31 Dec 2017, at 10:09, Clemens Koller wrote: > > On 2017-12-31 03:53, Jon Evans wrote: >> I know this would be work for

Re: [Kicad-developers] "Won't Fix" candidates

mailto:stambau...@gmail.com> >>>> <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>: >>>> >>>> I share your concerns about the bug tracker but I do not >>believe there >>>> is any way to delete bug reports.

Re: [Kicad-developers] Patches consistency

Having a single place I could do a simple git clone (as opposed to applying patches) would be the biggest win. I don’t think it matters that much where the single place is. If there are no legal/etc. issues then the kicad org would be best. But even if it has to be in the wxWidgets org, that

[Kicad-developers] bug process

When I start working on a bug I assign it to me and mark it “In Progress”. Once I upload a patch, should I un-assign it and give it some other status, or will committers find it either way? Thanks, Jeff. ___ Mailing list:

Re: [Kicad-developers] Default Canvas for v5

+1 No menu items. Just a checkbox for Enable Hardware Acceleration in Preferences. > On 31 Dec 2017, at 18:36, Andy Peters wrote: > >> - In the case of graphics glitches, inform the users in the FAQ/Manual >> that they can fall back to software renderer in the View menu. >> -

Re: [Kicad-developers] Patches consistency

ss for pointing this. My mistake. > I meant the wxwidgets-3.0.2_macosx_unicode_pasteboard.patch could not be > applied. > Neither on top of 3.0.2 nor on top of 3.0.3. > > -- > Sincerely, > Anton Shevchenko > in...@sancoder.com <mailto:in...@sancoder.com> > &

Re: [Kicad-developers] Tool-assisted selection disambiguation

Local Ratsnest in case anyone assigned hotkeys to them. So should I stash this and wait for 6.0, or is this the kind of thing we’re still accepting into 5? Cheers, Jeff. > On 2 Jan 2018, at 13:10, Jeff Young <j...@rokeby.ie> wrote: > > There’s a bug report[1] which complains that

Re: [Kicad-developers] Tool-assisted selection disambiguation

that by allowing tools to register filters which are run by the selection tool (which shouldn’t know anything about their specific semantics) before invoking the disambiguation menu. Cheers, Jeff. > On 5 Jan 2018, at 00:11, Jeff Young <j...@rokeby.ie> wrote: > > I’ve got a version of this

  1   2   3   4   5   6   7   8   9   10   >