[Kicad-developers] Revert 9bc2bb2 "Fixed a VIEW_ITEM memory leak"

I reverted commit 9bc2bb2 "Fixed a VIEW_ITEM memory leak", which caused a segfault: https://bugs.launchpad.net/kicad/+bug/1656481 Maybe we should be using smart pointers in these data structures... ;) -- Chris ___ Mailing list:

Re: [Kicad-developers] Group selection idea

Yes, It is a complex issue. Anyway, I attach 2 patches here. 0001 is the selectiongroup thing you saw in the video. 0002 is a patch adding a (group %s) to the kicad_pcb format, making groups persistant. If you ever use selection groups for something, you will notice it is very nice to have

[Kicad-developers] Jenkins build is back to normal : kicad-noscript-fedora20 #1474

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help :

Re: [Kicad-developers] Group selection idea

The more I think about it, the more complex this issue becomes. How do you instantiate a group multiple times (a hierarchy) in a board and maintain proper footprint reference designators and net connectivity? I think the issue is far more complex than everyone realizes. This is the exact same

[Kicad-developers] Jenkins build is back to normal : kicad-qa #2184

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help :

Re: [Kicad-developers] Standard symbol field names initiative

Sounds great Wayne, I'll give this some time to settle down and update this thread when I have more to show. On 13 January 2017 at 21:31, Wayne Stambaugh wrote: > On 1/13/2017 9:20 AM, Kaspar Emanuel wrote: > > > > On 13 January 2017 at 13:35, Wayne Stambaugh

Re: [Kicad-developers] Standard symbol field names initiative

On 1/13/2017 9:20 AM, Kaspar Emanuel wrote: > > On 13 January 2017 at 13:35, Wayne Stambaugh > wrote: > > Ithink using separate fields > would be cleaner and more reliable in the long run. > > > Yes, I am coming over to this point of

[Kicad-developers] Build failed in Jenkins: kicad-qa #2183

See Changes: [Maciej Suminski] Restored cursor in OpenGL canvas (still an issue with subpixel AA) [Maciej Suminski] Added a missing #include directive -- Started by user Nick Ostergaard Building

Re: [Kicad-developers] Group selection idea

Hi Kristoffer. I cannot apply your patches to the current version. Can you rebuild them ? Thanks. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

[Kicad-developers] Build failed in Jenkins: kicad-noscript-fedora20 #1473

See Changes: [Maciej Suminski] More code formatting [Maciej Suminski] checkGlError() may throw exceptions or display an error message [Maciej Suminski] Initialize fields in COMPOSITOR [Maciej Suminski] Alternative way of

Re: [Kicad-developers] Group selection idea

The technicalities of creating nested grouping is not the biggest problem. The real headache I would say is how to get this intuitive and how to present this to the user. The current implementation everyone can agree is useful and not that hard to understand/redo/change. I would suggest I fix the

[Kicad-developers] Build failed in Jenkins: kicad-noscript-fedora20 #1472

See -- Started by upstream project "linux-kicad-full-gcc-head" build number 1684 originally caused by: Started by an SCM change Building remotely on fedora21 (linux hugo fedora) in workspace

[Kicad-developers] Build failed in Jenkins: kicad-qa #2182

See Changes: [Maciej Suminski] Change exception message time from wxString to std::string -- Started by an SCM change Building remotely on debian8 (gcc clang linux) in workspace

[Kicad-developers] Build failed in Jenkins: kicad-qa #2181

See Changes: [Maciej Suminski] More code formatting [Maciej Suminski] checkGlError() may throw exceptions or display an error message [Maciej Suminski] Initialize fields in COMPOSITOR [Maciej Suminski] Alternative way of handling OpenGL

Re: [Kicad-developers] Group selection idea

Hi Kristoffer, Please consider the following ideas, perhaps you will find it useful: * Create a PCB_GROUP class inheriting from BOARD_ITEM_CONTAINER As BOARD_ITEM_CONTAINER is also a BOARD_ITEM, you get an easy way of creating nested groups. This also enables selecting a group with the

Re: [Kicad-developers] Group selection idea

Okay, got it. For the group selection thing, I did some quick tests today, and only letting board items belong to one group at a time seems like a good way, letting them belong to multiple groups gave me a headache in how to implement any way of handling the groups. This would then change

Re: [Kicad-developers] Standard symbol field names initiative

On 13 January 2017 at 13:35, Wayne Stambaugh wrote: > Ithink using separate fields > would be cleaner and more reliable in the long run. > Yes, I am coming over to this point of view. I just quite liked the compactness and clarity of the initial proposal but it might not

Re: [Kicad-developers] Standard symbol field names initiative

Hello, Kaspar! On 2017-01-13 12:50, Kaspar Emanuel wrote: > Hi all, > > I have started an initiative for external tools to agree on a few default > field names in schematics. Full details in the forum where you can also > propose amendments and register your preference. > >

[Kicad-developers] Design Reuse - Multichannel Layout (was: Re: Group selection idea)

Hello, Kristoffer, Wayne, friends... Last night, I was drafting some rough concept based on my experience and based on my "ideal" dream of doing things. Just a few notes from my side: - We need proper names for the things we implement. Physical Design Reuse (PDR) is just one example. channel,

Re: [Kicad-developers] Standard symbol field names initiative

Hi Kaspar, I applaud your efforts here but you should heed the warnings about using a colon as a separator within a field. I think using separate fields would be cleaner and more reliable in the long run. There are a lot of users who would like atomic symbols but no one can ever seem to agree

Re: [Kicad-developers] Group selection idea

Kristoffer, I was merely talking about getting your initial implementation correct in Pcbnew to prevent issues with the full implementation down the road. While I'm OK with opening up a full design specification, I think it's a bit premature and will distract us from the immediate work at hand.

[Kicad-developers] Standard symbol field names initiative

Hi all, I have started an initiative for external tools to agree on a few default field names in schematics. Full details in the forum where you can also propose amendments and register your preference. https://forum.kicad.info/t/standard-symbol-field-names-initiative/4870 Cheers, Kaspar