Open non-principal project files in main process, not as stand-alone apps.

Bug #1753071 reported by Andrey Kuznetsov on 2018-03-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

On macOS, eeschema appears to be launched as a standalone app, it creates a dock item.
I think eeschema should open like pcbnew, a window within KiCad app.

My mouse software has bind keys for KiCad, but the bind keys were not working because eeschema was showing as another app.

Application: kicad
Version: (5.0.0-rc2-dev-30-geb94d2f), release build
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
Platform: Mac OS X (Darwin 17.3.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.61.0
    Curl: 7.43.0
    Compiler: Clang 7.3.0 with C++ ABI 1002

Build settings:

Jeff Young (jeyjey) wrote :

@Andrey, did you click the big eeschema button in the Kicad main window, or double-click on a file in the project tree?

It /should/ open in the same app for the "principal" schema and board (ie: the ones with the same name as the project), and as a stand-alone window for other schemas/boards within the same project.

Andrey Kuznetsov (kandrey89) wrote :

OK, yes motherboard-stable.sch did not exist, I was opening motherboard.sch in a motherboard-stable project from the project tree.

I don't understand the purpose of opening sch files in a separate app from the project tree!
I think it should open within the KiCad app if opened from within KiCad, ie project tree.

Jeff Young (jeyjey) wrote :

I have some sympathy for that, but I'd have to research it a bit to make sure there isn't an architectural reason we do it that way.

Changed in kicad:
importance: Undecided → Wishlist
status: New → Triaged
summary: - Eeschema Launched as Standalone App from Inside KiCad
+ Open non-principal project files in main process, not as stand-alone
+ apps.
Wayne Stambaugh (stambaughw) wrote :

Actually there is a somewhat architecture reason. Inter and intra process communication between the schematic and board editors is undefined when you open a schematic (or board) that is not part of the current project so to prevent any issues do to undefined communications, we just don't allow opening non-project boards and schematics in a way that could cause problems. It's a fairly trick problem to solve since kicad is designed as a single document interface (SDI). We've talked in the past about converting to and MDI but there are far more important issues to fix at the moment.

Jeff Young (jeyjey) wrote :

Cool, I'll leave it on the wishlist for now.

If it's still there in a couple of years we can boot it as Won't Fix. ;)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers