![]() ![]() ![]() imagej.init(mode="gui") could work on all platforms and have the macOS behavior of automatically showing the GUI and blocking, whereas imagej. So: thoughts? Ways to improve this, so we can finally put this issue to rest? Perhaps something as simple as adjusting the imagej.init API so it's consistent across platforms, but fails fast when certain modes are requested? E.g. I do not know how to avoid this-we could start new threads in Python, but I don't think it works to invoke nConsoleEventLoop() from non-main threads I tried via a new threading.Thread and got a SIGSEGV. More importantly, while this update makes imagej.init(headless=False) do something useful on macOS, it does something that is reasonable but different from what happens on Linux or Windows: A) it automatically shows the GUI (by calling ij.ui().showUI() under the hood), and B) it blocks the imagej.init call forever, because the main thread becomes tied up doing the console event loop, which is necessary for Java AWT to work.There are now two private functions _create_jvm and _create_gateway, whose names are still up for debate, which perform the two major parts of initialization.I have now pushed a couple of commits making the situation less horrible on macOS: 27aea88 and f54e59e. But still requires pyobjc to be installed. Much more concise than the OSXAWTwrapper script. The ZIP file you download (Image1.xx. As usual you are correct: that code is exactly what we needed, thank you. Taken from: home news docs download plugins resources list links OS X Installation o Installation o Memory o Upgrading o Drag and Drop o Known Problems o Running from the Command Line o About the Icon Installation Download ImageJ for Mac OS X from the Download page. One year later, finally had time to look at this again. ![]() backports.functools_lru_cache=1.6.1=py_0 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |