Re: [Kicad-developers] [RFC] Symbol library file format

I agree with Carsten Here, The same way the footprints are not part of the symbol, the same way SPICE models should be defined separate. I would rather have a new atomic file-format or storage format, so one could actually send a complete part in an easy way, that would include 3D-Files,

Re: [Kicad-developers] [RFC] Symbol library file format

I like the idea of using something as Protobuf and I agree fully with the benefits, especially since one can add/remove fields with minimal impact. Basically the S-expression system used now is looking very much like a reinvented XML to me anyway, and storing protobuf-defined stuff as XML or

Re: [Kicad-developers] 5.1 preview

On Fri, 2018-07-13 at 11:33 -0600, Jeff Young wrote: > Hi Kristoffer, > > What platform are you on? Ill just paste my entire build info :) Application: kicad Version: (5.0.0-rc3-dev-82-g0bf877f83), release build Libraries: wxWidgets 3.0.4 libcurl/7.60.0 OpenSSL/1.1.0h zlib/1.2.11

Re: [Kicad-developers] 5.1 preview

Hey! Nice job! I am not really sure what is the difference everywhere but i will give my opinion on what i noticed :) Good: - Finally i can read the status text on the bottom thank you! - The BOM plugin menu is much nicer - Text and graphics view in pcbnew, very nice Bad: - Crashes

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

I agree with all of these points and I am very happy that there now is a plan! There is one thing I would like clarified for this though. Would It be okay to add the suggested template fields as a starting point for users? Ofcourse without the "silent" adding to symbols and netlists and boms.

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

Yes, the only way to make them translateable is to hard-code these and other values into kicad, same as the existing hard-coded fields. That would be a good solution for me, having similar to layers a large set of predefined fields, being able to name them and enable them at will. But storing

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

whatever would be decided. Uniformity > for > plugins use would definitely be an advantage. > > -Ben > > On Tue, May 22, 2018 at 5:38 AM kristoffer ödmark < > kristofferodmar...@gmail.com> wrote: > > > Thanks! This is exactly what i was going for, non

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

> Do the BOM generators automatically output all default fields or only > those with values? > > > On 22 May 2018, at 09:22, kristoffer ödmark <kristofferodmark90@gma > > il.com> wrote: > > > > Please disregard my previous mail, it got mangled badly some

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

and we can never have that. Because we can not suggest a name, that would be rude. I dont get the problem with a default config that hints at what it might be called. I chose MPN in my example since it is used be the Digikey library on github amongst other projects i found. > > Cheers, > Ors

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

useful, > > but > > that'll take to long for v5 so if Kristoffer's patch allows an easy > > way > > to add fields to all components or similar, I'd say do it because > > people > > will be pissed and waste their time doing it for every component in > > their

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

t'll take to long for v5 so if Kristoffer's patch allows an >> easy way to add fields to all components or similar, I'd say do it >> because people will be pissed and waste their time doing it for >> every component in their schematic. >> >> On Sun, May 20, 2018 at 3:01 P

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

patch allows an easy way to add fields to all components or similar, I'd say do it because people will be pissed and waste their time doing it for every component in their schematic. On Sun, May 20, 2018 at 3:01 PM, kristoffer Ödmark <kristofferodmar...@gmail.com> wrote: I obvviou

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

. - Kristoffer On 2018-05-20 23:40, José Ignacio wrote: I dont like this, the right solution would be to allow for importing a default config into kicad for things like that, as different groups will have different policies. On Sun, May 20, 2018 at 3:31 PM, Kristoffer Ödmark <kristofferodmar...@gmail.

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

would your patch allow that? -S Am So., 20. Mai 2018 um 13:00 Uhr schrieb kristoffer Ödmark < kristofferodmar...@gmail.com>: > Hello! > > I will open this can of worms again, I feel that I have to. So from what > I gather we have proffessionals as the main aim in Kicad. > Th

[Kicad-developers] More default fields in schematic

