@unknownuser said:

Is this extension also free to use in commercial scripts?

Yes, wxSU has always been distributed under the BSD License which allows you to package wxSU with either free/open source or commercial works. The wxSU part of the package must still include the source code (unencrypted) and the original copyright notices, but you can handle the rest of your package however you want. See the full license (License.txt) for more details.

Oops, just noticed you list SU 6-7 in your profile. If wxSU did install successfully under SU 7, you should be able to just copy it over to your SU 6 directory. If that's not the problem, let me know.

Well, I guess "platform independent" was kind of a mislabeling on my part... It would be more accurately described as a "source-code only package for Windows"; no installer. And thus the wacky error message. Sorry about that.

The Mac installer should have worked for you. It's supposed to be a PPC/x86 universal install. Are you using SU 6 or SU 7? It tries to install in the SU 7 directories, which could be the problem if you only have SU 6. Email me and I'll help you debug it. Sounds like there is at least one or two things for me to fix here.

Thanks,
P

Just reviving this thread briefly to let everyone know I've just posted version 0.3.0 of the wxSU plugin.

You can download it here: http://sourceforge.net/project/showfiles.php?group_id=240585&package_id=292646

Version 0.3.0 Release Notes

• Update of wxRuby engine and documentation to version 2.0.0.

• Bug fix to prevent the creation of multiple instances of the wxSU::App class. Multiple instances can cause crashes and conflicts.

• Bug fix for conflict with V-Ray plugin that prevented SketchUp from shutting down completely after exiting.

• Better error message and checking for the DLL libraries "msvcp71.dll" and "msvcr71.dll" required by wxRuby on Windows with SketchUp 7.

• Required DLL libraries ("gdiplus.dll", "msvcp71.dll", and "msvcr71.dll") are now installed automatically if missing.

A new version (v0.3.0) of wxSU is now posted on the project website.
http://sourceforge.net/project/showfiles.php?group_id=240585&package_id=292646

Multiple instances of wxSU are now blocked which should eliminate the conflict that I've seen between Random Painter, wxSU, Windowizer 4, and other plugins. However, the conflicts won't go away until each plugin that uses wxSU upgrades to 0.3.0. In particular, the PlayUp plugin needs to be upgraded.

The new version also updates to wxRuby 2.0 which is more stable and has some new features.

If anyone finds problems or conflicts that I haven't mentioned, please email me.

Thanks,
P

Hi Chris,

There's nothing you can do in your code to prevent the crash. It's really my fault for not blocking multiple sessions of wxSU. I'll make the change and try to put out a new release of wxSU over the weekend.

The only change I would make to your code is to replace:

require "wxSU.rb"

with

require "wxSU/lib/Startup"

Hey, thanks for being an early adopter!

P

Hi everyone,

First of all, thanks to Adam for bringing me into the discussion. I had no idea anyone was using wxSU with their plugins yet! I'm sorry it's been the source of some nasty crashes.

I've been studying the wxSU conflicts with other plugins and have come to some conclusions:

1. At least one configuration with guaranteed crashing is: Random Painter + PlayUp + Windowizer 4 ...with the final trigger being the menu command Plugins/Windowizer4

2. Part of the problem appears to be that Random Painter and PlayUp are both running their own separate sessions of wxSU, which is dangerous.

3. The other part of the problem is that wxSU's threading scheme has instabilities on its own.

I'm pretty sure I can fix #1 and #2 by adding some code to ensure that only one session of wxSU is running at a time. That should solve most of the crashes described in this topic.

I'm not sure I can fix #3 without help. With only one session of wxSU running, you can type "sleep 10" at the console without any crash. BUT, the unique threading scheme actually gives you back control before the sleep is done. If you now type "sleep 10" again, you get a crash. In reality, will two plugins be asking to sleep at the exact same time? Probably not. It would be nice to figure out but I don't think it's necessarily a showstopper for wxSU in the meantime.

A couple questions for the forum:

Are there other configurations (besides #1) that will cause a crash with wxSU?

Is anyone aware of any other plugins that are using wxSU?

Thanks,
P

I've just posted version 0.2 of the wxSU plugin.

You can download it here: http://wxsu.sourceforge.net/

The new release fixes several bugs, updates to wxRuby 1.9.9, and has a few other improvements.