Karl Nelson
Karl Nelson
There is not enough context here to answer this issue. jaydebeapi is its own project that makes use of JPype and may be able to give you a more direct...
Your installation of JPype is incomplete or corrupt. When shipped jpype should have a directory called jpype containing ``__init__.py`` and many module files, a jar ``org.jpype.jar`` and C module ``_jpype.cpython-39-x86_64-win.dll``....
I would have to look to see if there is an image in azure that can be used to build the required wheel.
I believe that the ``_jpype`` is legacy, though it does serve a debugging purpose. There are many times that I have had to test an internal without wanting to include...
Oddly I do lot of development work with _jpype without hooks installed at all. Yes that means ``jpype.__init__`` is not run. That is my usual configuration when I am developing...
Shouldnt the method be public? JPype is restricted to public methods and fields.
It works for me if I put the proper decorators. Template arguments are type "java.lang.Object" for the purposes of Python. ``` @jpype.JImplements(Test2) class MyTest(object): @jpype.JOverride def onSuccess(self, result): pass @jpype.JOverride...
I believe there are some macros in jpype.gui for this (using AppHelper) though I have never used them. They were never documented and I am not sure if they ever...
Sadly I don't know how to begin debugging something like this. It looks like it fails on the first call to create a screen resource. What happens if you try...
I unfortunately have work for now so I can't help with a debugging session. I did try the code you sent and it runs and shows the window as expected....