Hello! I will open this can of worms again, I feel that I have to. So from what I gather we have proffessionals as the main aim in Kicad. The reason I will open this issue again is that I feel we have a collaboration issue, maybe not a mayor one. But one nonetheless. We really need more

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

I think another stop gap measure is to have the ERC handle this, but otherwise I am for Orsons patch. Better a defined bad behavior than an undefined random behavior is my opinion :) On Fri, May 18, 2018, 16:53 Maciej Sumiński wrote: > How about my patch? I do not dare

Re: [Kicad-developers] New Footprint libs and wizard issues

Thank you JP! I will have a look when I get home, It was not happening on linux, and I do not currently have a windows computer anywhere, but maybe I can force the cursor to the end some other way. -Kristoffer On 2018-04-09 16:21, jp charras wrote: Le 08/04/2018 à 00:42, kristoffer Ödmark

Re: [Kicad-developers] New Footprint libs and wizard issues

I know its not the most elegant solution, but it is actually quite convenient. Just checking so that this tiny improvement isnt lost :) -Kristoffer On 2018-04-08 00:42, kristoffer Ödmark wrote: Agreed, hereis a patch for that :) - Kristoffer On 2018-04-06 17:18, Kevin Cozens wrote

Re: [Kicad-developers] New Footprint libs and wizard issues

Agreed, hereis a patch for that :) - Kristoffer On 2018-04-06 17:18, Kevin Cozens wrote: On 2018-04-06 06:30 AM, kristoffer Ödmark wrote: Attached is a patch that adds support for custom environment paths. Previously the wizard would only accept KISYSMOD, KIPRJMOD and the github one. I

Re: [Kicad-developers] New Footprint libs and wizard issues

not include the env var to KIPRJMOD, I guess there is a reason? On 2018-04-06 13:05, Jeff Young wrote: Patch looks good to me, although I’d rather see the redundant code removed. On 6 Apr 2018, at 11:30, kristoffer Ödmark <kristofferodmar...@gmail.com> wrote: <0001-Footprint-Wizard-now-als

Re: [Kicad-developers] New Footprint libs and wizard issues

Found a bug shortly after, I will reupload. I will also remove the redundant code and check if it still works. On 2018-04-06 13:05, Jeff Young wrote: Patch looks good to me, although I’d rather see the redundant code removed. On 6 Apr 2018, at 11:30, kristoffer Ödmark <kristofferod

Re: [Kicad-developers] New Footprint libs and wizard issues

charras wrote: Le 04/04/2018 à 10:01, kristoffer Ödmark a écrit : Hello! So it was a while since I made some noise, so its time again. Is there a way to create new footprint libs from KiCad? I cannot find it, right now I create them by mkdir name.pretty, thento be able to add them with the wizard, I

Re: [Kicad-developers] New Footprint libs and wizard issues

stoffer On 2018-04-04 11:02, jp charras wrote: Le 04/04/2018 à 10:01, kristoffer Ödmark a écrit : Hello! So it was a while since I made some noise, so its time again. Is there a way to create new footprint libs from KiCad? I cannot find it, right now I create them by mkdir name.pretty, thent

[Kicad-developers] New Footprint libs and wizard issues

Hello! So it was a while since I made some noise, so its time again. Is there a way to create new footprint libs from KiCad? I cannot find it, right now I create them by mkdir name.pretty, thento be able to add them with the wizard, I have to create a temp.kicad_mod file in that folder. Should

Re: [Kicad-developers] New lead developers

Congratulations! I am very glad to see this! I have been following the mailing list for a while now and seen the great contributions and ideas from you guys! Well deserved promotion! -Kristoffer On 2018-03-02 15:05, David Novak wrote: Great job guys! Thanks for your investment in the

Re: [Kicad-developers] Pads front and F.Cu visibility, possible bugs?

I started investigating this some more, there is much more rendering problems here. for example, disbling rendering of front footprints disables all the F.Silk, F.Fab, adhesive and many more. Disabling the rendering of Text on the front only disables text belonging to a footprint, no other.

