On 29/04/2019 12:52 AM, Jeff Young wrote:
3) Cut/copy/paste is now text-based over the system clipboard. (This means you
can also copy/paste between schematics, or even between your schematic and a
text editor.)
I can't tell you how nice this sounds after opening schematics in a text
Is there any particular philosophical or technical reason why
ADVANCED_CONFIG was created as a read-only system (i.e. to modify any
values, you are supposed to edit the text config file and restart the
program)?
I have a use case for modifying its state but want to understand the logic
behind
Am 2019-04-28 17:47, schrieb Simon Richter:
Hi,
it appears we can avoid running into the "constexpr" problem with GLM
0.9.9.3 by either
- deleting "#define GLM_FORCE_PURE" from
include/plugins/3dapi/xv3d_types.h
or
- switching to C++14 mode
Do we actually need the GLM_FORCE_PURE? The
I pushed another couple of commits with a bunch of context menu stuff in them.
> On 28 Apr 2019, at 17:52, Jeff Young wrote:
>
> I’ve pushed my eemodern branch to origin in case anyone wants to check it out.
>
> There’s still a lot not done, and there are no doubt many bugs. If anyone
> else
Folks,
Today I tried to create a BOM from eeschema using a plugin command line that
had been
working for about 8 years. I need information on this new interface. Either
it is broken
or I am missing the intended set of goals and intentions. So documentation on
the latter
would be nice.
This is a bit of a trade-off between compile-time optimizations through
constexpr, and run-time optimizations through SIMD intrinsics.
The difference is probably not relevant, except that in C++11 mode, gcc
(correctly) treats constexpr member functions as implicitly const, which
causes an
Hi,
it appears we can avoid running into the "constexpr" problem with GLM
0.9.9.3 by either
- deleting "#define GLM_FORCE_PURE" from include/plugins/3dapi/xv3d_types.h
or
- switching to C++14 mode
Do we actually need the GLM_FORCE_PURE? The commit where it was
introduced doesn't explain
Huge congratulations!
It is incredible to see how far KiCad has come over the last decade,
particularly since you've been the project leader Wayne!
On Sun, Apr 28, 2019 at 11:34 AM Wayne Stambaugh
wrote:
> JP,
>
> On 4/28/19 3:30 AM, jp charras wrote:
> > Le 27/04/2019 à 20:05, Wayne Stambaugh
I’ve pushed my eemodern branch to origin in case anyone wants to check it out.
There’s still a lot not done, and there are no doubt many bugs. If anyone else
wants to contribute to it let me know and we can figure out whether to fallback
to merges or to submit patches to a single person and
JP,
On 4/28/19 3:30 AM, jp charras wrote:
Le 27/04/2019 à 20:05, Wayne Stambaugh a écrit :
For those you who haven't heard yet, I made the announcement yesterday
at KiCon that I am now work for WIT and I will be working full time on
KiCad. I really excited about the possibilities for KiCad
Thank you everyone for the congrats.
WIT is a start up that is attempting to open the full stack from top to
bottom (software and hardware at all levels). There website is WIT.com
but there is not a lot of information there yet but there are lots of
things in progress that I am not at
It is indeed a milestone for KiCad. I've known for about a month that
is was going to happen but I wanted to surprise everyone at KiCon so I
had to keep in close to the chest. It was killing me not to tell
someone. Needless to say, when I made the announcement, there were lots
of surprised
Great news, and quite a milestone for KiCad! Congratulations Wayne!
Cheers,
Javier
On Sat, Apr 27, 2019 at 8:05 PM Wayne Stambaugh
wrote:
> For those you who haven't heard yet, I made the announcement yesterday
> at KiCon that I am now work for WIT and I will be working full time on
> KiCad. I
Hi Wayne,
Congratulatios!
Any words about who WIT are and why their support to KiCad?
Iñigo.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe :
Le 27/04/2019 à 20:05, Wayne Stambaugh a écrit :
> For those you who haven't heard yet, I made the announcement yesterday
> at KiCon that I am now work for WIT and I will be working full time on
> KiCad. I really excited about the possibilities for KiCad going
> forward. Here is the moment when
15 matches
Mail list logo