Last time I worked with it was around 4.8. I don't know how stable those libraries are in Macworld but welcome peoples' two cents.Īlso, Qt is its own tongue in the same way that WinForms is - I still think it's a very good library, but we will need to start looking for a lot more knowledge in that realm.

If some users could comment on the examples provided here - we need to decide if their interpretation works well enough to resolve the incongruities we are observing now (bye bye libgdiplus.dylib) and would at the same time open the door for new possible messes with libqt and its cadre of related object files. Qt would likely require small amounts of Mac-specific code in the same general way we have to include Platform.IsMac now. It solves the problem of running UI code on different platforms pretty well, but it does expect you to fill in, for example, multiple event handlers to deal with WinForms, OSX, and 'Mono on non-OSX platforms' i.e.

Just an aside, I was/am wrong about Eto, for now it seems to be progressing.

Ksp mac 64 bit workaround