I installed the stable 4.0.2 from .dmg. (After frustrating hours of trying to build). Anyway, now the kicad windows open in a small size, when I maximise them, the content stay the same size.
The photo should make it clear. Also, the close button on the windows don’t work.
Are you starting PCBnew independently or via the Kicad app? Also, which version of OSX? I’ve recently installed 4.02 on a new computer (I normally use the nightly builds), so I am in a position to try and replicate your problem.
/martin
This is a bug which is typically seen when you have wxpython installed under brew and are using the official nightlies or are using self-builds with wx-python inside the application bundle.
If this is not the case let me know
@chamod, if you want to build the latest commit, and assuming you use homebrew, simply use my tap at https://github.com/metacollin/homebrew-kicad
It supports both stable and --HEAD versions, and safely builds wx and wxpython with the needed kicad patches for you. It will result in a version of KiCad that will not try to link to any other versions of wx and wxpython on your system, instead using patched versions just for KiCad. These are completely invisible, and not even separate formula, so all of this is done without littering your filesystem with extra patched versions of wx, keg-only or not.
It’s mostly because I wanted an easy, reliable way of tracking dev builds but with certain features turned on (I like menu icons, etc.). I’ve been using it to build KiCad for months now, and I in turn use those builds in a production environment (I like to live dangerously I guess). It’s pretty much made for OS X users like yourself trying to work with KiCad’s latest dev version.
Kinda same problem in Windows.
After cold start he makes no effort to rezise the window if you click the upper right resize icon.
He could at least make an effort to make some size change even if he has no size history, one can imagine that any change would be nice
But nope.
I know this is an old thread, but I see the same problem from a recent stable-4.0.0 to stable-4.0.2 dmg install on OS X. It works fine on a different computer that is more fresh and doesn’t have lots of things installed from homebrew. stable-4.0.0 was also great.
Is there a solution for the dmg install? The whole idea of this packaging is to not have these problems…