John Hennig

No update, no. I cannot reproduce the error, so can't fix it. And using client-server mode seems to fix it anyway.

Just this week, in an entirely unrelated context (nothing to do with Comsol), I ran into a strange conflict with external libraries, which would *only* occur when the user had...

> How can I debug this? You can run the test suite with logging enabled: `python tools\test.py --log`. See the ReadMe's in the `tools` and `tests` folders for more details.

Seems like it. And apparently it crashes out of the Python session completely. You should be able to reproduce the crash in an interactive Python prompt. I just get the...

That makes sense if you were still in the same Python session. Were you? JPype seemed to crash in your test because you'd otherwise expect the log to continue like...

Well, I see no reason why this happens and have no idea how to fix that. It's almost certainly a bug in JPype, rather than Java, but would be difficult...

As far as I can tell, this is all expected behavior. As in: It works as documented. So I guess you wish the high-level Python API would support this use...

Yes, this is exactly the same as #135. And you already know the work-around: using the Java methods of the Comsol API directly. I've closed the other issue as it...

So the `Node` class we have in Python is essentially "trying to be" an abstraction of "whatever type of node class" there may be on the Java side. Of which...

Thanks for pointing this out. Yeah, absolutely, that *can* be added. Do you want to do it? I guess it's pretty straightforward to implement. Adding a meaningful test will be...