Re: [Kicad-developers] [Kicad source code]

Hi Andrea, Have a look at SCH_DRAWING_TOOLS::PlaceComponent(). Cheers, Jeff. > On 3 Feb 2020, at 18:08, Andrea Martí wrote: > > Hi, > I posted this question on the kicad forums website and someone directed me to > the developer's mailing list instead of that forum. I have been looking into

[Kicad-developers] [Kicad source code]

Hi, I posted this question on the kicad forums website and someone directed me to the developer's mailing list instead of that forum. I have been looking into the source code in order to develop my own project and I have a question regarding the Eeschema source code. In particular, is there a

Re: [Kicad-developers] macos notarization status

You are right, Bernhard, that it's weird. I found an issue where I can reproducibly segfault Apple's codesign! Ian, maybe hold off on anything drastic re symlinks until I do some more experimentation. It's possible the question was relayed incorrectly at WWDC and our setup could work fine...

Re: [Kicad-developers] macos notarization status

I think `kicad --eeschema` would fix this part of the notarization/signing issue, Ian. I share Bernhard's concern about letting it work from the GUI too. I wish I knew Apple's long term plans here. Can we continue to work on signing and notarization as a low priority thing, or is the next

Re: [Kicad-developers] macos notarization status

OK, I see… this is weird. My understanding from what I read in the documentation was, that it should sign everything in the top-level bundle (kicad.app) including sub-apps you might have in kicad.app/Contents/Applications. Regards, Bernhard > On 3. Feb 2020, at 16:47, Adam Wolf wrote: > > I

Re: [Kicad-developers] macos notarization status

Alright folks, based on this conversation I have at least one or two more tests to do regarding symlinks. Second, I'll do some investigating to see what Apple has changed with notarization today. If we see users having issues, we can assure them that we're working on it. Third, I'll update the

Re: [Kicad-developers] Gitlab issue tracker

Never mind. It did close it, just with a time lag from the other changes. Cheers, Jeff. > On 3 Feb 2020, at 15:45, Ian McInerney wrote: > > It should automatically close them when you do that. > > -Ian > > On Mon, Feb 3, 2020 at 3:29 PM Jeff Young > wrote: > I just

Re: [Kicad-developers] macos notarization status

I am not notarizing the DMGs. While this is possible, it has not been necessary so far. When I tried notarizing kicad.app but not the others, when I move to a new computer, it complains that eeschema.app is not notarized. The problem is not putting the signed kicad.app into an unsigned dmg. On

Re: [Kicad-developers] Gitlab issue tracker

It should automatically close them when you do that. -Ian On Mon, Feb 3, 2020 at 3:29 PM Jeff Young wrote: > I just used: > >/duplicate #2402 > > to mark a bug as a duplicate. Cool. > > But it didn’t close it. Do we want duplicates closed, or was that just > how Launchpad did it? > >

[Kicad-developers] Gitlab issue tracker

I just used: /duplicate #2402 to mark a bug as a duplicate. Cool. But it didn’t close it. Do we want duplicates closed, or was that just how Launchpad did it? Cheers, Jeff. ___ Mailing list: https://launchpad.net/~kicad-developers Post to

Re: [Kicad-developers] macos notarization status

Theoretically yes, I guess. From cmdline it probably would solve the problem and the links together with those standalone-apps could be removed. But, from a non-cmdline user perspective: Is there a way to “wrap” (?) this call to main kicad.app with some parameter into a nice icon that just

Re: [Kicad-developers] macos notarization status

Adam (et al.), If you didn't have to package the single top executable (e.g. eeschema, pcbnew) would this allow you to remove the symlinks? We have been discussing adding command line flags to the main kicad executable to launch the various frames as standalone (e.g. `kicad --eeschema` would

[Kicad-developers] New docked window, hotkeys stolen by KiCAD

KiCommand creates a Pane managed by the AUI Manager. manager = wx.aui.AuiManager.GetManager(parent) manager.AddPane( self.__class__.g, pane ) However, when this pane is docked, KiCAD steals hotkeys, like the key “o” and prevents the user from entering that key into the KiCommand pane. I had

Re: [Kicad-developers] macos notarization status

Hi Adam, I am also no fan of the symlinks, but having a different approach will be probably some work. I had someone ask if what we do would work during WWDC and I was told it would not work. I consistently get "the signature is invalid" when signing while we have symlinks, and when I remove

Re: [Kicad-developers] macos notarization status

Holger, There already is some OS specific loading stuff in eeschema.cpp. Any dylibs can probably lice where they are, but plaintext files like ... I think ciderinit, will have to move. I'll setup a gitlab issue for us to coordinate Thanks! Adam On Mon, Feb 3, 2020, 4:44 AM Holger Vogt

Re: [Kicad-developers] macos notarization status

Bernhard, I have no personal vendetta against the symlinks. I had someone ask if what we do would work during WWDC and I was told it would not work. I consistently get "the signature is invalid" when signing while we have symlinks, and when I remove the symlinks and just sign KiCad.app this

Re: [Kicad-developers] macos notarization status

I will have a look at the ngspice issues. I guess that the only files that we really need in the distribution (besides the ngspice dylib) are the codemodel *.cm files. They are also dylibs to be loaded dynamically into ngspice. The commands to load these files (including path information) is