Windows has always been sucky dealing with scrollwheel focus, on most
program you have to click before you can scroll.
On Tue, Jan 31, 2017 at 2:50 PM, Diogo Condeço
wrote:
> Just a side note... This is working 100% in macos... The focus is working
> just fine... on 3D preview it zooms in and ou
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... just testing
> the waters here:
>
> What do people think about, for either the 5.0 or 6.0 release, ditching
>
I really like this idea for after 5 is out
On Sat, Feb 4, 2017 at 11:25 PM, John Beard wrote:
> Hi,
>
> I support the general idea of being able to turn off bits of the
> legacy canvas at will, in principle. However, I'm not sure how many
> people will actually bother to check if stuff behind an
My experience is the opposite, on my particular linux box I get the worst
performance with legacy (it is fast for tiny toy boards, but the
performance rapidly declines as it gets more complicated), New Cairo is
also slow but not as bad, but the absolute best performance is with OpenGL
(of course).
I do like KiCad's behavior quite a bit, though maybe there could be a
better way to signal users about it. In any case it is much better than
E**le's tendency to fill zones even though things are disconnected. I have
a box with 100 fully assembled coasters from a previous designer that used
a groun
This broke all my designs with microchip parts (which have forward slashes
in the symbol names). Sadpanda.jpg
On Fri, Feb 10, 2017 at 8:55 AM, Wayne Stambaugh
wrote:
> I just pushed my changes to make the schematic I/O plugin the default
> for all schematic and symbol library I/O. This is a pre
I get that / is forbidden because part names will be file
> >> names in the new format, but this is going to break libraries. Manufs
> >> have used all kinds of horrid symbols in part numbers. Perhaps we should
> >> make the plugin system allow each plugin to specify i
I feel it would be important to have the freest possible license for
generated models and footprints as to not interfere with uses of the
library, in the interest of unifying library development and avoiding
license splits. (aside from the fact that copyright on some of those things
is a bit tenuou
One way would be to separate the input data to the scripts (dimension
tables) and declare that public domain, then keep the scripts GPL but
clarify that they will not impose on the output any more restrictions than
the license of the input.
On Sun, Feb 26, 2017 at 3:16 PM, Cirilo Bernardo
wrote:
GPL2+ Already includes GPL3+, i see no reason to change it up aside from
preventing code reuse by other projects. The whole of KiCad as it is cannot
be redistributed under
anything other than GPL version 3 at the moment.
- Jose
On Mon, Mar 13, 2017 at 9:51 PM, Cirilo Bernardo
wrote:
> Hi folks,
eeschema uses mils, which are exactly 25400 nanometers, eeschema can be
losslessly converted to nanometers. Another advantage of using nm in
eeschema would be that it would be possible to use round metric quantities
(right now it's impossible and confusing as numbers are rounded to the
nearest mil)
It would be interesting to just implement a graphic polyline class that
could work both in eeschema and pcbnew, it would be an extension of the
existing line one, that could case a (nice) change in the file format.
On Sun, Mar 19, 2017 at 4:43 PM, Oliver Walters <
oliver.henry.walt...@gmail.com> w
I like option #3 the most, #1 a close second, #4 the least, i wouldn't like
unexpected automatic saving behavior. If anything it may be worth it to
have a generic thing were to toss all these warts in the future. Perhaps a
general "file repair/recovery", kind of how the rescue system works for
symb
option when I get some time. I really wanted get this fix
> committed as quickly as possible to minimize the number of broken
> schematics.
>
> Cheers,
>
> Wayne
>
> On 3/31/2017 9:40 AM, José Ignacio wrote:
> > I like option #3 the most, #1 a close second, #4
While changing the format it would also be great if a separate clearance
could be specified between the zone and board edges vs trace clearances, at
least leave the capability in the format if it can't be implemented yet.
I've found that the required copper pullback in some cases is much higher
tha
It's been established that new features have to work with GAL, but they
don't need to work with legacy. What's not allowed yet is to BREAK legacy
by implementing a new GAL-only feature.
On Sun, Apr 30, 2017 at 9:43 PM, Simon Richter
wrote:
> Hi,
>
> what is the current outlook on the legacy canv
I've done a bit of testing on this branch and it works great for me, it cut
the time it takes to release a board to production significantly.
Thanks!
Jose
On Mon, May 1, 2017 at 7:42 AM, Wayne Stambaugh
wrote:
> Hey Oliver,
>
> I just need to find the time to test and review your changes. I wi
Yay!
On Tue, May 2, 2017 at 2:25 AM, Oliver Walters <
oliver.henry.walt...@gmail.com> wrote:
> I have attached a patch-set that implements "partial selection" of objects
> when the selection box is dragged right-to-left.
>
> L -> R = Objects must be completely enclosed to be selected
> R -> L = O
It used to be that kicad was too sensitive to pads and it would almost
never use the anchor in smaller components, now it works much better. I
don't see anything needing to be fixed. Could you show a test case where it
doesn't behave correctly and file a bug on launchpad? Just reverting
whatever ch
the way autocad did it since about when computer mice started coming out
for computers was to use a continuous border for the rectangle when doing a
"window" select (that is, all objects must be completely enclosed to be
part of the selection), when dragging the other way the outline is dashed
for
The attachments got scrubbed (probably too large), i'd recommend you upload
the videos to youtube or some other video sharing site.
On Fri, May 5, 2017 at 3:07 AM, Carlo Maragno wrote:
> Hi there,
>
> I done some tests, including a full system wipe and the behavior is still
> the same. I tried t
Perhaps one feature request regarding custom fields would be (if possible)
to select which field is used for grouping components, instead of just the
value field. Either a custom field or one of the standard ones like
footprint name or symbol name. Think editing all 0402 resistors, or all the
conne
Or switching between object and grid snap :)
On Mon, May 8, 2017 at 5:34 PM, Wayne Stambaugh
wrote:
> I tend to lean toward Oliver's approach. Most CAD tools I've used have
> this type of includes vs intersects selection paradigm. I don't see the
> need to tie up the modifier key if we don't h
The use of "..." for menu items that show a dialog with extra options
necessary to perform the operation has been in Microsoft's UX guidelines
and apple's HIG since time immemorial:
https://msdn.microsoft.com/en-us/library/dn742392.aspx#usingellipses
https://developer.apple.com/library/content/do
Menu icons are disabled by default in gnome 3 in an effort to make it look
more like an Apple product. You can enable them (on gtk 3.10+) with:
gsettings set org.gnome.settings-daemon.plugins.xsettings overrides
"{'Gtk/ButtonImages': <1>, 'Gtk/MenuImages': <1>}"
On Mon, Jun 5, 2017 at 5:11 PM, Ol
My two cents. All this copyleft licensing stuff for _libraries_ is
over-complicating things, copyright on stuff like footprints and accurate
3d models is fairly tenuous as the representation of the work is very
tightly constrained by engineering concerns and standardization, and a good
chunk are (o
Part of my argument is that for footprints and symbols there isn't much to
improve, they are either correct or they aren't, once a footprint is done
it probably should not be ever modified individually, most changes you
usually want to do to a library are sweeping and probably even automated,
those
Unfortunately that doesn't seem to be the intent of the people who made the
3d model generators, as they inject the license into the model files, and
explicitly stated that they indeed want to restrict some uses of the
mechanically generated models so people can't compile them in their own
librarie
The problem is that you can't make old kicad read the new format, unless a
patch gets backported.
On Mon, Jul 10, 2017 at 10:19 AM, Kristoffer Ödmark <
kristofferodmar...@gmail.com> wrote:
> Could we not support reading both formats, but only write one format?
>
> - Kristoffer
>
>
> On 2017-07-10
every
> net in Eeschema using some type of label. I do this so I know which
> signals I'm routing. I've never found net names such as N-# very
> useful.
>
> I am considering saving automatically assigned net names in the new
> schematic file format but that is
Please go ahead, it makes the code hard to read when instancing an object
in the middle of a function causes a global change in the application.
Encoding should be encapsulated in the streams themselves. Without that,
the ugly hack is the only way to make the even uglier global locale setting
hack
Well, WM is technically incorrect, but GTK3 has icons off by default unless
the application forces them on (vs on by default in GTK2)
On Tue, Jul 18, 2017 at 12:35 PM, Chris Pavlina
wrote:
> On Tue, Jul 18, 2017 at 07:34:25PM +0200, jp charras wrote:
> > Le 18/07/2017 à 19:14, "Jörg Hermann" a é
Clockwise and counter-clockwise are the most usual term in American Engish,
other localizations should use the most usual term in their respective
locales (remember, this is localization, not literal translation). For
example in Argentinian Spanish it should be "Horario" and "Antihorario".
Encoding
;
>>> On Wed, Jul 19, 2017 at 2:47 AM, Wayne Stambaugh >> <mailto:stambau...@gmail.com>> wrote:
>>>
>>> On 7/18/2017 8:24 PM, Chris Pavlina wrote:
>>> >> (remember, this is localization, not literal translation)
>>>
YES!
On Fri, Aug 25, 2017 at 8:37 AM, Maciej Sumiński
wrote:
> The attached patches add to eeschema possibility of updating fields for
> components already placed on schematics sheet using library values.
>
> It is useful for users maintaining additional fields in libraries to
> store informatio
You already established that you want to extract techniques from kicad for
your own project instead of contributing. The code is all there in the
repo, free to use under the GPL.
On Mon, Aug 28, 2017 at 12:41 AM, Arun Kumar wrote:
> Hi Team,
>
> Which PCB routing algorithm are used in PCB design
I don't see why you couldn't have both, an embedded version of the actual
setup and the ability to import/export from/to an external file.
On Thu, Aug 31, 2017 at 12:54 PM, Neal Hollingsworth
wrote:
> Hi all,
> I've mostly been lurking on the list, but thought I would make a
> suggestion regar
Another element of this would be to support an arbitrary amount of stacked
mechanical layers. I've been designing some flexible PCBs lately and using
the user layers to specify stiffeners is a bit clunky. It would be nice if
the 3d renderer could do multiple stacked edges. I've had to make separate
Hello, I wrote a patch to fix the issue of Kicad creating lock/pid files
for applications and open files in the user's home directory, which is
unsightly and wrong according to the XDG standards.
To fix it I created a new function in common.cpp which fetches the proper
path to use using environmen
Hello, I wrote a patch to fix the issue of Kicad creating lock/PID
files for applications and open files in the user's home directory,
which is unsightly and wrong according to the XDG[1]/Apple[2]
standards/spec.
To fix it I created a new function in common.cpp which fetches the
proper path to use
ill test this on OS X.
>
> Adam Wolf
> Cofounder and Engineer
> W&L
>
> On Mon, Jan 5, 2015 at 3:31 PM, José Ignacio wrote:
>>
>> Hello, I wrote a patch to fix the issue of Kicad creating lock/PID
>> files for applications and open files in the user's home
atting of the if/else if statements does not follow the coding
> policy. They should be formatted:
>
> if( condition )
> {
> }
> else if( condition )
> {
> }
>
> Thanks,
>
> Wayne
>
> On 1/5/2015 4:36 PM, José Ignacio wrote:
>> Whoops, I didn't realize
low the coding
>> policy. They should be formatted:
>>
>> if( condition )
>> {
>> }
>> else if( condition )
>> {
>> }
>>
>> Thanks,
>>
>> Wayne
>>
>> On 1/5/2015 4:36 PM, José Ignacio wrote:
>> > Whoops, I
I really like the idea of opening newer files as read only, that will
force the user to do a conscious decision to save with data loss, and
would practically eliminate the issues of accidental data loss. Also
it would accommodate the issue of people using different versions
being able to "check out
#1 is the sanest option, it would be nice if there was an indication
in the editing dialog that there's a global override when you
view/edit them. Something like coloring them red and putting a warning
message in the bottom of the dialog like "Settings marked in red are
currently overridden by exte
+1 on Wayne's comments. One of the nice things about the recent work on the
board setup dialog is the centralization of board settings that were
previously spread all over the place, we really shouldn't go back the other
direction.
On Wed, Aug 21, 2019 at 8:46 AM Wayne Stambaugh
wrote:
> Hi JP,
That's a big change. Are you sure it is a good idea to do without asking
users about it? (from my part it would annoy me quite a bit if i was using
master).
On Tue, Sep 10, 2019 at 8:09 AM Jeff Young wrote:
> Ctrl-click was made consistent with Pcbnew (and platform standards) for
> toggle select
Cows (like most mammals) are toruses though...
On Mon, Dec 2, 2019 at 11:06 AM Wayne Stambaugh
wrote:
> On 12/2/19 11:59 AM, Tomasz Wlostowski wrote:
> > On 02/12/2019 17:40, Vesa Solonen wrote:
> >> topological routing will
> >
> > Could you please explain what 'topological routing' does mean (
Just one step closer to KiCAD world domination.
On Sat, Apr 4, 2020 at 11:19 AM Wayne Stambaugh
wrote:
> For those of you who haven't heard, the Altium board importer[1] was
> merged into the master branch. It should be available in nightly builds
> now or in the very near future. If you have
I am an avid user of Jan's tools (KiKit mostly) and it has become
increasingly difficult to keep them working with current v6 code as api
calls keep getting removed or moved around. I know that having an open
development process for the new API can be counter productive (bikeshedding
and all) but i
I second this. I am affected by most of these bugs (except the eeschema
one). Now that we are past the string freeze, would it be possible to at
least restore the functionality that was available in V5, even if the API
is different? Missing this functions will break things for a long time.
On Mon,
It is a nice feature when you're laying out a board that has mixed
metric and imperial footprints, you can line up the grids at a given
point in the board instead of having it handed to you randomly
depending on where you start drawing the outline. Say you have a 0.1"
pitch header and you want to p
Those artifacts look like duplicate vertexes with normals pointing
different directions, ideally, for smooth shading wou'd want to break
up the mesh on each facet of the model (ie: have all vertexes from the
star pointing up, the other side pointing down and each side pointing
perpendicular to each
M, "Cirilo Bernardo"
wrote:
> Thanks Jose,
>
> I'll adjust the IDF plugin code to do just that - split the model so the
> top and bottom planes have 1 set of vertices and the vertical edge has
> smoothed vectors with Z=0.
>
> - Cirilo
>
> On Thu, Dec 17
Woops, forgot to add the list...
...
That patch seems to be missing some things like the fake boost target
and the patches, here's one that removes that too.
Would be nice to test without the fake target, it seems to speed up compilation.
On Sun, Dec 20, 2015 at 1:29 PM, Wayne Stambaugh wrote:
What about removing the fake boost target and dependencies?
On Dec 21, 2015 11:25 AM, "Adam Wolf" wrote:
> I was able to apply the patch cleanly by doing patch --ignore-whitespace
> -p0.
>
> The build went fine on the nightly builder for OS X.
>
> On Mon, Dec 21, 2015 at 9:24 AM, Wayne Stambaugh
That patch doesn't seem to add msvc specific code, in fact it seems to
just _remove_ MINGW specific code.
-#if defined(__MINGW32__)
+#if defined(_WIN32)
On Sat, Jan 16, 2016 at 1:34 PM, Wayne Stambaugh wrote:
> Please do not commit this patch. The current policy is no MSVC specific
> code in K
I like the date idea, gEDA PCB uses that too
On Thu, Apr 7, 2016 at 1:04 PM, Chris Pavlina wrote:
> What about using the date the change was made as a "version number"? Can
> integerize it like 20160407 for example. This allows easy cross-referencing of
> a format version with the revision that i
I don't believe that's correct !(!a || !b) is equal to a && b (de
morgan)
http://hyperphysics.phy-astr.gsu.edu/hbase/electronic/ietron/demorgan2.gif
On Tue, Apr 12, 2016 at 4:16 PM, Pereira, Patrick
wrote:
> Hi,
>
> Corrections to avoid unnecessary boolean operations
> !(!a || !b) = a || b
>
> B
Looking at the change in context, it might be a slight improvement in
readability, using a positive vs a double negative, it's still mostly
a no-op though. that logic is so simple it shouldn't be confusing
either way when read in context.
On Wed, Apr 13, 2016 at 9:53 AM, Pereira, Patrick
wrote:
>
Pretty good summary on how net ties are implemented and are used in a
certain popular EDA package
http://wiki.altium.com/download/attachments/25079430/NetTies-and-How-to-Use-Them.pdf
On Fri, Apr 22, 2016 at 4:16 PM, Chris Pavlina wrote:
> Yes, you might need a nonzero impedance between nets. Or y
What about simply removing the legacy canvas preemptively from the
development branch? gal-only is pretty usable by now and it might
reduce development workload for new features.
On Tue, May 3, 2016 at 7:52 AM, Wayne Stambaugh wrote:
> On 5/2/2016 4:54 PM, Chris Pavlina wrote:
>> I'd like to star
I'm 300% in favor of this proposal, an it makes sense to store the
dimensions in the key_value pairs. From a user's perspective, they can
grab a premade symbol with default values populated in those fields,
place in the schematic and edit if necessary. for selecting the
"autogenerated flag" what ab
If a setting is removed from the GUI but is still read from the config
files the key name should be changed. Otherwise we'd have a situation
where an unsuspecting user could (accidentally or not) set something
in the UI, upgrade, and then have no way to revert to the default
behavior without editin
What about (ab)using the footprint field (actually the library plugin
system) for this? Say you add a new library plugin called "python",
each library would be a python module (either a single .py file or a
folder with an __init__.py script) That module will have a callable
for each "virtual" footp
It would not introduce a limitation, just a standard format that would
work with pcbnew footprint generators, external scripts can run
outside of kicad and use field names and values however they please.
On Wed, May 11, 2016 at 10:23 AM, Wayne Stambaugh wrote:
> On 5/11/2016 10:24 AM, J
might complicate the "caching" behavior when
deciding whether to regenerate footprints or not.
On Wed, May 11, 2016 at 10:41 AM, José Ignacio wrote:
> It would not introduce a limitation, just a standard format that would
> work with pcbnew footprint generators, external scripts
+1 on a "Clear cache" button/menu item
On Thu, May 19, 2016 at 3:39 AM, easyw wrote:
> Hi,
> I think it would also useful to have a menu item to clean 3D cache on
> request...
> just to avoid having a huge caching ...
>
> Maurice
>
>
> On 19/05/2016 05.42, Cirilo Bernardo wrote:
>>
>> Hi Folks,
>
tream patches done by packagers to patch it up, but
this should make it unnecessary.
On Thu, May 19, 2016 at 12:59 PM, José Ignacio wrote:
> Patch 1: Fix resources/linux/mime/mime/packages/kicad.xml by changing
> the extension to .kicad_pcb (was set to .brd which is the old one),
> the
The current behavior is fairly annoying, you can't really know
beforehand how much the command is gonna delete, since collinear wires
are not always merged (only when drawing more traces, not when
dragging points), so sometimes it might delete just a single little
chunk of the line, or the whole th
Hi, would any of the Linux packagers/users like to give these patches a test?
On Thu, May 19, 2016 at 1:09 PM, José Ignacio wrote:
> As for the motivation behind this annoying to apply patch, it's quite
> simple: desktop integration with linux as it is right now is fairly
> bro
bulk of the work, so I still credited you.
>
> On Sun, May 29, 2016 at 06:30:40PM -0500, José Ignacio Romero wrote:
> >
> > Put all keys in consistent order and remove/fix bogus mime types, some
> > assigned to programs that don't even open files. Those files could use
I like both suggestions, I got bitten by the annular ring issue before
because the DRC doesn't even check for that.
On Sun, Jun 5, 2016 at 4:06 PM, Chris Pavlina wrote:
> Hi,
>
> Just a quick warning - I'm going to update the default via size to 0.8mm
> diam/0.4mm drill, as the current default of
Look carefully, I removed the magic section from the gerber mime type
as requested.
On Mon, Jun 6, 2016 at 9:41 AM, jp charras wrote:
> Le 05/06/2016 à 23:53, José Ignacio Romero a écrit :
>> ---
>>
>> This version of the patch doesn't have the magic string for gerbe
That's really embarrassing, for some reason gmail was showing me the
wrong patch, here's the right one.
On Mon, Jun 6, 2016 at 11:22 AM, José Ignacio wrote:
> Look carefully, I removed the magic section from the gerber mime type
> as requested.
>
> On Mon, Jun 6, 2016
Segfault here too on linux
On Fri, Jun 10, 2016 at 2:50 PM, Simon Wells wrote:
> also getting a crash here after starting in OGL -> Cairo -> OGL (osx)
>
> On Sat, Jun 11, 2016 at 5:20 AM, jp charras wrote:
>> Hi, Orson,
>>
>> I have a new issue after commit 6912/6913:
>> I can switch from legacy
On Tue, Jun 14, 2016 at 7:33 PM, Simon Richter wrote:
> Hi,
>
> for net ties, I have to touch the schematic cleanup, because that will
> merge adjacent wires going in the same direction, which is not useful
> for me, as I need all wires going into a tie as separate nets (except
> for ERC, where th
kicad.org used to be a "domain for sale" landing page for a long
while, but looks like in July it was acquired by DigiKey and made to
redirect to http://digikey.com. Maybe it would be a good idea to ask
them nicely if they could redirect it to kicad-pcb.org instead, or
donate it to the project.
I
On Thu, Sep 1, 2016 at 12:02 PM, Wayne Stambaugh wrote:
> Sorry it took so long. I took a look at Cirilo's changes an it looks
> good. We still need a PKGBUILD file for msys2 with JPs patch so we
> don't have to build oce from source.
>
> When I merge Cirilo's 3d-plugin branch and I had to creat
You need to use wxformbuilder, otherwise someone else editing the
dialog would overwrite your changes.
On Thu, Sep 1, 2016 at 6:51 PM, Diogo Condeço wrote:
> Hi all,
>
> I've attached a patch to correct some dialog behaviour in kicad. Tested on
> mac os x and windows...
>
> Affected dialogs are:
I have version 3.5.2
On Fri, Sep 2, 2016 at 4:28 PM, Chris Pavlina wrote:
> Along these lines: this isn't the first time wxfb version issues have
> come up. Perhaps we should pick an "official" wxfb version for the
> project to use, and then actually provide builds of it for developer use
> (as i
Would patches to make some of the simpler dialogs programmatic be accepted?
On Fri, Sep 2, 2016 at 7:17 PM, Wayne Stambaugh wrote:
> We've been dancing around this issue for a while without any real
> resolution. I'm fine with using Mark's version of wxFB but a lot folks
> are going to want to u
discussion about if and how we want to implement
> programmatically created dialogs. I want our dialogs to be more
> consistent in terms of spacing and layout and use the proper wxWidgets
> method for transfer data to and from controls. That will be an involved
> discussion.
>
&
Please!
On Mon, Sep 5, 2016 at 10:13 AM, Chris Pavlina wrote:
> The disambiguation menu makes it absolutely tedious to move a large
> number of hierarchical sheet pins. Would a patch be accepted to make
> hierarchical sheet pins automatically preferred when the items under the
> cursor are only
Big kudos to DigiKey, they did a great service to the project!
On Fri, Sep 9, 2016 at 8:21 AM, Wayne Stambaugh wrote:
>
> [1] http://kicad-pcb.org/about/kicad/
>
> On 9/9/2016 9:21 AM, Wayne Stambaugh wrote:
>> For those of you who have not been in the loop, Digi-Key Electronics has
>> been added
It works great on my end! As for the tool, I think it would be good to
just have it in a repo on github, as it could be very useful for other
projects too.
On Sat, Sep 10, 2016 at 10:05 AM, Michael Steinberg
wrote:
> Hello there,
>
> I've been working on trying to solve the blurred font issue in
Hi, I just committed some basic CMake support to that repo, it should
compile on all platforms provided you have the freetype and boost
libraries installed (I don't know which minimum versions are
required). It compiled successfully on Debian stretch with boost 1.61
and freetype 2.6.3.
On Sun, Sep
I don't see length matching splines to be any easier than length
matching polylines. If anything having arcs is a lot more important
than beziers as arcs can form circles while beziers can't exactly (you
need NURBS for that). Also iirc Gerbers support arcs natively so it
would end up generating bet
On Wed, Sep 14, 2016 at 5:20 PM, Oliver Walters
wrote:
>
> Any suggestions on how I could fix this? Should I be submitting one patch
> per commit, or a single patch as I have done here? Also, can I submit a
> pull-request straight from git or is the patch-email method preferred?
>
The best way is
That sound perfect! Does you "Copy 3D model" really copy the
originals, or rebuild them from the scenegraph? (I very much prefer
the latter so it's compatible with all the formats), in that case it
might be best to rename that option as "Use external model files" or
invert it and call it "Generate
rendering on blender.
On Sat, Sep 17, 2016 at 4:53 AM, Cirilo Bernardo
wrote:
> On Sat, Sep 17, 2016 at 4:35 PM, José Ignacio wrote:
>>
>> That sound perfect! Does you "Copy 3D model" really copy the
>> originals, or rebuild them from the scenegraph? (I very mu
;t be necessary if the mesh was output centered.
On Sat, Sep 17, 2016 at 9:15 AM, Nick Østergaard wrote:
> Den 17/09/2016 15.20 skrev "José Ignacio" :
>>
>> It works great, both in inline and monolithic mode! one thing I
>> noticed though is that the model output is no
me point
> so only the user-specified X, Y offset remains in the VRML export. I will
> add the options to use Grid or Drill origin as well, and make these options
> per-project rather than per-user.
>
> - Cirilo
>
> On Sat, Sep 17, 2016 at 11:19 PM, José Ignacio
> wrot
On Wed, Oct 5, 2016 at 3:55 PM, Wayne Stambaugh wrote:
> pcbnewPYTHON_wrap.cxx
That file is a source of pain, it appears to be generated by swig as a
side effect and it does go stale sometimes (whenever there is a
breaking change in the python api) as cmake is not keeping track of it
(the only so
Oh my solution was just to get the thing to build again if it got
stale, it wouldn't fix the current problem :(
On Wed, Oct 5, 2016 at 6:07 PM, Wayne Stambaugh wrote:
> On 10/5/2016 5:42 PM, José Ignacio wrote:
>> On Wed, Oct 5, 2016 at 3:55 PM, Wayne Stambaugh wrote:
>>>
WANT
On Sun, Nov 6, 2016 at 11:44 AM, Dino Ghilardi wrote:
> Hi everybody,
>
> I had to edit a lot of components in a schematic and doing it one-by-one was
> a tedious task without a chance to copy a field
> (as footprint) to many components in a single operation.
>
> To make this task easier I'v
Only jon can edit, our "edits" are just suggestions, which can be accepted
or rejected.
On Tue, Mar 6, 2018 at 1:33 PM, Wayne Stambaugh
wrote:
> I'm fine with using this for bike shedding as long as the results get
> updated in the actual road map and this is not the official road map.
> One cav
The separate program issue is just an implementation detail. The main thing
that Kicad is headed for is the refactoring slated for the 6.0 dev cycle.
The cleaner data structure foundation and subsequent decoupling of the
logic from the UI classes will allow all sorts of automation that are
currentl
Bad keming strikes again!
On Thu, Mar 15, 2018 at 4:34 PM, Marco Ciampa wrote:
> Here is a small typo:
>
> diff --git a/gerbview/toolbars_gerber.cpp b/gerbview/toolbars_gerber.cpp
> index 2c774baad..58e3c9163 100644
> --- a/gerbview/toolbars_gerber.cpp
> +++ b/gerbview/toolbars_gerber.cpp
> @@ -
The user would have to click through a big fat warning that the file is
from the future. If you wanna be doubly sure, open things in read only mode
if there is a version mismatch, so the user at worst can save the file with
another name, allowing recovery without having to drop into a text editor.
1 - 100 of 181 matches
Mail list logo
