We are having an issue getting the TreeView plugin Version 7.1 to work in any Windows XOJO version. This newer version works on the Mac and the prior version of TreeView works seems to work fine in Windows. We are unable to create a sub-class with Version 7.1 in Windows and it will not find the superclass for the TreeView.
We tried the Sample project and the plugins in included in the zip and it will not run either. We have both the TreeView.xojo_plugin and #CoreClasses.xojo_plugin installed under program files/xojo/plugins/ folder and we have restarted XOJO.
For the record, we have been using this class and other classes for a few years. We just don’t understand why we are unable to get XOJO to see the TreeView class under Select Super when creating a subclass. We have tried in both Windows 7 and 10 64-bit.
Thanks to Bjorn, I was able to find out that the issue with the plugin not loading had to do with having to many plugins installed under Windows which lead to the plugin with the name at the far back of the alphabet not loading. Renamed the plugin to start with an A and it loaded. I will now have to weed out any unused plugins.
I do a lot of graphics with matplotlib in Python. Now I wonder if I coiuld use your PythonScript Plugin to display the praphics - if possible live - in a Xojo window instead of the Python consol.
I currently save the python output to a file and show the file in Xojo but this is not interactive - I can’t tilt or rotate the picture without creating a new output and overwrite the old one.
Here an example of my graphics. https://www.dropbox.com/s/77ti3tg02gylbi4/GrapExample.png
I do a lot of graphics with matplotlib in Python. Now I wonder if I coiuld use your PythonScript Plugin to display the praphics - if possible live - in a Xojo window instead of the Python consol.
I currently save the python output to a file and show the file in Xojo but this is not interactive - I can’t tilt or rotate the picture without creating a new output and overwrite the old one.
Here an example of my graphics. https://www.dropbox.com/s/77ti3tg02gylbi4/GrapExample.png[/quote]
Hello Hanspeter
I have to confess I do not really got good answer to that one, I am not familiar at all with Python graphics. How you would bridge the Graphics with the Python Plugin bridge to Xojo is not clear to me. Probably best bet would be if you can save to temp file and load it from the Xojo code?
In R.1.1 all plugins are loaded include “SearchControl”, but all other MBS plugins are not working and I got 376 errors when build the application. Fore example all features and functions from ‘MBS Xojo Util Plugin.xojo_plugin’ and ‘MBS Xojo Win Plugin.xojo_plugin’ (and more) are not available.
I don’t know if you are on Windows or Mac.
If you are on Windows the combination MBS+Einhugur can cause painful problems. Clean all Xojo caches you can find is the first step.
Then I suggest you download the Microsoft tool DbgView here and see how far the plug-in loading works and then start removing plug-ins above that you may not need. Mind the cross-requirements of some of MBS plug-ins.
I have literally spent days on troubleshooting this.
Remove half of the MBS Plugins and other plugins load again.
It’s simply that Windows has a limit on how many DLLs you can load and with so many plugins you run into that limit.
Plugin authors usually don’t statically link it. The whole plugin set now days is just huge amount and will never work to load them all at once on Windows.
Note I said they SHOULD not
Not THEY DO - but if they do it has a bad side effect.
In theory dynamic linking should make it possible to load up to 300 DLL’s BUT of course there are other issues that can lower that limit (memory etc etc)
You only encounter this on Windows because its only Windows that has this issue with how dlls load
Thats an OS issue
OS X and linux handle this entirely differently and so do not have the same issue
That you can only load that many fewer may have to do with increased memory requirements for the IDE
Open Task Manager and start Xojo and see what the memory requirements are when it starts not loading plugins
Thats my suspicion
Only the Windows OS has this limitation, it is a silly limitation. This has slowly been getting fewer DLL’s you can load as Xojo gets bigger. So a tiny bit bigger Xojo might have bumped you over the limit between versions.
There is not really any solution to this except not loading all DLL’s in the world or unloading them again. The new Xojo Plugin format of course will have them per project but of course I have some reservations on how much of the existing many complex plugins makes sense to port to it time will tell, it will probably make sense for some kinds to make such swith and other kinds not (guessing here).
We have some ideas but nothing concrete enough to share
Actually it probaly wont have this issue since it wont involve loading dylibs
Geoff just spoke about this at the European conference and bob blogged about it here This new plugin format is project based, so its easier to handle different versions for different projects. The new Xojo plugins are compiled into an intermediate LLVM format so theres no need to ship classes with encrypted source code.