Closed pgregson1 closed 5 years ago
MitjaNemec
commented
5 years ago This might be similar as #52.
Also on windows, you have to close the KiCad completely in order for log to get written.
Any it might be in different location (did you open different project and run a plugin, then opened different project and rerun the plugin. The log might be in the first project location.
Can you check this out and confirm it.
pgregson1
commented
5 years ago In answer to your questions,
"This might be similar as #52." It isn't. No replicate_layout.log file is written at all, neither with Place_footprints nor with Replicate_layout, and certainly not when both are used.
"Also on windows, you have to close the KiCad completely...". I'm using a Mac, not Windows. Exiting KiCad and re-opening it did not result in the writing of a replicate_layout.log file.
"Any it might be in different location (did...". No I didn't do that. However, I just ran my test case. For it, I ran Place_footprints first, and then Replicate_layout. I found the replicate_layout information at the end of the place_footprints.log file. That's a bug.
Best regards,
Peter
MitjaNemec
commented
5 years ago OK there is at least one bug in the logging code. The bug has been fixed so the plugins should generate .log files as one would expect. But as I can only test it on Windows platform I'd appreciate it if you can test it on macOS.
pgregson1
commented
5 years ago Will do. I am in the middle of something so I won't be able to get to it until this evening.
MitjaNemec
commented
5 years ago There is no hurry. Everybody has his own life with schedules, family, various commitments ... I can only be happy that you are contributing with testing. And if you would stop without notice, I can only say "it was fun while it lasted" but I'll be the last to judge you as I don have the slightest idea about you, your life and other circumstances. The same goes for me. I try to be prompt but sometimes it might take me a couple of weeks to respond, so please keep this in mind.
MitjaNemec
commented
5 years ago The logging issue should be solved now (https://github.com/MitjaNemec/Kicad_action_plugins/issues/36#issuecomment-495282294)
pgregson1
commented
5 years ago Thanks Mitja. Much appreciated.
Best regards,
Peter
On Jun 18, 2019, at 4:43 PM, Mitja Nemec notifications@github.com wrote:
Closed #51 https://github.com/MitjaNemec/Kicad_action_plugins/issues/51.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MitjaNemec/Kicad_action_plugins/issues/51?email_source=notifications&email_token=AADMHNJALCYZ6J365KIXXHDP3E3G7A5CNFSM4HOCR4FKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSBOVFDY#event-2422035087, or mute the thread https://github.com/notifications/unsubscribe-auth/AADMHNK3YOLU4IGAQ4MQU53P3E3G7ANCNFSM4HOCR4FA.
Hello,
I upgraded my computer from an older Mac Air running OS X 10.12.6 Sierra to MacBook Air running OS X 10.14.4 Mojave with 16 Gbytes of RAM.
The file "replicate_layout.log" for my current project is missing from my current computer. Ones from previous projects exist on my old computer, but none with dates more recent than March 9.
To determine where the problem was, I copied the KiCad project that produced a "replicate_layout.log" file on my previous computer to the new one. I then used the new machine to see if the "replicate_layout.log" would be produced when I ran "Place_footprints" and then "replicate_layout" again on a layout that was know to produce that file on the older machine. The log file was not created on the new machine.
So, things that have changed for that test case:
Things that have not changed:
I need to get the "replicate_layout.log" because I am trying to track down a few other issues. Any help would be greatly appreciated.
Best regards, Peter