Re: [Kicad-developers] 5.1.5 release tag

I set rc1 to build earlier today. I can upload it when it finishes and if folks can test it, I can easily rebuild as 5.1.5 tomorrow! On Wed, Nov 20, 2019, 4:59 PM Wayne Stambaugh wrote: > I'm willing to push the release date up if the MacOS package is ready. > Just let me know. > > Cheers, > >

Re: [Kicad-developers] 5.1.5 release tag

On Mittwoch, 20. November 2019 19:33:53 CET Steven A. Falco wrote: > Fedora Rawhide has 5.1.5 now. Fedora 30 and 31 will have 5.1.5 in a week or > so, depending on whether we get any karma. > > Also of note - as of 5.1.5 we are now using OCC on all builds. OCE is no > longer needed for current

Re: [Kicad-developers] 5.1.5 release tag

I'm willing to push the release date up if the MacOS package is ready. Just let me know. Cheers, Wayne On 11/20/19 5:46 PM, Nick Østergaard wrote: > 5.1.5 is fairly well rolled out now, thanks to various good people :) > > To make the release official, I think we are only needing the macos >

Re: [Kicad-developers] 5.1.5 release tag

5.1.5 is fairly well rolled out now, thanks to various good people :) To make the release official, I think we are only needing the macos build. @Adam Wolf if you need any help, please speak up. Nick On Wed, 20 Nov 2019 at 19:33, Steven A. Falco wrote: > > Fedora Rawhide has 5.1.5 now.

Re: [Kicad-developers] Back annotate references from PCB

On 11/7/19 5:06 AM, Alexander Shuklin wrote: > Hi, > is it alright to answer anybody in one letter? > First of all, don't take amiss if I keep silence for a day, as I have > 2 little children and at the best case I have couple of hours a day on > my own. > > On Wed, 6 Nov 2019 at 16:27, Wayne

Re: [Kicad-developers] [PATCH v5] eeschema: Allow hierarchy navigator to stay open

Le lun. 11 nov. 2019 à 16:59, Franck Jullien a écrit : > > Hi again ! > > I now have fixed the commit message to include a tag (ADD). > > Franck. If it can help the review, you can find this patch on github: https://github.com/fjullien/kicad/commit/350f5fc0ad7c128c3d152317297468a7b9516e62

Re: [Kicad-developers] suggestion: draw text selection as simple rectangle

On 20.11.19 20:37, Jonatan Liljedahl wrote: If yes, does it need to be configurable? We had a color blind fellow designer. The schematic entry (ACE-Plus) derived its colors from the library - no chance for user setup ... ___ Mailing list:

Re: [Kicad-developers] suggestion: draw text selection as simple rectangle

Jonatan, have you read this forum discussion: https://forum.kicad.info/t/selection-highlighting-in-development-version/18694 ? Eeli Kaikkonen ke 20. marrask. 2019 klo 21.37 Jonatan Liljedahl (li...@kymatica.com) kirjoitti: > Hi list, > Here's another suggestion, to draw the boundary box of

[Kicad-developers] suggestion: draw text selection as simple rectangle

Hi list, Here's another suggestion, to draw the boundary box of selected text instead of drawing the text itself with the thick selection shadow. See attached screenshot. Is this a good idea? If yes, does it need to be configurable? Personally I find it a lot easier and visually less tiresome.

Re: [Kicad-developers] eeschema selection appearance

On Wed, Nov 20, 2019 at 5:55 PM Seth Hillbrand wrote: > On 11/20/19 7:11 AM, Jonatan Liljedahl wrote: > > Ok, I'll look into making it configurable. However, I find the current > default appearance hard to use, so maybe one could consider changing > the defaults in that case? > > Everyone likes

Re: [Kicad-developers] 5.1.5 release tag

Fedora Rawhide has 5.1.5 now. Fedora 30 and 31 will have 5.1.5 in a week or so, depending on whether we get any karma. Also of note - as of 5.1.5 we are now using OCC on all builds. OCE is no longer needed for current Fedora releases. Steve On 11/17/19 11:56 AM, Rene Pöschl wrote: >

Re: [Kicad-developers] Fwd: eeschema selection appearance

Ruth, brilliant! This behavior in commercial apps has irritated me for decades. *Drew Van Zandt* On Wed, Nov 20, 2019 at 12:29 PM Ian McInerney wrote: > (Ruth, I think you meant to send this to the entire list). > > -- Forwarded message - > From: Ruth Ivimey-Cook > Date:

[Kicad-developers] Fwd: eeschema selection appearance

(Ruth, I think you meant to send this to the entire list). -- Forwarded message - From: Ruth Ivimey-Cook Date: Wed, Nov 20, 2019 at 5:23 PM Subject: Re: [Kicad-developers] eeschema selection appearance To: This looks like an improvement on v5.1, anyway. Thanks! A side request

Re: [Kicad-developers] eeschema selection appearance

On 11/20/19 7:11 AM, Jonatan Liljedahl wrote: Ok, I'll look into making it configurable. However, I find the current default appearance hard to use, so maybe one could consider changing the defaults in that case? Everyone likes to have their preferences as the default.  This is not a useful

Re: [Kicad-developers] Building current master fails

I do the same thing. Trying to switch between the master and 5.1 branches to work is not very productive. On 11/20/19 11:13 AM, Ian McInerney wrote: > I keep 5.1 and master in separate worktrees because I find that the > compile time if you switch branches is excruciatingly painful (we have >

Re: [Kicad-developers] 5.1.5 release tag

And there is already 1200 downloads since yesterday... Le 20/11/2019 à 17:17, Jean-Samuel Reynaud a écrit : > Hi All, > > Version 5.1.5 are now available on the PPA (ubuntu). > > > Le 18/11/2019 à 12:06, Nick Østergaard a écrit : >> Everything is tagged. >> >> @adam, you should be able to

Re: [Kicad-developers] 5.1.5 release tag

Hi All, Version 5.1.5 are now available on the PPA (ubuntu). Le 18/11/2019 à 12:06, Nick Østergaard a écrit : > Everything is tagged. > > @adam, you should be able to bump the macos releases as well. > > søn. 17. nov. 2019 17.57 skrev Rene Pöschl >: > >

Re: [Kicad-developers] Building current master fails

I keep 5.1 and master in separate worktrees because I find that the compile time if you switch branches is excruciatingly painful (we have some differences in the base header files now that basically mean an almost full recompile). That is probably why I never saw this issue. -Ian On Wed, Nov

Re: [Kicad-developers] Building current master fails

This will do it in one step: find . -name *_lexer.h -delete > On 20 Nov 2019, at 15:57, Adam Wolf wrote: > > Thanks for this! I have just been cleaning a lot.. :) > > On Wed, Nov 20, 2019 at 9:16 AM Jeff Young wrote: >> >> I switch between 5.1 and master and back in the same tree. You have

Re: [Kicad-developers] Building current master fails

Thanks for this! I have just been cleaning a lot.. :) On Wed, Nov 20, 2019 at 9:16 AM Jeff Young wrote: > > I switch between 5.1 and master and back in the same tree. You have to run > the clean each time you go from 5.1 to master. > > On 20 Nov 2019, at 14:34, Ian McInerney wrote: > > Thats

Re: [Kicad-developers] Building current master fails

I switch between 5.1 and master and back in the same tree. You have to run the clean each time you go from 5.1 to master. > On 20 Nov 2019, at 14:34, Ian McInerney wrote: > > Thats correct, all those lexer files should now be in the build folder. I > think that only the board file has had

Re: [Kicad-developers] Building current master fails

Ah, yes I have switched between 5.1 and master so that would probably be it then! Thanks. On Wed, Nov 20, 2019 at 3:34 PM Ian McInerney wrote: > > Thats correct, all those lexer files should now be in the build folder. I > think that only the board file has had new keywords added, so it would

Re: [Kicad-developers] eeschema selection appearance

Ok, I'll look into making it configurable. However, I find the current default appearance hard to use, so maybe one could consider changing the defaults in that case? Not only does it make the text easily legible, but also the whole symbol less cluttered when selected. You can still select

Re: [Kicad-developers] Building current master fails

Thats correct, all those lexer files should now be in the build folder. I think that only the board file has had new keywords added, so it would be the only one that is different. Ok, so there is probably another cause of the files appearing. Did you switch branches between master and 5.1 and

Re: [Kicad-developers] eeschema selection appearance

I'm on the fence about the text highlighting, on the one hand not doing it does make it so the text is still easily legible when selected, but on the other it can be nice to show that it is part of the selected symbol. I think this would definitely be a case where making it a configurable option

Re: [Kicad-developers] eeschema selection appearance

On 2019-11-20 05:48, Jonatan Liljedahl wrote: Hi, I'm tweaking the appearance of the new selection, what do you think? Except a change of color, transparency and width, it also skips drawing the fields and pin labels of components. I think it gives a much cleaner look with less clutter. This

[Kicad-developers] eeschema selection appearance

Hi, I'm tweaking the appearance of the new selection, what do you think? Except a change of color, transparency and width, it also skips drawing the fields and pin labels of components. I think it gives a much cleaner look with less clutter. -- /Jonatan http://kymatica.com

Re: [Kicad-developers] KiCad Assembly at 36C3

Hi, On Wed, Nov 20, 2019 at 12:57:31PM +0100, Carlo Maragno wrote: > I saw that Seth was planning to do something similar at fosdem. Yes, I'm also going there, and that is probably where the interesting stuff happens, since there are people there with insight into the codebase and a general

Re: [Kicad-developers] KiCad Assembly at 36C3

Hi Simon, I saw that Seth was planning to do something similar at fosdem. It would be super cool to do the same thing at the congress. I for sure will bring my big laptop. Carlo On Wed, 20 Nov 2019, 12:28 Simon Richter, wrote: > Hi, > > On Tue, Nov 19, 2019 at 10:31:36PM +0100, Carlo

Re: [Kicad-developers] Building current master fails

Hi, I see. So then I assume all these should also not exist? $ ls include/*_lexer.h include/lib_table_lexer.h include/netlist_lexer.h include/page_layout_reader_lexer.h include/pcb_lexer.h include/pcb_plot_params_lexer.h Of these files, only pcb_lexer.h differed between include/ and

Re: [Kicad-developers] KiCad Assembly at 36C3

Hi, On Tue, Nov 19, 2019 at 10:31:36PM +0100, Carlo Maragno wrote: > an assembly is just a table and some power cords. It's meant to serve as a > base for people to gather and hack around. If there is a critical mass of people who want to do development work, I could bring two machines for

Re: [Kicad-developers] Building current master fails

Jonatan, The pcb_lexer.h in include/ shouldn't exist anymore. There was a switchover a few months ago in how that file was generated, and that change moved it into the build directory. As a consequence of that switchover, you need to clean out the stray files that existed from old build. Try

Re: [Kicad-developers] Building current master fails

It seems to build ok for linux on jenkins. Maybe double chevk you are not in a merge state or something. Also, please state the has of the version you are trying to build. ons. 20. nov. 2019 11.34 skrev Jonatan Liljedahl : > Hi, I'm trying to build the current master, cmake configured like

Re: [Kicad-developers] Building current master fails

include/pcb_lexer.h does not include T_copper_finish etc. However, build/common/pcb_lexer.h does! How come? I'm guessing the one in common is generated during build, but for some reason it picks the other one when including the header. On Wed, Nov 20, 2019 at 11:34 AM Jonatan Liljedahl wrote: >

[Kicad-developers] Building current master fails

Hi, I'm trying to build the current master, cmake configured like this: cmake -DNGSPICE_INCLUDE_DIR=/Users/lijon/Coding/kicad-mac-builder/build/ngspice-dest/include/ -DNGSPICE_LIBRARY=/Users/lijon/Coding/kicad-mac-builder/build/ngspice-dest/lib/libngspice.dylib -DKICAD_USE_OCE=OFF