KiCad leaves tombstone process after plugin wx.App wx.CallAfter
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Fix Released
|
Unknown
|
Bug Description
1. some python plugins, i.e.
https:/
https:/
need to have gui-thread-safe invocation methods
2. this is best accomplished by using wx.App wx.CallAfter
https:/
https:/
3. however, that requires proper initialization of wx.App singleton
which currently occurs only when kicad_pyshell is invoked
https:/
4. attempt of initialization of wx.App in user plugin, i.e.
https:/
without first activating kicad_pyshell
results in KiCad leaving tombstone process after wx.App wx.CallAfter,
5. proposed solution:
https:/
kicad should automatically provision global wx.App instance by default,
similar to how it is done in kicad_pyshell
https:/
Changed in kicad: | |
importance: | Low → Unknown |
status: | Expired → Fix Released |
Makes sense.