[Plugin] Random Painter (Updated March 9th, 09)
-
That would be really cool... Just like Windowizer 3, where a drop-down menu lets you choose materials for each part!
-
You can also choose your colour values using this free utility from NOVOSIB:
http://www.linxexplorer.com/colorpicker.html
Visual Color Picker is very easy to use and powerful RGB-HSV-HSL-CMYK-HEX color selector. The program allows you to easily capture color value from any position of the screen even if program does not have input focus. The program has small screen capture preview area. By clicking associated button, you will get the associated RGB value in the dialog. The RGB color is automatically translated to RGB, HSV, CMYK and HTML HEX values. The program has standard and custom color tables. Text-background preview allows you to see how two colors will look next to each.
I use it all the time
-
No Pantone/ RAL format?
-
Hey, thats a great tool. I'll have to d/l it and play with it when I get home,
Chris
-
chris,
just for your information (i am not sure there is something you can do): having wxSU installed causes conflicts with windowizer4 (the dialogue appears blank) and immediate crashes after invoking it.
regards.
-
Hi Edson, thanks for the note. I saw the post in Rick's windowizer script. Hopefully it gets worked out. I suppose I could also provide a version of random painter that does not require wxsu again.
Chris
-
@chris fullmer said:
Hi Edson, thanks for the note. I saw the post in Rick's windowizer script. Hopefully it gets worked out. I suppose I could also provide a version of random painter that does not require wxsu again.
Chris
i thought it would not work without it.
-
Well, it is the nice User Interface that comes from wxsu. So I can remove wxSU and make pop up dialog boxes that require you to type in RGB values. Its more tedious than just clicking on the color you want. But it works fine. It is how the script worked at first. So if you'd like, I could re-write it and put the old inputbox version back. I'll just have 2 versions available for download. One with a nice GUI and one without.
Chris
-
i think it is a good idea and i would thank you for that. but i suggest you wait a few days to see if rick comes up with a solution to this problem.
-
Great idea for a script - thank you! Should come in very useful for a bit of mattepainting.
I'm getting all kinds of errors with wxSU when sketchUP loads, which means that I haven't got 'randompainter' to run at all yet (though it's in the menu bar).
Obviously me having problems with wxsu is nothing to do with you at all
, but until I can work out what's happening a version that doesn't require wxSU to run would be brilliant.Thanks for all your work.
AJ
-
Oh bummer, sorry to hear it. I think I'll post a version that is independent of wxsu. Hopefully I can get it done today.
Chris
-
OK Edson, I put another version of random painter up. It is non-reliant on wxsu. Its a bit slower to use, but I suppose if the other didn't work at all, then this is quite an upgrade
Chris
-
surely. thanks a lot. you have become quite an asset to this forum.
is this "new" version up on the first post? why do you not keep both versions up? not all people use windowizer4; perhaps some would prefer the version that relies on wxSU.
-
They are both up there - the latest version that supports wxsu and the stripped down version that does not. I think at some point I had added some features to pre-wxsu version that have been lost. So if there is something you remember it doing that it no longer does, let me know. All in all though, its still very functional. Thanks for the complements Edson, I'll let you take me out to a churrascaria if I ever make it down to Porto Alegre
Chris
-
Cool plugin.
However, I think wxSU isn't really ready for primetime. Specifically, it doesn't manage Ruby threads correctly wrt SketchUp.
If you have a look at lib/App.rb there are some moderately scary comments. It seems to assume its the only plugin running - I think this is why it causes so many problems.
Adam
-
Adam, does having it installed for my plugin mean that it is possibly going to mess up other plugins?
-
Yes, I believe it does. I've spent weeks trying to track some crash bugs for LightUp users that appear to be directly related to having wxSU loaded.
The most simple case I found was having wxSU installed and typing "sleep 10" at the console for a crash with some plugins that use it.
Today I've been talking on email with Peter (author of wxSU) and he's on the case - so lets hope it can be fixed asap.
Adam
-
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:
-
At least one configuration with guaranteed crashing is: Random Painter + PlayUp + Windowizer 4 ...with the final trigger being the menu command Plugins/Windowizer4
-
Part of the problem appears to be that Random Painter and PlayUp are both running their own separate sessions of wxSU, which is dangerous.
-
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 -
-
HI Peter, great work on WxSU. I'm afraid most of this discussion might be over my head. I only barely was able to implement WxSU, and I'm not sure that I did it correctly.
Is there a better way to implement so that it won't cause a crash? or is that something you need to do on the development end? I can post my code in this thread if that will help.
Chris
EDIT: I am unaware of other plugins that use WxSU at this point.
-
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
Advertisement