Re: [Kicad-developers] Schematic symbol chooser clarification

Attached is a minimal patch that differs the dialog title. - Kristoffer On 2018-02-05 13:25, Marco Ciampa wrote: On Mon, Feb 05, 2018 at 01:10:08PM +0100, kristoffer Ödmark wrote: Hey! I just spent some time trying to "debug" a library non-issue with a EE switching from Altium for

[Kicad-developers] Pads front and F.Cu visibility, possible bugs?

Hey! Another confusion arised when I was speaking to a friend. When disabling the F.Cu layer, the pads are still visible. I can understand the need to be able to disable the pads on the front layer separate from everything else, to check for things under pads etc. What I cannot understand

Re: [Kicad-developers] Schematic symbol chooser clarification

Yeah, that to adds to the confusion. I think maybe coherency should be one of the main goal for v6. On 2018-02-05 13:25, Marco Ciampa wrote: On Mon, Feb 05, 2018 at 01:10:08PM +0100, kristoffer Ödmark wrote: Hey! I just spent some time trying to "debug" a library non-issue

[Kicad-developers] Schematic symbol chooser clarification

Hey! I just spent some time trying to "debug" a library non-issue with a EE switching from Altium for a test. He had added the libraries correctly, and they showed up. But everytime he tried adding a symbol to the schematic, no symbols was there. We sent pictures back and forth, and indeed

Re: [Kicad-developers] Update PCB from Schematic

It would be trivial if the "duplicate tool" either generated new unique identifiers or left the unique identfier value empty. I honestly dont understand why to have unique identifiers if they are not unique, so maybe this should be a bug? I know they are referenced as "timestamps" in the

Re: [Kicad-developers] FYI: Horizon

Yeah, just downloaded it and gave it a whirl. This project really shows some promise! The "pool" idea actually shows some promise for library management. I like how they want everything as parts. I will keep an eye on this. Might be something to learn and integrate into kicad! - Kristoffer

Re: [Kicad-developers] Copy/paste eeshema block betwee two different application

I do see the value of copy pasting between schematics. Its very common for design reuse. The way the copy-paste for pcbnew is done is like this: Copy: 1. checks what items are selected. 2. check what requirements the selected items have( nets, layers etc) 3. this creates a new pcb file in

Re: [Kicad-developers] Libedit and Modedit Icons

For me it feels more natural with thins flowing from left to right, so that means moving the import arrow to the left side, and also making it flowing into the document. Export also flow from left to right, so making it flowing from inside the document to out on the right side. These are good

Re: [Kicad-developers] [PATCH] Implement primitive icon scaling for high DPI

size? Thanks. On Wed, Jan 10, 2018 at 11:16:46PM +0000, kristoffer Ödmark wrote: Tried the patch, didnt really notice anything different though, I guess you need to add some custom scaling for this to take effect? On 2018-01-10 22:23, Chris Pavlina wrote: Sure, assign me to it. I should have time to

Re: [Kicad-developers] [PATCH] Implement primitive icon scaling for high DPI

size? Thanks. On Wed, Jan 10, 2018 at 11:16:46PM +0000, kristoffer Ödmark wrote: Tried the patch, didnt really notice anything different though, I guess you need to add some custom scaling for this to take effect? On 2018-01-10 22:23, Chris Pavlina wrote: Sure, assign me to it. I should have time to

Re: [Kicad-developers] Libedit and Modedit Icons

iskette and the folder in the repo with the patch, basically if someone wants to create future icons. They could use the same arrows for any kind of export, import, save, inspect or view. I have created a set of "common icons" for exactly this purpose :) On Thu, Jan 11, 20

Re: [Kicad-developers] Libedit and Modedit Icons

Wow, really nice! Although, the icon for the bitmap2component basically looks like a screenshot symbol to me, or something related to a webcam. The old one isnt as polished, but I think it fits better. Also, would it be too much to ask for getting the arrows, the diskette and the folder in

Re: [Kicad-developers] Libedit and Modedit Icons

