I've installed this build and observed the the eeschema Library Editor hanging quite regularly. It is generally after a mouse click (left or right?) when I'm placing pins. I continually save after every minor change so I can reload, but it is very frustrating
Are there any later builds that address this issue ??
The problem seems to show up if I launch eeschema from the kicad.app launcher, then edit schematic symbols.
If I launch eeschema directly from the Finder then the everything is ok -- well at least the problem happens far less often or is not exposed.
Try launching eeschema from kikad.app, the edit a component -- add pins, right click on pins, background, etc, add more pins, etc. Hopefully it hangs for you too
This is a bug well known in debug builds.
Please if is possible use it standalone, if no more bugs and evident problems will show.
I'll make a release build to fix also this problem.
I'm happy that those are the problems spotted on the OSX port
You could always upload both builds -- a debug build and a snapshot build (testing release) so that users can use both. e.g. use the testing build, then if problems are noticed, use the debug build to gather more info. Just a thought
When i try to edit a component from a library i get this error :
How to reproduce :
Go to library editor
Select active library. Click on load and edit a component in the library, select the component and click on OK
./src/osx/carbon/dcclient.cpp(184): assert "window->MacGetCGContextRef() != NULL" failed in wxPaintDCImpl(): using wxPaintDC without being in a native paint event
Call stack:
[00] wxNativeDCFactory::CreatePaintDC(wxPaintDC*, wxWindow*)
[01] wxPaintDC::wxPaintDC(wxWindow*)
[02] wxScrollHelperBase::HandleOnPaint(wxPaintEvent&)
[03] wxScrollHelperEvtHandler::ProcessEvent(wxEvent&)
[04] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[05] wxWindowBase::HandleWindowEvent(wxEvent&) const
[06] wxWindow::MacDoRedraw(long)
[07] wxWidgetCocoaImpl::drawRect(void*, NSView*, void*)
[08] wxOSX_drawRect(NSView*, objc_selector*, CGRect)
[09] -[NSView _drawRect:clip:]
[10] -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:]
[11] -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
[12] -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
[13] -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
[14] -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
[15] -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:]
[16] -[NSView displayIfNeeded]
[17] wxNonOwnedWindowCocoaImpl::Update()
[18] wxNonOwnedWindow::Update()
[19] wxWindow::Update()
[20] wxStatusBar::DoUpdateStatusText(int)
Do you want to stop the program?
You can also choose [Cancel] to suppress further warnings.
I installed this version on Mountain Lion and I have a problem with cvpcb.
It gives me this error when I open the app:
http://d.pr/i/iyQL
and if I press cancel the app starts but the window is empty. I cannot see any of my components in the list:
http://d.pr/i/io3V
What should I do?
Thank you.
just in case you are still searching the bug, I have some hints were it could be. I would take a look myself, but my C++ knowledge is close to none. So, at least, I wanted to share, what I think I know about the problem's origin with you:
I discovered the same problem with recent revisions (self built) and I am quite sure that the revision Nr. 3742 (http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/revision/3742) introduced the first problems with Cvpcb on Mac OS X. Things have got worse since then as John and Andrea were reporting. In Rev. 3742 you were at least able to see your parts in the list. However, since then it is impossible to assign footprints to parts as Cvpcb is freezing after a double click on any footprint.
Since then, I stayed with a self compiled rev 3741 for my projects.
Hi,
I were working on the fix, you have spot half of the issue, the OSX compiler wants a bit more pedant code.
The rest of the issue was hidden in the cvpcb's OSX specific code.
I'm building the code and after some little tests i'll commit it.
Hoping you will be happy build the new release.
--
Marco