When one item of a specific color is selected and the color picker called to change the object color, it comes up first with the existing object color, so you know right away what it is and can maybe tweak it a little bit with the sliders.
If two or more objects of the same color are picked however, the color picker always defaults 0,0,0, so you have no idea what the original object color was. Makes it more difficult to do a small adjustment.
I also prefer to have the color change live before pressing OK.
Meaning a preview feature, or an Apply button separate from OK?
see also this similar topic
I would lovet to have the color picker start with the first selected object’s color if multiple objects are selected.
Live preview
Well, the thing is, if items are selected, they are generally highlighted in yellow (or some other color if you changed it), so I don’t know how you get the “live preview” color on the selected objects…
This is for the wireframe by layer color, right?
I’ve had a similar need for plugins: a double highlight saying “Rhino has selected this, and so have I.”
The drawing pipeline implementation isn’t entirely uniform for object types on the Rhino end so there are a few WISHes to file, but the concept seems easy: leave the yellow highlighting and add a few pixels of other highlighting surrounding it.
What do you think of doing something similar to leave the yellow highlighting and show the new color? The yellow is the default Rhino highlighting. Red is the color I picked as a different, contrasting one which may be applied separately or simultaneously to objects Rhino has selected or not.
Not necessarily, it could be for color-by-object and surfaces/polysurfaces/hatches etc. in shaded modes…
I think select by object would be the same- the shaded case is a good point. Image editing software solves this sometimes with animations and other time domain approaches.
I’d be optimistic that someone at McNeel can come up with a reasonably visually appealing way to handle it.
Hi Mitch -
Clearly, I’m misunderstanding something.
-wim
Maybe it’s me that is missing something…
The objects are solid hatches.
Hang on, I think I found the problem… The button was actually running a script and the script appears to be buggy… Problem solved, my bad, sorry for the noise. The button has been around in my workspace for so long I forgot what was under it.
Edit - now fixed the script… 
Can you share it 
ObjectColor.py (908 Bytes)