I think trying to replicate what this guy does here would be quite time saving wouldnt it? http://scottbezek.blogspot.se/2016/04/automated-kicad-schematic-export.html Basically scripting keypresses, and then using something like scrot to take a screenshot of the intended area. This would keep

Re: [Kicad-developers] One more quick plug for reducing "Clarify Selection" dialogs

LY_SET::POLYGON_MODE)': kicad/common/geometry/shape_poly_set.cpp:489: undefined reference to `ClipperLib::Clipper::Clipper(int)' On 2018-01-09 19:22, Wayne Stambaugh wrote: Does the patch resolve your issue? On 1/9/2018 1:21 PM, kristoffer Ödmark wrote: Yes, I can reproduce this with very thick

Re: [Kicad-developers] One more quick plug for reducing "Clarify Selection" dialogs

I just about to try :) hang on, got some merge conflicts on some local stuff On 2018-01-09 19:22, Wayne Stambaugh wrote: Does the patch resolve your issue? On 1/9/2018 1:21 PM, kristoffer Ödmark wrote: Yes, I can reproduce this with very thick tracks! On 2018-01-09 16:55, Jeff Young wrote

Re: [Kicad-developers] One more quick plug for reducing "Clarify Selection" dialogs

change the selection disambiguation is run *before* we know it’s a drag action on a simple corner, so the selection_tool thinks it needs to know which of the two segments is to be selected. Cheers, Jeff. On 9 Jan 2018, at 15:37, Kristoffer Ödmark <kristofferodmar...@gmail.com> wrote:

Re: [Kicad-developers] Renaming headers?

stuck on the Legacy/GAL stuff in the very beginning, not finding what was where. -Kristoffer On 01/09/2018 05:02 PM, Tomasz Wlostowski wrote: On 09/01/18 16:21, Kristoffer Ödmark wrote: Oh I was not planning on doing this, I am way to new to do a good job of sorting the codebase. Just wanted

Re: [Kicad-developers] One more quick plug for reducing "Clarify Selection" dialogs

If i understand him correctly that would only be when on a corner, I think it would be the desired behaviour. Although, when I try it on my build on my laptop, there is no clarify selection menu popping up when trying do drag ( 'd' ) or such on corners. Not in opengl anywas. So I dont know.

Re: [Kicad-developers] Renaming headers?

of an overview. Anyway, I just wanted to see what anyone thought about it, if a renaming was to happen, a good time for something like this might be around the same time. -Kristoffer On 01/09/2018 04:08 PM, Wayne Stambaugh wrote: On 1/9/2018 10:01 AM, Kristoffer Ödmark wrote: Quite a bit of files under

Re: [Kicad-developers] Renaming headers?

Quite a bit of files under the root directory that could benefit from some sorting as well :) Would be two patches then, one for renaming, and one for sorting them somehow, both kinda large. Maybe move classes to a folder called classes? -Kristoffer On 01/09/2018 02:59 AM, Wayne Stambaugh

Re: [Kicad-developers] Libedit and Modedit Icons

, >>> and they were accepted >>> because... I don't know? Many of the new icons >>> are really ambiguous and >>> kind of useless. Shouldn't have been merged.

Re: [Kicad-developers] [PATCH] Add bidirectional net highlight cross-probing

I was just expecting the net to be highlighted when i filed the report, I have a memory of being able to do this on a previous nightly, nothing else. But after the comments, maybe I remember wrong? Jumping around in the schematic when highlighting net is not something I want at least. I

Re: [Kicad-developers] Libedit and Modedit Icons

that there is a lack of consistency between similar icons. e.g. there are many icons which incorporate an arrow but the style/shape of the arrows varies. For the record, I like these proposed ones. They bring back the ability

Re: [Kicad-developers] Via dialog to support

when doing this, the DRC doesnt warn if there are vias that are buried are on the board, but not allowed in the design rules. I will file a bug report. On 2018-01-06 21:51, Wayne Stambaugh wrote: On 01/06/2018 02:46 PM, Tomasz Wlostowski wrote: On 06/01/18 20:41, kristoffer Ödmark wrote

