Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wx object is NoneType #1

Closed
KarlZeilhofer opened this issue May 5, 2018 · 7 comments
Closed

wx object is NoneType #1

KarlZeilhofer opened this issue May 5, 2018 · 7 comments

Comments

@KarlZeilhofer
Copy link

Hi,
I just tried your plugin on Linux Mint 18.1 with the nightly KiCad.
I get this message, when I click on the menu entry:

2018-05-05_003

Do you have any ideas, what I can do about it?

Greets,
Karl

To make the text searchable:

Traceback (most recent call last):

  File "/usr/share/kicad/scripting/plugins/layerviewset.py", line 390, in Run
    wx.GetTopLevelWindows()

AttributeError: 'NoneType' object has no attribute 'GetTopLevelWindows'
@HiGregSmith
Copy link
Owner

What version of KiCad are you using (and version of wxPython)?

I should be able to look at this in about 12 hours.

@HiGregSmith
Copy link
Owner

I just saw "nightly" so that answers that question. What about wxPython version?

@HiGregSmith
Copy link
Owner

I downloaded today's windows nightly and had to fix one of the constants from pcbnew. But I don't get the error you see regarding "wx" as NoneType. It seems like something is wrong with "import wx" but I'm not sure why there isn't an error on the "import wx" line.

@HiGregSmith
Copy link
Owner

Also uploaded a fix to the name/save function.

@HiGregSmith
Copy link
Owner

I have one windows user that had the same error as you reporting that the updated LayerViewSet works for them. Does this fix the issue in Linux?

@HiGregSmith
Copy link
Owner

I duplicated the error by initiating LayerViewSet from the External Tools menu. It failed with the same error message you report. I've uploaded a fix for this.

@KarlZeilhofer
Copy link
Author

That problem seems to be fixed now, but I got a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants