der.
>
> On Thu, Mar 9, 2017 at 8:54 AM, Nick Østergaard wrote:
>
> > 2017-03-08 22:33 GMT+01:00 Wayne Stambaugh :
> > > On 3/8/2017 4:08 PM, Chris Pavlina wrote:
> > >> That's why I submitted such a trivial patch to the list first, I figured
> > &
The RescueProject() optimization looks good to me.
On Thu, Mar 09, 2017 at 08:59:33AM +0100, jp charras wrote:
> Le 08/03/2017 à 22:50, Chris Pavlina a écrit :
> > On Wed, Mar 08, 2017 at 04:33:06PM -0500, Wayne Stambaugh wrote:
> >> On 3/8/2017 4:08 PM, Chris Pavlina wrote:
I'm trying to speed up my new component selector, since the previous one
loaded and searched so quickly. I don't want a serious efficiency
regression in one of the most used dialogs in eeschema.
Since optimizing the column sizing cache and data sorting, the slowest
part is now loading FOOTPRINT_PR
It's faster for me now - about five seconds to load an empty schematic
project with all the official libs, which is bearable, and about the
same time to load a large multipage schematic with a smaller library
set.
Can we declare a verdict on whether the busy cursor is welcome still? I
feel like fi
ets to know what would happen if you
> tried to keep a single draw panel widget around, and attach/detach it from
> the component selector dynamically. But, if that is supported, you should
> be able to have your GAL panel start/stop drawing as needed.
>
> -Jon
>
> On Thu, M
On Thu, Mar 09, 2017 at 09:01:44PM +0100, jp charras wrote:
> Le 09/03/2017 à 20:31, Chris Pavlina a écrit :
> > It's faster for me now - about five seconds to load an empty schematic
> > project with all the official libs, which is bearable, and about the
> > same time
t; be read using glReadPixels().
>
> Regards,
> Orson
>
> On 03/09/2017 08:27 PM, Chris Pavlina wrote:
> > I'm trying to speed up my new component selector, since the previous one
> > loaded and searched so quickly. I don't want a serious efficiency
> > re
Fix seems simple, just make LIB_EDIT_FRAME::refreshSchematic()
non-const. It probably shouldn't be const anyway since it edits state.
I'd do it myself but don't want to step on Wayne's toes.
The addition of LIB_EDIT_FRAME::refreshSchematic() allows me to fix an
old bug finally too, so I have a fix
function informs the schematic editor (if open) to refresh it's
> view which has always been broken. Prior to this change, you had to
> perform some action to update edited symbols. I'll drop the const in a
> couple of minutes.
>
> On 03/10/2017 09:40 AM, Chris
Definitely faster - tolerably so, I'd say, maybe 1.5 seconds or so to
load all the libraries in my largest projects.
Not faster than stable though :(
Thank you.
On Fri, Mar 10, 2017 at 09:31:08PM +0100, jp charras wrote:
> Le 09/03/2017 à 21:11, Chris Pavlina a écrit :
> > On Thu
This doesn't directly address your question - but couldn't the automated
library checker actually load the footprints into KiCad, via the Python
API, to truly verify that they parse in KiCad proper?
On Sat, Mar 11, 2017 at 10:39:37AM +1100, Oliver Walters wrote:
> Hi all,
>
> Can someone tell me
Does anyone know why we have "#define VTBL_ENTRY virtual" in kiway.h and
then use that in several kiway-related places? Would anyone object to
just using "virtual"?
--
Chris
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-
>From 76a8578dc2b4b0fae3f5243e40f262f0ddfc5ef2 Mon Sep 17 00:00:00 2001
From: Chris Pavlina
Date: Sat, 11 Mar 2017 12:28:51 -0500
Subject: [PATCH] Refactor: split footprint filter data model out of cvpcb
---
common/CMakeLists.txt | 1 +
common/footprint_filter.cpp
I assume you want the header in include/preview_items as well, right?
On Sat, Mar 11, 2017 at 08:54:11AM -0500, Jon Evans wrote:
> Hi John, you are right! It was late and I didn't remember about your new
> directory but it's totally the right place. Updated patch attached.
>
> Thanks,
> Jon
>
It would be very nice if we could have a totally standalone (in terms of
constants used, etc) legacy loader that translates everything to the
constants used in the new code, so we didn't always have to tread so
carefully...
On Sun, Mar 12, 2017 at 02:06:01PM -0400, Wayne Stambaugh wrote:
> I canno
etter than Uncrustify.
The attached patch adds a _clang-format configuration file to the root
of the repository.
--
Chris
>From bd6355238dc9fd2c1c193f082ca1dbd2fb875bb7 Mon Sep 17 00:00:00 2001
From: Chris Pavlina
Date: Mon, 13 Mar 2017 09:28:22 -0400
Subject: [PATCH] Add clang-format configuration
---
Stambaugh wrote:
> Chris,
>
> I'm assuming you're asking for comment on this since you posted it as a
> patch. It makes sense to me to factor this out if you need to use in
> the symbol selection dialog.
>
> Cheers,
>
> Wayne
>
> On 3/11/2017 12:31 PM
Hi,
Would there be serious objection to merging a very minor patch to make
KiCad build properly on FreeBSD? This isn't anything big, it's basically
just adding __FreeBSD__ to the list of defines to test for alongside
__linux__ in a couple places:
https://forum.kicad.info/t/boost-lib-problem-on-64
t; >> Is this Tom's context library code? If so, Tom would you please
> >comment
> >> on the patch. I'm OK with assuming it doesn't break anything.
> >>
> >Hi Wayne,
> >
> >It's OK. I'll merge it soon.
> >
> >Che
Hi,
Currently, the footprint filter strings in a component match a footprint
if they occur *anywhere* in the footprint's name. This leads to some
possibly unintentional matches - for example, "R" has a filter "R_*",
which matches literally every footprint with R_ somewhere in its name.
This is qui
On Tue, Mar 14, 2017 at 05:24:07PM +0100, Simon Richter wrote:
> Hi,
>
> On 14.03.2017 16:57, Chris Pavlina wrote:
>
> > What if I changed this to require matching at the beginning of the
> > string? A filter meant to match anywhere in the string could be written
> &g
>
> I imagine that most footprints with a pattern like "R_*" intended it
> to be match-at-front anyway.
>
> Cheers,
>
> John
>
> On Tue, Mar 14, 2017 at 11:57 PM, Chris Pavlina
> wrote:
> > Hi,
> >
> > Currently, the footprint filter stri
On Tue, Mar 14, 2017 at 05:49:28PM +0100, Simon Richter wrote:
> Hi,
>
> On 14.03.2017 17:30, Chris Pavlina wrote:
>
> >> The regex matcher should give you good results for "^R".
>
> > I think people would be opposed to using regexes in the footprint
I can repro this as well. Latest master, also Linux.
On Tue, Mar 14, 2017 at 11:20:52AM -0700, Andrew Zonenberg wrote:
> This one is probably for Orson or Tom...
>
>
> Tested with latest code from git (on Debian Jessie), but I also had the
> issue with my old version (a few weeks old, forgot to
I'm of two minds on this. On one hand, I'd like to disable scripting on
the macOS nightlies until it's fixed, so macOS users still *have*
nightlies. On the other hand, I worry that doing so will remove
motivation to actually fix it.
Is anyone actually _actively working on a fix_? I keep seeing cha
On Fri, Mar 17, 2017 at 08:08:28AM -0400, Wayne Stambaugh wrote:
> Would someone please disable python scripting on OSX builds so we can
> provide nightly builds until we can find a solution for the python issue.
>
> On 3/16/2017 4:56 PM, Jean-Paul Louis wrote:
> > I agree 150% with Bernhard.
> >
On Fri, Mar 17, 2017 at 09:56:14AM -0400, Chris Pavlina wrote:
> On Fri, Mar 17, 2017 at 08:08:28AM -0400, Wayne Stambaugh wrote:
> > Would someone please disable python scripting on OSX builds so we can
> > provide nightly builds until we can find a solution for the python issue.
&
On Fri, Mar 17, 2017 at 10:01:20AM -0400, Wayne Stambaugh wrote:
> On 3/17/2017 9:56 AM, Chris Pavlina wrote:
> > On Fri, Mar 17, 2017 at 08:08:28AM -0400, Wayne Stambaugh wrote:
> >> Would someone please disable python scripting on OSX builds so we can
> >> provide
Hi,
When running a debug build on Windows, I get an assertion failure here:
common/fp_lib_table.cpp:250
FP_LIB_TABLE::FootprintLoad
wxASSERT( aFootprintName == (wxString) fpid.GetLibItemName() );
This is clearly related to the character encoding of the footprint name.
The footprint in qu
Oops. I lost a LOCALE_IO during a refactor. Never mind this.
On Sat, Mar 18, 2017 at 04:05:28PM -0400, Chris Pavlina wrote:
> Hi,
>
> When running a debug build on Windows, I get an assertion failure here:
>
> common/fp_lib_table.cpp:250
> FP_LIB_TABLE::FootprintLoad
On Wed, Mar 22, 2017 at 09:06:33AM -0400, Wayne Stambaugh wrote:
> On 3/22/2017 5:32 AM, Fabrizio Tappero wrote:
> > hi guys,
> > I am looking at some new icons that were introduced in kicad by the
> > people who made the related functionalities and at the user experience
> > in general. If any of
On Wed, Mar 22, 2017 at 09:19:21AM -0400, Wayne Stambaugh wrote:
> On 3/22/2017 9:20 AM, Chris Pavlina wrote:
> > On Wed, Mar 22, 2017 at 09:06:33AM -0400, Wayne Stambaugh wrote:
> >> On 3/22/2017 5:32 AM, Fabrizio Tappero wrote:
> >>> hi guys,
> >>>
"[PATCH] 3 better icons" made me think of this:
Every once in a while we get patches from people redesigning a bunch of
icons. I think we should probably have some clear policy on icons so we
can have some consistency - it makes a bit of a mess when someone
redesigns half the icons every once in a
Hi all and mostly Wayne,
I notice that a lot of our older documentation comments redundantly list
the name of the function they document:
/**
* Function IsVoid
* @return true if the field value is void (no text in this field)
*/
bool IsVoid() const
I don't see any purpose
*" above a line of code:
>
> /**
> * @brief [brief description]
> * @details [long description]
> *
> * @param aColor [description]
> * @return [description]
> */
>
> There is also the "@see" tag which is quite useful
>
> -Jon
>
> On Wed, Mar 22, 201
ures some sort of consistency - my experience is that
when we do things "as we go" we just end up forgetting to and end up
with an ugly mix.
>
> On 3/22/2017 11:41 AM, Chris Pavlina wrote:
> > Hi all and mostly Wayne,
> >
> > I notice that a lot of our older docum
On Wed, Mar 22, 2017 at 04:08:40PM -0400, Wayne Stambaugh wrote:
> On 3/22/2017 1:14 PM, Chris Pavlina wrote:
> > On Wed, Mar 22, 2017 at 01:05:48PM -0400, Wayne Stambaugh wrote:
> >> A lot of this is a product of habit and copy & paste. It's not uncommon
> >>
On Wed, Mar 22, 2017 at 11:53:40PM +0100, Clemens Koller wrote:
> Hello, Fabrizio!
>
> The horizontal + vertical justify radio buttons could possibly be improved by
> showing the alignment visually as it's done in [1] by using a 3 x 3 radio
> button matrix. It can also reduce the number of click
rather
> than components? as with the footprints being seperated from the
> symbols i don't see the justification for calling it a component (will
> also require renaming other stuff)
>
> On 23 March 2017 at 12:12, Chris Pavlina wrote:
> > On Wed, Mar 22, 2017 at 1
On Thu, Mar 23, 2017 at 10:27:55AM +0100, Clemens Koller wrote:
> Hello, Chris!
>
> On 2017-03-23 00:12, Chris Pavlina wrote:
> > On Wed, Mar 22, 2017 at 11:53:40PM +0100, Clemens Koller wrote:
> >> The timestamp is not human readable. It seems strange to me to dump it as
ot;part" that stores all the needed
> > information like symbol, footprint, pin connections between symbol and
> > footprint,
> > 3D modell, documentation.
> >
> > This might be more intuitive for new user who I see repeatedly trying to
> > match a symbol
o introduce a "part" that stores all the needed
> >> information like symbol, footprint, pin connections between symbol and
> >> footprint,
> >> 3D modell, documentation.
> >>
> >> This might be more intuitive for new user who I see repeatedly tryi
ol that determines the
> symbol/component difference and it's pretty grey definition at best. I
> retract my original statement and go with my preference of symbol.
>
> On 3/23/2017 9:05 AM, Chris Pavlina wrote:
> > Many of them actually don't have that notion. Surprising
For dialogs already using wxFormBuilder, you should continue to do so.
Any patches editing the generated files by hand will be rejected.
On Thu, Mar 23, 2017 at 03:16:34PM +0100, Fabrizio Tappero wrote:
> Hello,
> in reference to this recent email about using and not using the
> wxFormBuilder:
> h
o do some testing tomorrow.
>
> Thanks,
>
> Wayne
>
> On 3/23/2017 3:22 PM, Chris Pavlina wrote:
> > Hi again,
> >
> > Updated patch unless this doesn't apply cleanly anymore after b47a6e4
> >
> >
> > On Wed, Mar 22, 2017 at 09:09:01PM
Hi,
I've been thinking about my intent to make KiCad fall back cleanly to
Cairo when OpenGL isn't available. From what I can see, there are
certain situations where trying to use OpenGL causes crashes that appear
very hard to prevent.
I really want to do something about this - they're hard to pre
iority list to implement. I'm much more concerned
with preventing them from happening. Remember, once a crash has actually
occurred in the main program you're already past the point of no return
for possible data loss.
>
> -Jon
>
> On Thu, Mar 23, 2017 at 8:11 PM, Chris Pavlina
l IMO ;)
On Thu, Mar 23, 2017 at 08:34:39PM -0400, Jon Evans wrote:
> On Thu, Mar 23, 2017 at 8:30 PM, Chris Pavlina
> wrote:
>
> > Remember, once a crash has actually
> > occurred in the main program you're already past the point of no return
> > for possible
ork on the useless 945 chipset or whichever one it is that
> reports having hte right opengl features but does not?
>
> On 24 March 2017 at 13:39, Chris Pavlina wrote:
> > Yeah, good autosave helps.
> >
> > To be fair this is a bit offtopic - what I want really is a pr
> > > It could be a good idea to introduce a "part" that stores all the needed
> > > information like symbol, footprint, pin connections between symbol and
> > > footprint,
> > > 3D modell, documentation.
> > >
> > > This migh
test this before we push
> this to the master branch.
FWIW I have tested on all three platforms.
>
> Cheers,
>
> Wayne
>
> On 3/23/2017 3:22 PM, Chris Pavlina wrote:
> > Hi again,
> >
> > Updated patch unless this doesn't apply cleanly anymore after
On Fri, Mar 24, 2017 at 09:07:22AM -0400, Wayne Stambaugh wrote:
> On 3/24/2017 8:52 AM, Chris Pavlina wrote:
> > On Fri, Mar 24, 2017 at 08:43:00AM -0400, Wayne Stambaugh wrote:
> >> Chris,
> >>
> >> I did some testing on this and it looks good. I ha
...crap.
I'll have this fixed today.
On Fri, Mar 24, 2017 at 02:28:57PM +0100, Miguel Angel Ajo wrote:
> See <http://ci.kicad-pcb.org/job/kicad-qa/2492/display/redirect?page=changes>
>
> Changes:
>
> [Chris Pavlina] Add footprint select dropdown to component choos
hope the build box likes it :\
Apologies for any noise that may occur as a result...
On Fri, Mar 24, 2017 at 09:30:10AM -0400, Chris Pavlina wrote:
> ...crap.
>
> I'll have this fixed today.
>
>
> On Fri, Mar 24, 2017 at 02:28:57PM +0100, Miguel Angel Ajo wrote:
> >
Has cc7825d been tested on macOS? It's refusing to build for me on macOS
Sierra, clang complains that boost/test/unit_test.hpp doesn't exist. It
does, so I guess the include path must be set wrong (missing
/usr/local/include). I'm not sure how the build on those works...
--
Chris
___
Hi,
I noticed today that we have been handling conversion between UTF8 and
wxString wrong _all over_, leading to some interesting encoding issues
(UTF8 strings were being converted in the encoding of the current
locale, not UTF-8). Following a bit of discussion with Wayne I went
through and fixed
.
--
Chris
On Fri, Mar 24, 2017 at 09:29:46AM -0400, Wayne Stambaugh wrote:
> On 3/24/2017 9:18 AM, Chris Pavlina wrote:
> > On Fri, Mar 24, 2017 at 09:07:22AM -0400, Wayne Stambaugh wrote:
> >> On 3/24/2017 8:52 AM, Chris Pavlina wrote:
> >>> On Fri, Mar 2
Oh my, this is looking good! :)
On Sat, Mar 25, 2017 at 01:21:51PM +0200, Heikki Pulkkinen wrote:
> Hi,
>
> Any comments, questions!
>
> https://youtu.be/CQC6XMTGxkk
>
> Heikki
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
> > macOS machine right now :(
> > Probably qa/geometry/CMakeLists.txt should be fixed (my experience with
> > CMake and other OSes different than Linux is quite limited).
> >
> > 2017-03-25 2:47 GMT+01:00 Chris Pavlina :
> >>
> >> Has cc7825d been tested o
Hi,
Can someone please confirm authoritatively which Boost version is
installed on the Jenkins boxes? I recently had to "fix" my code to build
on Boost 1.55 [1], making it rather ugly in the process. Out of
curiosity I checked our documentation just now, and it claims that we
require 1.56 or later
On Sun, Mar 26, 2017 at 07:32:54PM -0400, Wayne Stambaugh wrote:
> On 3/26/2017 7:13 PM, Chris Pavlina wrote:
> > Hi,
> >
> > Can someone please confirm authoritatively which Boost version is
> > installed on the Jenkins boxes? I recently had to "fix"
On Sun, Mar 26, 2017 at 08:11:07PM -0400, Kevin Cozens wrote:
> On 2017-03-26 07:32 PM, Wayne Stambaugh wrote:
> > find_package( Boost 1.54.0 REQUIRED COMPONENTS system )
> >
> > That seems fairly old to me but every time we bump a dependency version,
> > users on older platforms get dropped. Any
Hi,
Just a quick update - I'm giving up for now on my plan to have a 3D
footprint view in the component selector. I just don't think the value
added vs effort spent is worth it, and there are more important things I
want to spend time on. I feel that the component chooser is Good Enough now
with 2
Hey Wayne,
In the interest of prioritizing my own work - just curious if you have
any idea how long it's going to be before declaring the v5 feature
freeze, and what that's waiting on.
--
Chris
___
Mailing list: https://launchpad.net/~kicad-developers
finish it up. I'm not
> sure where Tom and Orson stand. I just saw an email from Tom the other
> day so it looks like there is still a bit of work to do on his end with
> the stitching via support.
>
> Thanks,
>
> Wayne
>
> On 3/28/2017 10:45 AM, Chris Pavlina w
I also vote #3 for the same reason as everyone else :)
On Thu, Mar 30, 2017 at 01:33:55PM -0400, Wayne Stambaugh wrote:
> I have found and fixed the bug in this bug report:
>
> https://bugs.launchpad.net/kicad/+bug/1677282
>
> This bug creates invalid schematic files which sets the component uni
Ops. Sorry.
I caught one place where I had done that. Thought that was all. :\
On Thu, Mar 30, 2017 at 03:13:31PM -0400, Wayne Stambaugh wrote:
> I believe since the new component chooser dialog has been implement
> which hasn't been very long.
>
> On 3/30/2017 2:53 PM, Maciej Suminski wrot
ne 169 of eeschema/getpart.cpp. The component unit
> cannot be 0 even for components that do not have multiple units. There
> probably should be an assertion in the SCH_COMPONENT ctor to warn devs
> about this.
>
> On 3/30/2017 3:24 PM, Chris Pavlina wrote:
> > Ops. Sorry.
Can't build:
CMake Error at cvpcb/CMakeLists.txt:134 (add_library):
Cannot find source file:
dialogs/dialog_footprints_tree.cpp
Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
.hxx .in .txx
On Fri, Mar 31, 2017 at 12:12:54AM +0200, Maciej Suminski wrote:
> He
Merged, thank you.
On Thu, Mar 30, 2017 at 10:12 PM, Jon Evans wrote:
> Hi all,
>
> Quick patch attached to add output stream operator for COLOR4D, useful for
> debugging and for some future things I am working on.
>
> -Jon
>
> ___
> Mailing list: https
OMG YES.
I won't get to test this for a while, but...YES :)
On Apr 1, 2017 08:53, "Oliver Walters"
wrote:
> After a long break on this project I have finally rounded the edges off
> the component table viewer I have been working on.
>
> This is a table/spreadsheet view of all the components in
visibiliy of what remains to do and people looking to pick
> > off bugs can have a list of things to hit first.
> >
> > Cheers,
> >
> > John
> >
> > On Tue, Mar 28, 2017 at 11:07 PM, Chris Pavlina
> wrote:
> >> Sounds good.
> >>
> &
Looks like it should cause breakage, please don't merge. I'll have a
look at this later - wx 3.1 is unsupported, but it should be relatively
easy to resolve this and reduce future breakage if we ever upgrade.
Could you please file a bug report?
On Sun, Apr 02, 2017 at 04:08:32PM +0200, Bernhard S
By caching the width required for every text item, and using that cache to
calculate widths manually. wx's column sizing is stupid slow because it
(partially?) renders every text every time to calculate the space it uses...
On Apr 4, 2017 02:07, "Nick Østergaard" wrote:
> Hi Maciej,
>
> I also n
On Sun, Apr 16, 2017 at 04:05:10PM +0200, jp charras wrote:
> Le 16/04/2017 à 08:38, Joseph Chen a écrit :
> > Does someone here know how to make this work?
> >
> > With pcbnew's "footprint properties" dialogue window, the ESC and ENTER
> > keys are not functioning as
> > defaults as with the "pa
On Sun, Apr 16, 2017 at 08:31:41PM +0200, jp charras wrote:
> Le 16/04/2017 à 19:49, Chris Pavlina a écrit :
> > On Sun, Apr 16, 2017 at 04:05:10PM +0200, jp charras wrote:
> >> Le 16/04/2017 à 08:38, Joseph Chen a écrit :
> >>> Does someone here know how to ma
Shouldn't matter, numpad keys are traditionally treated separately for
hotkey use.
Clemens, can you link me to the bug report? I've been absent from
development for a while, but I'll be back soon and this is code I've
worked on a lot. I'll assign it to myself and fix it when I get a
chance.
On F
Hi,
Just giving a bit of an early heads-up. The macOS build VM called
"c4osx" in Jenkins - the one currently responsible for macOS nightly
builds - will be down for one to two weeks starting on Wednesday, May 10
while I move house. Hopefully I can keep this downtime on the short end
of the estimat
Hi,
Apologies for my absense. I'm looking into the issue with macOS nightles
not building, which appears to be because of kicad-ogltest which I added
a while ago.
I'm still really busy and am having trouble finding real time for this,
but I want to get the nightlies going again. If I can't actual
that (especially the “install( CODE” part) it won’t
> > find/use the libs copied into the bundle.
> > From the error, I guess that’s exactly the problem you see.
> >
> > I also didn’t notice this when I did my last build.
> > I can definitely look into it,
Hi,
Sorry for the delay in getting the macOS build VM running again - it's
up now in its new location in Denver, after a couple minor hiccups. I'll
also be returning to development soon, starting with the component
chooser bugs that have piled up.
--
Chris
__
I've been daydreaming of doing this for a while, sounds good to me.
On Sun, Jun 04, 2017 at 10:27:49AM -0400, Jon Evans wrote:
> I agree with this approach! Switching to a tree lister for preferences was
> on my list of things to propose one day. Complicated creation software like
> KiCad inevitab
They look way better in certain UI fonts. However if there's a bug that
stops them from being translatable I'm all for switching to a simple ...
-- honestly I thought that's what we were using anyway
On Mon, Jun 05, 2017 at 11:12:22PM +0200, Marco Ciampa wrote:
> On Mon, Jun 05, 2017 at 12:38:45PM
On Fri, Jun 09, 2017 at 02:03:29AM +0200, Simon Richter wrote:
> Hi,
>
> On 08.06.2017 23:56, Kristoffer Ödmark wrote:
>
> > I attached a patch where i removed all of them just to show how many of
> > them there are, also suggest that we remove that from the coding policy
> > ( patch 2 ).
>
> Wo
I'm back~~~
Since the new component selector treats the whole footprint filter list
+ footprint field as equals, shouldn't we really search through _all_ of
that?
No objection to merging this though, looks good. Mind the coding
convention, a blank line is required before conditionals
On
Hey, I'm finally back after a long absence, and haven't been paying
attention to the mailing list since like March - there's been way too
much for me to go back and read everything since then. Just fyi, if
there's been any important discussion relating to my component chooser
dialog, might want to
On Mon, Jul 17, 2017 at 09:38:12AM -0400, Wayne Stambaugh wrote:
> 7/15/2017 10:46 PM, Chris Pavlina wrote:
> > Hey, I'm finally back after a long absence, and haven't been paying
> > attention to the mailing list since like March - there's been way too
>
The following is in LIB_VIEW_FRAME (viewlib_frame.h specifically):
// TODO(hzeller): looks like these members were chosen to be static to
survive different
// instances of this browser and communicate it to the next instance. This
looks like an
// ugly hack, and should be solved diff
On Mon, Jul 17, 2017 at 04:29:44PM -0400, Wayne Stambaugh wrote:
> On 7/17/2017 4:15 PM, Chris Pavlina wrote:
> > The following is in LIB_VIEW_FRAME (viewlib_frame.h specifically):
> >
> > // TODO(hzeller): looks like these members were chosen to be static to
If I somehow found the time to strip LOCALE_IO completely out of the
footprint parser without changing the behavior, would anyone have any
religious objections or otherwise mourn the loss?
--
Chris
___
Mailing list: https://launchpad.net/~kicad-develop
LOCALE_IO exists is to hide resetting the locale on exceptions.
> I don't see how any other solution is going to result in cleaner code
> but I'm willing to entertain the idea. Please test your changes
> thoroughly and submit a patch so we can test it and take a look at it
>
On Tue, Jul 18, 2017 at 10:11:39AM -0400, Wayne Stambaugh wrote:
> On 7/18/2017 9:47 AM, Chris Pavlina wrote:
> > Yes, the goal would be to try to make the footprint parser entirely
> > non-locale-sensitive so as not to need to switch anyway. The problem
> > with L
On Tue, Jul 18, 2017 at 04:42:28PM +0200, jp charras wrote:
> Le 18/07/2017 à 15:47, Chris Pavlina a écrit :
> > Yes, the goal would be to try to make the footprint parser entirely
> > non-locale-sensitive so as not
> > to need to switch anyway. The problem with L
Little known fact: no object prior to the invention of the clock had
ever rotated before, so words for this before then were not required~~~
On Tue, Jul 18, 2017 at 08:09:52PM +0300, firewalker wrote:
> How about before clocks? :P :P :P
>
> On Tue, Jul 18, 2017 at 7:49 PM, Wayne Stambaugh
> wrot
On Tue, Jul 18, 2017 at 07:34:25PM +0200, jp charras wrote:
> Le 18/07/2017 à 19:14, "Jörg Hermann" a écrit :
> > Translation of Clockwise and Counterclockwise are long texts in many
> > languages:
> > Uhrzeigersinn and Gegenuhrzeigersinn in german for example.
> >
> > If the icon depicts (dynam
K.
The WM itself has no knowledge of menus though.
On Tue, Jul 18, 2017 at 08:04:41PM +0200, jp charras wrote:
> Le 18/07/2017 à 19:35, Chris Pavlina a écrit :
> > On Tue, Jul 18, 2017 at 07:34:25PM +0200, jp charras wrote:
> >> Le 18/07/2017 à 19:14, "Jörg Hermann" a écri
> (remember, this is localization, not literal translation)
Thank you! en_US should be "counterclockwise" and "clockwise" (or even
CCW/CW would be easily understood), and different phrasings should be
used in different languages. Don't avoid "clockwise" in English because
the French don't use it.
Generally single entry controls will contain a colon in the label but
entire sections will not - thus "Output directory" and "Default line
thickness (mm)" should have colons, but "Messages" and "Page Size"
should not. This is because the single entry controls read as a single
line of text, where it
I like this change, and I was about to push it and suggest we can add
any suggested changes others have later, when I decided to test it on a
large project.
It's REALLY slow now. If I click on a sheet, KiCad freezes for a solid
ten seconds in my larger test project. IMO that isn't acceptable, it's
Server back up, apologies. Power cycled the host and forgot to bring the
VM back up.
On Mon, Jul 31, 2017 at 03:26:43AM +1200, Simon Wells wrote:
> just had a look at the jenkins stuff and it seems the osx build server
> is down, i will yell at the build server owner
>
> On 31 July 2017 at 02:23,
201 - 300 of 1122 matches
Mail list logo