Re: [Kicad-developers] Via dialog to support

:51, Wayne Stambaugh wrote: On 01/06/2018 02:46 PM, Tomasz Wlostowski wrote: On 06/01/18 20:41, kristoffer Ödmark wrote: The menu for the vias have the via type choice disabled, I cannot change the via type from through via to buried via. It is grey. Sorry, it's not implemented yet... Help

Re: [Kicad-developers] Via dialog to support

Alright! I will have a look at it :) On 2018-01-06 20:46, Tomasz Wlostowski wrote: On 06/01/18 20:41, kristoffer Ödmark wrote: The menu for the vias have the via type choice disabled, I cannot change the via type from through via to buried via. It is grey. Sorry, it's not implemented yet

Re: [Kicad-developers] Via dialog to support

setting the layers correctly for a buried/blind via? On 01/06/2018 01:03 PM, kristoffer Ödmark wrote: Hello! I just tested changin a via to a buried/blind via but I cannot get it to work, Is this a bug or am I missing something?. I have enabled the blind/buried via in the design rules

[Kicad-developers] Via dialog to support

Hello! I just tested changin a via to a buried/blind via but I cannot get it to work, Is this a bug or am I missing something?. I have enabled the blind/buried via in the design rules. - Kristoffer ___ Mailing list:

Re: [Kicad-developers] Libedit and Modedit Icons

I would love to see improved icons, I still never get used to them so i read the tooltip, newer know which one is pcb and which one is module editor. Luckily most of the time I only need to double click the kicad_pcb file anyway :) On 2018-01-06 15:08, Nick Østergaard wrote: 2018-01-06

Re: [Kicad-developers] Default Canvas for v5

ous which options will be or were set by the setup dialog Simon On 1/01/2018, at 11:08 AM, Kristoffer Ödmark <kristofferodmar...@gmail.com <mailto:kristofferodmar...@gmail.com>> wrote: There is still some functionality in it that is missing from what I gather. I do like the

Re: [Kicad-developers] Default Canvas for v5

There is still some functionality in it that is missing from what I gather. I do like the idea that just having an "enable hw acceleration" button or switch in the nagdialog, it feels proffessional, and most people will try it i think. Also, these problems seems like there could be some

Re: [Kicad-developers] Default Canvas for v5

My personal preference would be to show the nag-dialog only if the user has upgraded from a previous version of kicad, and only once. New users wouldnt have to be informed, and if possible fallback a fallback to the cairo solution instead of falling back to legacy might be tempting. Could

Re: [Kicad-developers] Default Canvas for v5

The power of defaults ;) This is also something I have encountered has turned a lot of users away, because when they try it, they dont really like the setup. So even if they can change it, they give up before they realize they can. -Kristoffer On 12/30/2017 10:30 PM, Chris Pavlina wrote:

Re: [Kicad-developers] Intel video drivers on linux

Honestly I am using the intel driver more often than the built in nvidia in my ux302 zenbook. Mostly to get better battery time from it. I find it very stable. I have a friend who recently got a Xiaomi pro 15.6 inch laptop and runs linux on it, it comes with both nvidia and intel drivers and

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

On 2017-12-20 16:58, Jon Evans wrote: For user experience, it might be a bit annoying to have to remember to insert a separator character if you want one to appear. So I guess one question would be: do we want to support no separator character at all?  Or default to a dot if the user doesn't

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

/2017 02:29 PM, kristoffer Ödmark wrote: Then dont use a underscore? If the dot is not inserted, nothing hinders you from not putting a underscore there? On 2017-12-20 13:32, Wayne Stambaugh wrote: Using an underscore as a replacement for the period will add another reserved character which will add

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

and/or require quoting when saving to the file which makes the file format less readable. On 12/19/2017 4:52 PM, kristoffer Ödmark wrote: Why would this be problematic for users like you to be able to chose whichever character you fancy instead? On 2017-12-19 22:03, Wayne Stambaugh wrote: This would

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

Why would this be problematic for users like you to be able to chose whichever character you fancy instead? On 2017-12-19 22:03, Wayne Stambaugh wrote: This would be problematic for users like me who use the underscore character in names for readability. On 12/19/2017 3:57 PM, kristoffer

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

Another thing, maybe not force the usage of the dot ".", I would rather like to force the dot myself, or be able to use "_" or whatever i fancy. So instead putting CH0.{ADC}, or CH0_{ADC}. - Kristoffer On 2017-12-19 21:28, Jon Evans wrote: Hi Marco, Thanks a lot for your feedback. I agree

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

Personally I think this feature would be huge boost for readability. Most people who will review a schematic knows what nets are on a USB connection, or a SPI connection or similar. I see them as an abbreviation, just the same as everyone knows what USB is, even though it stands for Universal

[Kicad-developers] Information regarding unit tests.

Hello! I just went through the ML and the docs. I found some tests in the qa folder that seemed related to the python scripting interface and some different documentation regarding testability from tomasz and the thread "simple C++ tests". Has there been added anything for doing tests in cpp

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

, so there is nothing preventing you from doing so. I would rather not impose such constraint on aliases, but I am interested in other opinions. Regards, Orson On 12/14/2017 01:09 PM, kristoffer Ödmark wrote: Maybe we could adapt from c++ here? having the notation instead of {ALIAS}, the same way

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

Maybe we could adapt from c++ here? having the notation instead of {ALIAS}, the same way c++ uses templates. one could do MEMORY{ D[15..0]}. And get MEMORY.OE MEMORY.WE and MEMORY D15 etc. Just to be more clear that it is an alias and not a net-name. - Kristoffer On 2017-12-14 12:43,

Re: [Kicad-developers] Simulator towards 5.0

I think that this message is important, and I feel a decision on this matter features has to be done by the project manager, basically give a pointer to what should be used to as far extent as possible. Wayne, this is a package dev that wants to know this and while I do not know who are

Re: [Kicad-developers] Simulator towards 5.0

option (which apparently on arch linux it is not), setting KICAD_SPICE=ON will fail during build config. It is up to the system package developer to determine if kicad should be built with spice support. On 12/6/2017 9:04 AM, Kristoffer Ödmark wrote: Are we not in feature freeze, the features

Re: [Kicad-developers] Simulator towards 5.0

I am still lacking a clear documentation about which options are inte official releases, or planned to be. On 2017-12-07 09:27, Maciej Sumiński wrote: The attached patch lists options that have "KICAD" in their name when calling CMake: -- Build configuration: -- KICAD_BIN=bin --

Re: [Kicad-developers] Simulator towards 5.0

the default build should reflect the ones being run by the less savvy users. -Kristoffer On 12/06/2017 11:31 AM, Simon Richter wrote: Hi, On 06.12.2017 11:12, Kristoffer Ödmark wrote: I do not see why anyone is even objecting to this? Where is the logic at having a default build that does

Re: [Kicad-developers] Simulator towards 5.0

I sent the wrong patch before attached the correct now. Silently compiling something else then what was expected is much much worse than failing. I do not see why anyone is even objecting to this? Where is the logic at having a default build that does not correspond to any of the official

Re: [Kicad-developers] Simulator towards 5.0

I would personally also like to see these options enabled by default. It makes it easier for a packager to be convinced what options to enable... :) 2017-12-05 15:05 GMT+01:00 Kristoffer Ödmark <kristofferodmar...@gmail.com <mailto:kristofferodmar...@gmail.com>>: I check

Re: [Kicad-developers] Simulator towards 5.0

to see these options enabled by default. It makes it easier for a packager to be convinced what options to enable... :) 2017-12-05 15:05 GMT+01:00 Kristoffer Ödmark <kristofferodmar...@gmail.com <mailto:kristofferodmar...@gmail.com>>: I checked the default package in Ubun

