Can we rename "Normal" and "Normal+Insert" to "THT" and "SMT", or
"Through hole" and "Surface mount", or something similarly descriptive?
I *still* have to mouse over for the tooltip to remember which is
which...
--
Chris
___
Mailing list: https://lau
The addition of (diff_pair_gap) and (diff_pair_width) has made it such
that NO PCBs made with 'master' builds can now be loaded in the 4.0
branch. Would a patch be accepted to do one of the following, to be
added to the 4.0 branch to ease future conversion from 4 to 5?
1. Fully backport saving dif
Oh, good catch, thanks! Fixed.
On Thu, Dec 15, 2016 at 08:38:18PM +0100, easyw wrote:
> those terms should also be aligned in:
> 3d-viewer/3d_viewer/eda_3d_viewer.cpp
> 3d-viewer/3d_viewer/3d_toolbar.cpp
>
> M
>
> On 12/14/2016 8:51 PM, Chris Pavlina wrote:
> >Can we
On Fri, Dec 16, 2016 at 07:55:20AM -0500, Wayne Stambaugh wrote:
> On 12/16/2016 6:03 AM, Tomasz Wlostowski wrote:
> > On 15.12.2016 20:02, Chris Pavlina wrote:
> >> The addition of (diff_pair_gap) and (diff_pair_width) has made it such
> >> that NO PCBs made with '
There's another little project I'd like to work on in the month or so I
have off now:
https://misc.c4757p.com/outline-error.png
We have way too many error messages like that. That is, in my opinion,
completely unacceptable. It's confusing and intimidating to anyone
unfamiliar with kicad's... uniq
Can we put Page Settings back in the File menu where it was prior to
de46873? That's where it is in every other application I have ever used.
--
Chris
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launch
I second this suggestion. Numerous people have been proposing this for
quite a long time in IRC, it's a popular idea. A large number of parts
are configurable, and forcing the pins to be non-configurable makes ERC
pretty weak.
On Wed, Jan 04, 2017 at 07:22:37PM +1100, Oliver Walters wrote:
> As fa
Looks good to me, I pushed it. Thank you for your contribution to KiCad.
It's easy for patches to slip through the cracks - in the future, don't
be afraid to bump a patch a bit sooner, say within a week or two.
Apologies for losing it.
On Wed, Jan 04, 2017 at 07:45:40PM +, Diego Herranz wrote
Hey, I don't mean to be too obnoxious of a stickler, but can we work on
our commit messages just a bit? There are three things I'd really like
to see improved:
1. No vague messages like:
- 8e11d9b: very minor change.
Better: Realign comments
- 995940e: refinement
Better:
ain in a different command event causing the UI element state
> to be incorrect.
>
> Cheers,
>
> Wayne
>
> On 1/4/2017 5:18 PM, Chris Pavlina wrote:
> > Looks good to me, I pushed it. Thank you for your contribution to KiCad.
> >
> > It's easy for pa
Frankly I don't think we should be encouraging users to use the Python API
until it is significantly improved. The issues JP raises make the API
completely unsuitable for plugin use. It's opaque and no users have any
idea how to write robust Python plugins given the current state of the API.
On Ja
you: During devs of scripts it's crashing and my devs
> have to find the rigth way to process.
>
> But this kind of feature can increase number of users/devs of this kind
> of scripts and raise crash case easily.
>
> Regards,
> Le 10/01/2017 à 16:00, Chris Pavlina a écri
My concerns
are not specifically about you. I'm sure you find this feature useful;
that doesn't mean it's for full inclusion in KiCad proper.
>
> An other point is that master branch is a *dev* branch ? So modification
> on file format, API... can happen.
...what?
>
&g
On Tue, Jan 10, 2017 at 05:50:02PM +0100, Jean-Samuel Reynaud wrote:
> > I'm sure you find this feature useful;
> > that doesn't mean it's for full inclusion in KiCad proper.
> Yes, many users of KiCad here on my side are waiting for a simpler use
> of script we use internally. Anyway I understand
I reverted commit 9bc2bb2 "Fixed a VIEW_ITEM memory leak", which caused
a segfault:
https://bugs.launchpad.net/kicad/+bug/1656481
Maybe we should be using smart pointers in these data structures... ;)
--
Chris
___
Mailing list: https://launchpad.net/
This looks bad:
https://misc.c4757p.com/ugly.png
Really bad. Three of the same icon, with low enough contrast that I can
barely tell what it's a picture of... and seriously, prepending "** " to
mark the selected item? Really? Even text-mode applications that are
stuck doing things like that usual
u?
>
> 2017-01-14 15:35 GMT+01:00 Chris Pavlina :
> > This looks bad:
> >
> > https://misc.c4757p.com/ugly.png
> >
> > Really bad. Three of the same icon, with low enough contrast that I can
> > barely tell what it's a picture of... and seriously, prepe
> As variant, we may just disable menu entry for currently selected canvas.
>
> 2017-01-14 16:51 GMT+02:00 Chris Pavlina :
>
> > That's what I think I'll have to do.
> >
> > It can be annoying to have to fit within the GUI paradigm of all three
> > O
I agree that needing to switch canvases is bad. Unfortunately I really
do not think your idea is feasible.
On Sat, Jan 14, 2017 at 08:49:25PM +0100, Clemens Koller wrote:
> Sorry for trolling a bit, but...
>
> On 2017-01-14 15:35, Chris Pavlina wrote:
> > This looks bad:
In the future, you should probably send only plain text mails to this
mailing list. My client is having trouble viewing your signed message;
I'm probably not the only one. Looks like gmail's web client doesn't
show it either.
On Sun, Jan 15, 2017 at 03:09:24PM -0500, Edward Johns wrote:
Pushed. Thank you
On Wed, Jan 18, 2017 at 10:49:02PM +, Mário Luzeiro wrote:
> Hello all,
>
> Attached is a fix for the issue described by Edward. It also fixes another
> precision issue (or bug) while rendering on some angles while using the
> orthogonal projection.
>
> Thanks Edward for
Uh...subject says it all. I very frequently get things like this when
using differential pair length tuning. Are these known bugs? I'm
constantly fighting with it.
https://misc.c4757p.com/diff-pair-length-tuning-potato.png
___
Mailing list: https://lau
Unfortunately it looks like it would take me more time than I have to
learn the workings of that code :(
On Fri, Jan 20, 2017 at 05:06:29PM +0100, Tomasz Wlostowski wrote:
> On 20.01.2017 13:52, Chris Pavlina wrote:
> > Uh...subject says it all. I very frequently get things like
Mário Luzeiro wrote:
> Hi all,
>
> Attached is a patch that fixes some issues and improves the reflection and
> refraction on 3D-viewer raytracing.
> Hope you can merge it.
>
> This followed the critics sent by Chris Pavlina and Marcos Chaparro.
> Thanks for the
Merged, thank you.
On Sun, Jan 22, 2017 at 04:45:31PM +0200, Константин Барановский wrote:
> By default in Linux, KiCad opens pdf-files in GIMP (on my system), so I
> setup it to open pdf with another app and it works if extension of the doc
> in lower case (pdf). But if extension in upper case (P
Merged. Thank you.
On Sun, Jan 22, 2017 at 06:32:52AM +0800, John Beard wrote:
> Hi,
>
> There are a few accessors in D_PAD that could do with const qualifiers.
>
> Also a few functions return non-POD objects by const value. This
> doesn't actually acheive anything, except forcing the compiler t
After reading about the application of std::make_unique, I like it; I am
not opposed to merging this. I would, however, be in favor of modifying
it slightly to emit a warning or error if built under C++14, so that it
is not forgotten if and when we do make the transition to C++14 in the
future.
Is
Merged. Thank you
On Mon, Jan 23, 2017 at 09:28:42AM +0800, John Beard wrote:
> This patch makes it possible to edit locked modules in the module editor.
>
> Since you have to explicitly launch modedit to be able to change the
> module, and there is no change to pcbnew behaviour, editing locked
>
I'm talking to someone on IRC right now who lost two hours of routing
because pcbnew crashed, then deleted his autosave file before he could
make use of it. We need to put some new efforts into:
1. Never delete autosave data. He may have accidentally saved the board
before loading the autosave, I'
Can developers who reply to bugs by handwaving an explanation that
totally misunderstands the point of the bug report and then set them
"Won't Fix" without any further comment please just... not do that? It
gives users an impression that the developers are rude and not grateful
for the user feedbac
On Tue, Jan 24, 2017 at 09:09:45AM -0700, Andy Peters wrote:
>
> > On Jan 23, 2017, at 4:26 PM, Chris Pavlina wrote:
> >
> > I'm talking to someone on IRC right now who lost two hours of routing
> > because pcbnew crashed, then deleted his autosave file be
n not I end up accidentally hitting the enter key when opening a
> project at work. Usually causing overwrites I didnt need to.
>
> On Tue, Jan 24, 2017 at 11:42 AM, Chris Pavlina
> wrote:
> > On Tue, Jan 24, 2017 at 09:09:45AM -0700, Andy Peters wrote:
> >>
> >> &
In the file format specification at [1] via [2], we specify the
following for string escapes:
> Here is a legal string with an embedded quote: leg"23
> Here is the same string quoted, and because it is quoted the internal
> quote must be duplicated: "leg""23"
This is NOT how we are actually quoti
On Thu, Jan 26, 2017 at 09:49:40AM -0500, Wayne Stambaugh wrote:
> If no one is opposed to adding spin controls to the 3D model selection
> dialog, I'll commit this patch when I get a chance. I've never been
> convinced that using a spin control to change a floating point number is
> terribly usef
I just pushed this; apologies for it getting lost. Thank you for your
contribution to KiCad.
On Fri, Nov 04, 2016 at 04:41:55PM +, Dan Weatherill wrote:
> Hi all,
> attached is a patch which removes the spurious "Ohm" sign from the multiplier
> bitmaps in PCB calculator. This is bug #1005383
because
> it's kind of standard?
>
> Regards,
>
> Clemens
>
> On 2017-01-26 21:45, Chris Pavlina wrote:
> > I just pushed this; apologies for it getting lost. Thank you for your
> > contribution to KiCad.
> >
> > On Fri, Nov 04, 2016 at 04:41:55
who 1. is French, 2. is accepted as an authority
on SI matters) says kilo has lowercase "k". Can you cite a source?
On Fri, Jan 27, 2017 at 12:50:05PM +0100, jp charras wrote:
> Le 27/01/2017 à 12:26, Chris Pavlina a écrit :
> > I noticed the artifacts in the code too, but
ristoffer
>
> On 2017-01-26 17:09, Chris Pavlina wrote:
> >On Thu, Jan 26, 2017 at 09:49:40AM -0500, Wayne Stambaugh wrote:
> >>If no one is opposed to adding spin controls to the 3D model selection
> >>dialog, I'll commit this patch when I get a chance. I'
On Fri, Jan 27, 2017 at 05:21:42PM -0500, Wayne Stambaugh wrote:
> I finally got the new schematic I/O plugin fully functional for the
> current schematic and symbol library file formats. When you have some
> time, please test this to see if I've missed anything. I've pushed it
> to my repo on la
On Fri, Jan 27, 2017 at 07:28:09PM -0500, Wayne Stambaugh wrote:
> On 1/27/2017 6:02 PM, Chris Pavlina wrote:
> > On Fri, Jan 27, 2017 at 05:21:42PM -0500, Wayne Stambaugh wrote:
> >> I finally got the new schematic I/O plugin fully functional for the
> >> current schema
On Fri, Jan 27, 2017 at 11:32:06PM -0500, Wayne Stambaugh wrote:
> On 1/27/2017 7:40 PM, Chris Pavlina wrote:
> > On Fri, Jan 27, 2017 at 07:28:09PM -0500, Wayne Stambaugh wrote:
> >> On 1/27/2017 6:02 PM, Chris Pavlina wrote:
> >>> On Fri, Jan 27, 2017 at 05:21:42P
Is it a known bug that in the schematic, symbols are seen as having no
library association? If I click on a part, it shows "Library: none" in
the status bar, and if I press ctrl+E over the part, libedit makes me
select a library.
On Fri, Jan 27, 2017 at 05:21:42PM -0500, Wayne Stambaugh wrote:
> I
00:00:00 2001
From: Chris Pavlina
Date: Sat, 28 Jan 2017 15:48:55 -0500
Subject: [PATCH] Reorder eeschema toolbar slightly
- Put the output generation steps (annotation through pcbnew) in the
correct order as expected by the user running through them.
- Add a Plot button to match pcbnew
---
ees
On Sat, Jan 28, 2017 at 04:26:06PM -0500, Wayne Stambaugh wrote:
> On 1/28/2017 3:56 PM, Chris Pavlina wrote:
> > Hi,
> >
> > A number of users have been confused by the fact that the order of
> > toolbar buttons in eeschema no longer corresponds to the order in w
th it.
--
Chris
>From 78aea6145b8a6f21e7290238c07be987250af8b7 Mon Sep 17 00:00:00 2001
From: Chris Pavlina
Date: Mon, 30 Jan 2017 16:53:48 -0500
Subject: [PATCH] libedit: preselect active component when switching
---
eeschema/component_tree_search_container.cpp | 27 +++
Hi,
This patch adds a hotkey (default: Ctrl+L) to libedit for Load
Component. Just another simple workflow-quickener when doing a lot of
library edits. I'll push this one in a day too.
--
Chris
>From c45f9c2b740ca5e7a7ac264d50a7d59d57794f3b Mon Sep 17 00:00:00 2001
From: Chris Pavli
I think it's worth revisiting this. I know we're not ready to remove
legacy yet, but we're getting close. Starting to factor it out into a
switchable build option is a good way to make sure the transition is
smooth and help find anything that is still missing. Obviously the
default build option sho
On Tue, Jan 31, 2017 at 11:32:40PM +0800, John Beard wrote:
> Hi,
>
> The attached patches add the "exchange footprints" command to the GAL edit
> tool.
>
> This is 1 out of 3 parts of
> https://bugs.launchpad.net/kicad/+bug/1541460. I'm not sure how to put
> this as a commit comment exactly.
G
On Tue, Jan 31, 2017 at 10:45:42AM -0500, Wayne Stambaugh wrote:
> On 1/31/2017 10:36 AM, Chris Pavlina wrote:
> > On Tue, Jan 31, 2017 at 11:32:40PM +0800, John Beard wrote:
> >> Hi,
> >>
> >> The attached patches add the "exchange footprints" command
/home/cmp/git/kicad/eeschema/dialogs/dialog_edit_one_field.cpp: In member
function ‘virtual bool DIALOG_EDIT_ONE_FIELD::TransferDataToWindow()’:
/home/cmp/git/kicad/eeschema/dialogs/dialog_edit_one_field.cpp:174:42: warning:
comparison between signed and unsigned integer expressions [-Wsign-compa
tting. I saw:
> >
> > if ( ... )
> >
> > instead of:
> >
> > if( ... )
> >
> > more than once in your patch.
> >
> > Thanks,
> >
> > Wayne
> >
> > On 1/31/2017 2:13 PM, Chris Pavlina wrote:
> > > /home/cm
Okay, just pushed this to both branches.
On Sat, Jan 28, 2017 at 04:26:06PM -0500, Wayne Stambaugh wrote:
> On 1/28/2017 3:56 PM, Chris Pavlina wrote:
> > Hi,
> >
> > A number of users have been confused by the fact that the order of
> > toolbar buttons in eeschema n
This sounds really nice, I'm testing it now.
I'm not sure how, but you seem to have got another patch tangled up in
this one. I've attached a cleaned version for the convenience of anyone
else looking to test this.
On Thu, Feb 02, 2017 at 07:51:41PM +1100, Oliver Walters wrote:
> When first launc
This is a very nice improvement, and the change is pretty trivial - I'm
going to merge it. Thank you!
On Thu, Feb 02, 2017 at 10:10:25PM +1100, Oliver Walters wrote:
> Ah, sorry Chris.
>
> On Thu, Feb 2, 2017 at 10:09 PM, Chris Pavlina
> wrote:
>
> > This sounds reall
Oops, I didn't mean to push this one at the same time, clumsy push
command - but it looks good too. I always hated that delete dialog.
Thank you!
On Thu, Feb 02, 2017 at 09:42:01PM +1100, Oliver Walters wrote:
> The attached patch removes the clunky "Delete Single Part" dialog in
> libedit, and re
or that in case you want it, I had it all done before
noticing this.
On Thu, Feb 02, 2017 at 06:15:57AM -0500, Chris Pavlina wrote:
> Oops, I didn't mean to push this one at the same time, clumsy push
> command - but it looks good too. I always hated that delete dialog.
> Thank you!
&
I admit I'm getting self-indulgent here, this request is definitely a
bit "what Chris would do if made Dictator of KiCad", but... just testing
the waters here:
What do people think about, for either the 5.0 or 6.0 release, ditching
the old application names, in favor of everything being one tool u
ke that the apps have unique names and notngeneric names
> like PCB editor, because it makes it easier when talking about a specific
> name rather a description.
>
> Den 02/02/2017 14.56 skrev "Chris Pavlina" :
>
> > I admit I'm getting self-indulgent here, t
; different process library. (i.e. use RoundRect shapes vs. Rectangular
> >> shapes
> >> to improve tombstoning or solderpaste release.)
> >> Here, we are thinking to generate footprints dynamically depending on
> >> soldering process parameters - but an MSOP-8 will
On Thu, Feb 02, 2017 at 11:20:46AM -0600, José Ignacio wrote:
> On Thu, Feb 2, 2017 at 7:56 AM, Chris Pavlina
> wrote:
>
> > I admit I'm getting self-indulgent here, this request is definitely a
> > bit "what Chris would do if made Dictator of KiCad", but
keep them.
>
> On 2/2/2017 8:56 AM, Chris Pavlina wrote:
> > I admit I'm getting self-indulgent here, this request is definitely a
> > bit "what Chris would do if made Dictator of KiCad", but... just testing
> > the waters here:
> >
> > What do
Keep in mind I am not suggesting changing the name of the whole package.
This is more like if Ford suggested changing Qxshift* to SelectShift[1].
It's a clearer name that tells what the thing does, and
really...nobody's going to miss "Qxshift".
[1]
https://owner.ford.com/how-tos/vehicle-features/
On Thu, Feb 02, 2017 at 01:07:05PM -0500, Wayne Stambaugh wrote:
> On 2/2/2017 1:08 PM, Chris Pavlina wrote:
> > Keep in mind I am not suggesting changing the name of the whole package.
> > This is more like if Ford suggested changing Qxshift* to SelectShift[1].
> > It's
On Thu, Feb 02, 2017 at 01:07:05PM -0500, Wayne Stambaugh wrote:
> On 2/2/2017 1:08 PM, Chris Pavlina wrote:
> > Keep in mind I am not suggesting changing the name of the whole package.
> > This is more like if Ford suggested changing Qxshift* to SelectShift[1].
> > It's
*scratches head* must have missed this...now I sure look like an ass for
submitting that suggestion as if nobody else had ;)
On Thu, Feb 02, 2017 at 07:33:01PM +0100, jp charras wrote:
> Le 02/02/2017 à 15:41, Pedro Martin a écrit :
> > Hi Chris,
> >
> > Maybe "Composant Vers pcb"? Component to
I'm not getting these emails that JP is replying to that seem to be
addressing me...
On Thu, Feb 02, 2017 at 07:54:02PM +0100, jp charras wrote:
> Le 02/02/2017 à 19:13, Pedro Martin a écrit :
> > Hi Chris,
> >
> > Beginners solve this issue... reading the manual.
That's not the point. Silly qui
Can I just copy all this and claim I wrote it? It sounds good ;)
On Feb 2, 2017 2:11 PM, "Jon Evans" wrote:
> As a mostly user and occasional code hacker, here are my thoughts:
>
> The EDA tool industry is trending towards more integration, as many of the
> commercial products were originally fo
g for "how to
FOO in eeschema", just search for "how to FOO in kicad"!
>
> Ki in german is used for "Künstliche Intelligenz" (artificial
> intelligence)... but i've heard KiCad was mocked as KinderCad as well.
>
> Regards,
>
> Clemens
>
Most recent commit is: Update tools/property_tree support so it builds again.
Entirely out of curiosity...what is tools/property_tree actually for? I
don't get what its purpose is.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
ke ubuntu and their decision to have
> "Document Viewer" as the name for evince etc.
Agreed.
>
> - Kristoffer
>
> On 2017-02-02 22:04, Chris Pavlina wrote:
> >On Thu, Feb 02, 2017 at 09:55:59PM +0100, Clemens Koller wrote:
> >>Hi!
> >>
> >&
I don't have a chance to test this right now, but I REALLY like the
idea. As a (non-official) library maintainer I'd use the hell out of
this.
On Fri, Feb 03, 2017 at 10:40:30AM +1100, Oliver Walters wrote:
> bump :)
>
> On Thu, Feb 2, 2017 at 1:28 AM, Oliver Walters <
> oliver.henry.walt...@gmai
Hi,
There's a feature I'd like to contribute if nobody objects (and if
nobody is working on something similar - let me know!). This should not
change or impede the existing standard KiCad workflow, but should help
out those who do it a bit differently.
I would like to add another section to the c
Chris,
>
> I have attached an updated patch that (at least on my end) fixes the
> unit-deletion bug.
>
> Can you please confirm that you no longer see the erroneous behaviour?
>
> I have also included your preselect patch.
>
> Cheers, Oliver
>
> On Thu, Feb
the m_unit* variable to the selected unit. If the currently
> selected part did not have at last as many units, it was showing a
> non-existent view of the selected part.
>
> This has been addressed in the attached version of the patch.
>
> Hopefully no more errors!
>
> On S
changes:
1. Make datasheet a clickable link
2. Add footprint preview/selection discussed earlier
3. Rearrange dialog to make this all fit
--
Chris
>From bd18e1c54e4cdd8ae42d185410eabd42f7c4ef1b Mon Sep 17 00:00:00 2001
From: Chris Pavlina
Date: Sun, 5 Feb 2017 14:18:29 -0500
Subject: [PA
Still very early... I call it "componentchoosernew"
https://misc.c4757p.com/componentchoosernew.png
--
Chris
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.n
Awesome! I was going to do it last night but spent so much time trying
to make wx behave that I never got around to it. Thank you!
On Mon, Feb 06, 2017 at 10:38:55AM +0100, Tomasz Wlostowski wrote:
> On 06.02.2017 03:52, Chris Pavlina wrote:
> > Still very early... I call it "compo
Wlostowski wrote:
> On 06.02.2017 12:29, Chris Pavlina wrote:
> > Awesome! I was going to do it last night but spent so much time trying
> > to make wx behave that I never got around to it. Thank you!
> >
> The feature you're working on is also awesome! Looking forward to see it
mage ;)
>
> Mario
>
> From: Kicad-developers
> [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of
> Chris Pavlina [pavlina.ch...@gmail.com]
> Sent: 06 February 2017 02:52
> To: kicad-developers@li
like to
see it happen someday, but it's by no means high-priority.
On Thu, Feb 02, 2017 at 12:46:37PM -0500, Chris Pavlina wrote:
> I think I am going to seek out some user views on this. As usual it
> doesn't do us much good to speculate about what non-developers want.
>
>
On Mon, Feb 06, 2017 at 02:55:35PM -0500, Wayne Stambaugh wrote:
> On 2/6/2017 7:59 AM, Chris Pavlina wrote:
> > Eagle converts should like it, it's rather inspired by their component
> > selector... ;)
> >
> > It's coming together nicely. Footprint prev
Preview at g...@github.com:cpavlina/kicad branch componentchooser.
Footprint part still pending.
On Sun, Feb 05, 2017 at 09:52:03PM -0500, Chris Pavlina wrote:
> Still very early... I call it "componentchoosernew"
>
> https://misc.c4757p.com/componentchoosernew.p
I'm working on an eight-layer board and really can't wait for this to
hit pcbnew too. It's bloody impossible to tell layers apart with KiCad's
state-of-the-80s-art color system.
On Mon, Feb 06, 2017 at 10:03:11PM -0500, Jon Evans wrote:
> Hi all,
>
> I started working on the idea of a color theme
d)
>
> There are not a lot of suitable binary values.
> In all cases the background must be black (when using OR or transparency).
>
> Note also Eeschema does not use currently transparency, and the choice of
> colors is not critical.
>
> >
> > On 7 February 20
Honestly I think that's one of the silliest things I've ever heard. Pins
that you can't see should make connections that you can't see to wires
that you can? The ONLY imaginable use case for this is stacks of pins.
Every other possible case is a mistake.
On Tue, Feb 07, 2017 at 11:09:44AM +0100, K
visible pins of type "no connect". Remove
the stupidity in the design without screwing the people who depended on
it.
>
> -Kristoffer
>
> On 2017-02-07 12:33, Chris Pavlina wrote:
> >Honestly I think that's one of the silliest things I've ever heard. Pins
ough popup warnings /yet/?! Are you
kidding?
The feature is confusing, it should be reworked to be less confusing.
Not leave it confusing and yell at the user when he gets confused.
>
> - Kristoffer
>
> On 2017-02-07 12:50, Chris Pavlina wrote:
> >On Tue, Feb 07, 2017 at 12:44:45PM
d behaviours.
>
> To me every no-connect pin should not be able to be connected. Not depending
> on its visibility.
>
> - Kristoffer
>
> On 2017-02-07 13:22, Chris Pavlina wrote:
> >On Tue, Feb 07, 2017 at 01:15:43PM +0100, Kristoffer Ödmark wrote:
> >>I think t
Commit 43cb4560bfcf0624e9707c4c512cc3ccce385ce9
Rewrite code for PANEL_PREV_3D because the way events were previously managed
are not compatible with a good mouse event management.
To avoid a lot of tedious code, wxFormbuilder is used to create the
PANEL_PREV_3D_BASE class.
...didn't we agree
Merged. Thank you
On Tue, Feb 07, 2017 at 09:30:53PM +0800, John Beard wrote:
> Hi,
>
> Here is a patch to show zero-thickness lines in GAL using the "outline width".
>
> This addressess https://bugs.launchpad.net/kicad/+bug/1501749
>
> Cheers,
>
> John
__
k forward to that. Definitely an area we can improve on.
>
> -Jon
>
> On Tue, Feb 7, 2017 at 6:32 AM, Chris Pavlina
> wrote:
>
> > Let people choose. Have the default colors be wxDC-friendly. Trust me,
> > nobody is choosing to work with eight-layer boards in lega
Currently our UI policy says to follow the GNOME user interface
guidelines.
...has anybody read the GNOME HIG lately? It's really different from
anything we have now, and generally pretty controversial. I don't think
it's what it was back when we decided to use it. Unless we really want
to start m
On Tue, Feb 07, 2017 at 01:57:53PM -0500, Wayne Stambaugh wrote:
> On 2/7/2017 1:15 PM, Andy Peters wrote:
> >
> >> On Feb 7, 2017, at 8:16 AM, Nox wrote:
> >>
> >> From a user point of perspective I would claim that the issue only raises
> >> because there is the possibility to make pins invisi
ector dialog patch?
> If so hold off committing it until I get a chance to review it.
>
> Thanks,
>
> Wayne
>
> On 2/5/2017 2:21 PM, Chris Pavlina wrote:
> > Hi,
> >
> > This patch adds more information to the component selector. In
> > particular, it a
We actually discussed this on IRC, it had a bug - I pushed a fixed
version. Sorry, I should have replied here to say so.
On Tue, Feb 07, 2017 at 11:18:42PM +0100, Maciej Suminski wrote:
> Hi John,
>
> For the record, Chris has already committed your patch. Thank you both,
> I am slowling crawling
I suggested something related earlier. Here is what I would do:
- Merge OpenGL and Cairo!!! The average user doesn't know what a Cairo
is, or what a GAL is. We're lucky if they know what an OpenGL is.
OpenGL and Cairo should just be "Pcbnew", with a fallback from GL to
Cairo if GL can't star
Since the recent updates to it, I have found the Cairo backend to be on
par with legacy. Have you tried using Cairo in a nightly build?
On Wed, Feb 08, 2017 at 10:48:45AM +0100, Martin Schreiber wrote:
> On Wednesday 08 February 2017 10:25:03 Mário Luzeiro wrote:
> >
> > I never investigate, maybe
Something stands out from this email that's worth mentioning, I think:
> Admitted, I don't have the newest hardware but I like to have not so fast
> machines in order to be forced to develop fast software. ;-)
WE DON'T. It is unreasonable to expect the developers of KiCad to lock
themselves into
refuse to
get basic things like OpenGL working properly.
On Wed, Feb 08, 2017 at 01:10:52PM +0100, Martin Schreiber wrote:
> On Wednesday 08 February 2017 12:35:40 Chris Pavlina wrote:
> >
> > Seriously, every $50 used laptop on Craigslist has OpenGL support.
> >
> Which norma
On Wed, Feb 08, 2017 at 01:28:16PM +0100, Martin Schreiber wrote:
> On Wednesday 08 February 2017 13:18:39 Chris Pavlina wrote:
> > As a Linux user for many years now, that has not been my experience.
>
> You are a happy guy!
> I am the author of MSEide+MSEgui where users expect
1 - 100 of 1122 matches
Mail list logo