Re: [Kicad-developers] Simulator towards 5.0

to enable... :) 2017-12-05 15:05 GMT+01:00 Kristoffer Ödmark <kristofferodmar...@gmail.com <mailto:kristofferodmar...@gmail.com>>: I checked the default package in Ubuntu ppa through a friend. Indeed all of this is enabled. Here I attach a small patch that changes the default c

Re: [Kicad-developers] Simulator towards 5.0

for a novice will look, maybe it will reduce some initial confusion for someone. - Kristoffer On 12/04/2017 10:19 PM, Nick Østergaard wrote: Den 4. dec. 2017 18.50 skrev "kristoffer Ödmark" <kristofferodmar...@gmail.com <mailto:kristofferodmar...@gmail.com>>:

Re: [Kicad-developers] Simulator towards 5.0

Hi! On 2017-12-04 21:33, Maciej Suminski wrote: As far as I remember the simulator is enabled in Windows nightlies since October last year. Does not it work for you? To be honest, I havent tested the windows version, I dont really run a windows installation anywhere. I just falsely assumed If

Re: [Kicad-developers] Hierarchical Schematic to contain link to pcb

implement. Steven On 13/11/17 23:11, Kristoffer Ödmark wrote: Hello! I suspect this has been discussed before in different formats. But anyway. What would be the major problems or concerns with allowing a schematic to have a pcb as file to include? What I mean is that the same way we let a s

Re: [Kicad-developers] COMPONENT_TREE performance

What are the roadblocks besides the huge amount of programming effort required for this? Im on linux and I would like this as well. - Kristoffer On 2017-12-04 19:09, Bernhard Stegmaier wrote: On 4. Dec 2017, at 18:55, Chris Pavlina wrote: On Mon, Dec 04, 2017 at

Re: [Kicad-developers] Simulator towards 5.0

, kristoffer Ödmark wrote: Okay, My suggestions: 1. Enable the spice simulator by default and start shipping it with windows nightlies. This way we will find much more bugs. Because I doubt everyone is running with the simulator on even on nightlies. Same goes for the OCE and step stuff. This I see

Re: [Kicad-developers] Simulator towards 5.0

On 2017-12-04 15:22, Tomasz Wlostowski wrote: Kristoffer, You're very welcome to specify how you'd like to have the Spice-related fields organized - but remember it's not only the integrated ngspice simulator that relies on them. People have been exporting PSpice netlists from Kicad for a

[Kicad-developers] Simulator towards 5.0

Hello! What is the official status on the simulator part going towards v5? Will it be included or not. I just tried it and I really like the features in it, its basically ready to be used as a simulator and compete and conquer ltspice. What i do not like is the way it stores information, in

Re: [Kicad-developers] Signal integrity simulation within Kicad

This is very interesting indeed! Would you keep us updated of your progress? :D - Kristoffer On 11/29/2017 10:55 PM, Andreas Buhr wrote: On 11/29/2017 08:07 PM, Tomasz Wlostowski wrote: On 29/11/17 19:09, Andreas Buhr wrote: [snip] The input which my solver needs would be an array of

Re: [Kicad-developers] Some tests.

Heikki, That is not blackmailing, it is the exact same rules everyone else that is a kicad developer or wants to be is expected to follow. It makes working on the same project easier. Tom did not mean to kick you out of the mailing list, he meant that your code is not going to be put into

Re: [Kicad-developers] Polygons: should have outline mode to draw Edge.Cuts

Could not a quick fix for this be to attach the "magnetic" functionality that exists when routing to the endpoints of a Edge.Cuts line? On 11/21/2017 04:00 PM, Thomas Pointhuber wrote: Hi, as librarian I would also note that an improved Edge:Cuts behaviour should take in account footprints

[Kicad-developers] Hierarchical Schematic to contain link to pcb

Hello! I suspect this has been discussed before in different formats. But anyway. What would be the major problems or concerns with allowing a schematic to have a pcb as file to include? What I mean is that the same way we let a symbol have a footprint in eeschema, we let a schematic point to

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

ountered this before. > > On Fri, Nov 10, 2017 at 7:09 AM, Oliver Walters > <oliver.henry.walt...@gmail.com> wrote: >> >> I like 2) or 3) - I think that a major release is a good time to fix such >> a bug. >> >> Would you like me to add a patch implementi

Re: [Kicad-developers] [REQUEST] Default library install location

Personally I think this is a nice solution http://1.bp.blogspot.com/-3u-eixTrMbI/VDWb25kPNkI/A-g/0qn7ehRq4Mo/s1600/ReadOnly.PNG Very helpful, instead of the "Edit document" button, there could be something such as "Copy to user-library for edit". - Kristoffer On 11/09/2017 02:02 AM,

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

Currently the footprints arent compatible anyway i guess, they support more than 4.07 footprints do. So option 2 is my preferred solution. On 11/09/2017 12:51 PM, jp charras wrote: Le 09/11/2017 à 11:12, Kristoffer Ödmark a écrit : My 2 cents is that the headaches of storing values in mixed

Re: [Kicad-developers] Update of KiCad documentation?

. Then everyone can contribute easily and we can track it for the documentation, where the info is to be used anyways. For now label them new_kicad_feature if it is. 2017-11-09 10:54 GMT+01:00 Kristoffer Ödmark <kristofferodmar...@gmail.com <mailto:kristofferodmar...@gmail.com>>:

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

My 2 cents is that the headaches of storing values in mixed units, without indication of which unit they are stored as is a huge drawback for readability of the saved files and for maintainability. Also I think the proposed new tag offset is a good idea, since the libraries can be gradually

Re: [Kicad-developers] Update of KiCad documentation?

AM, Kristoffer Ödmark wrote: I think starting small would be best in this case. The least needed would be a "News" File, that is always refering to kicad stable. I propose the same way that patches with policy errors are rejected, patches that introduces new functionality or change o

Re: [Kicad-developers] [FEATURE] Array 3D models

To be fair, as it stands now, even if it is "only" for the pin headers, this is close to half of the 3d library size as of now. The pin headers can now be of an arbitrary size as well. Someone can now create a 4x6 pin header for example, and the current footprints can be converted to this

Re: [Kicad-developers] Update of KiCad documentation?

I think starting small would be best in this case. The least needed would be a "News" File, that is always refering to kicad stable. I propose the same way that patches with policy errors are rejected, patches that introduces new functionality or change of existing functionality are required

Re: [Kicad-developers] Update of KiCad documentation? (when to release kicad-5.0)

How does the documentation work now? Do we have any standardisation on how to document? On 11/01/2017 09:53 AM, Maciej Sumiński wrote: On 11/01/2017 09:40 AM, Carsten Schoenert wrote: Hello Wayne, Am 31.10.2017 um 13:06 schrieb Wayne Stambaugh: We are very close to a feature freeze and

Re: [Kicad-developers] [PATCH] Nest level error, causes problems with git

Whoops, managed to mess upp the coding style while only changing 3 lines.. not very good Updated On 10/27/2017 11:03 AM, Kristoffer Ödmark wrote: Hi! I found that the nest level when saving stuff is wrong ( error from the clipboard plugin ). This patch fixes that so that version control

[Kicad-developers] [PATCH] Nest level error, causes problems with git

Hi! I found that the nest level when saving stuff is wrong ( error from the clipboard plugin ). This patch fixes that so that version control systems doesnt generate large diffs when saving. -- -Kristoffer >From d07b38f27509533de087a089febfe68dd8fb58db Mon Sep 17 00:00:00 2001 From:

Re: [Kicad-developers] Datasheet confusion

Seems there are no major objections :) Bumping this so it doesnt get lost in history :) On 10/19/2017 09:57 PM, Wayne Stambaugh wrote: Looks good to me. If there are no major objections I will merge this patch. On 10/19/2017 11:53 AM, Kristoffer Ödmark wrote: I tested

  1   2   3   >