Edit Colour Window Problem?

Hope someone can help me. I'm trying to add a subtle tint to a prim using the in world colour picker in the Edit window-I know this is the cheap way of doing it BTW, I should do it in PSP and I will once I get the shade I am happy with.

Anyway, that's neither here nor there, my problem is I want to use this tint on quite a few prims for test purposes. Not a problem I thought, I'll drag the colour down into the presets at the bottom of the colour window so it is always there for me in the future.

Well, for some reason, this is now impossible to do. I am using the Release Candidate 1.19.1(0) from March 5th. In the regular SL client , I can do this without a problem, but this new viewer I end up dragging the whole edit colour window around, rather than just the swatch to my desired position.

It even says under the Current Color swatch "Drag below to save)". Well, I try, but I drag the window. Am I doing something wrong?

-Brick-

I'm not in-world right now to test if the color picker is misbehaving on my end as well, but if it is, there is an easy work-around. Simply write down the numerical value of the texture. Then just plug in the same numbers again each time you want to use that color.

Thanks for the reply Chosen.I could do that, an even easier way would be just to select the my new prim I want the colour applied to, then select an existing prim with the colour already on it. Then just apply the same colour to both prims.

It's just that this colour could be one I want to save for later tests on different builds. Rendering both alternatives null. I could have sworn I always have been able to drag the colour down to a pre set for fast, easy access until I installed this new client.

I think you're missing the possibilities. It doesn't "render both alternatives null" at all. Either option will work just fine, infinitely.

The reason I would prefer to write down the numbers, rather than to sample an existing prim, is so that the record would be as easily permanent, and universally applicable, as possible. Your prim-sampling method is fine too. I opted not to mention it only because to me, it's slightly more complicated than just writing down the numbers. But either one is easily applicable for your purposes.

With regard to the numbers, if you're worried about remembering which number set goes with which color, that just comes down to good record keeping. One simple solution is just to write a description, like "pale blue from my house siding" or "bright orange from that pumpkin I made for my Halloween costume" or whatever works for you to help jog your memory. Another idea would be to plug the same numbers into you paint program of choice, and store a collection of swatches there.

If you prefer to work entirely in-world, you can make a color swatch collection very easily out of cubes. Link a set of cubes together, with a blank texture on each. If you do a grid of 16x16, that's gives you 256 panels (or up to 1536 if you use all sides), far more than what's available to you in the color picker's tiny swatch palette. Whenever you've got a color you want to save, whip out your swatch collection object, and apply that color to one of the cubes. There it will stay saved, permanently, ready for you to sample it whenever you need. Then when you've got a project for which you want to try out any of your saved colors, simply rez the swatch collection object again, and sample its colors in the manner you described. You could even make it a HUD if you want.



I'm sure you did. Your mention of it now is the first I've ever heard of it.

Thanks for the reply, this idea is genius. I think I'll have to start using it.




I just logged into the regular viewer, and I can drag the colour swatches perfectly to the presets along the bottom, just as I remembered.

Logged back onto the Release Candidate, and I can't drag them no matter what I try.There is definitely something wrong with the new viewer with regards to the colour picker window.

All these words are fine... and I honestly (kind of) stopped reading after a paragraph... or so. The bottom line is: the colour picker doesn't work... in the latest Candidate Release or the newest *regular* sl load.... I am going to try to yell at whomever is the fixer of all things... cause I want it back. I can find adventures enough in sl... without being slowed down by what so obviously has been broken. I can't take learning scripting (on one hand) and having to keep keep colour number logz on another... )-;

This is a definite bug in the Release Candidate client. It has been reported, but they have failed to fix it. One of the independent coders looked at the Open Source and came up with a one-line patch that fixes this, but LL hasn't yet implemented it.

That's too bad. You missed out on at least two very simple work-arounds, then. And that's including one for how to make your own color picker in-world that actually works BETTER than the built-in one, even when the built-in one isn't broken.

Read, read, read.


So in your experience, yelling at people encourages them to give you what you want faster? Tell me, what are your people called, and what planet are they from? Because human beings from the planet Earth don't tend to be too eager to help you after they've been yelled at. Maybe our species is inferior to yours or something, but that is how it works here.

The bug is well known, and it is on the list to be fixed. And if Cerra's right (which she usually is), the fix is known at this point, too. It's entirely possible, not to mention very likely, that the human beings who are responsible for that particular part of the code have other, larger, bugs to squash before they can get to that particular one. Their world doesn't stop for your color picker, as much as you might like it to.

Look, we all hate the bugs, and sometimes we don't always understand why seemingly simple ones don't get repaired as quickly as we'd wish. But the fact is the Lindens aren't stupid. Just about all the ones I've met and spoken with, either by phone, E-mail, or in person, have actually been some of the brightest people I've ever encountered, in fact. Often, when things get 'wait-listed', it's for good reason. I don't always agree with their ordering of priorities, but I do respect the fact that they know a hell of a lot more about what needs to be done how than I do. So I'm willing to accept that they probably also have a better sense of the most appropriate when as well. That's admittedly frustrating, but there's certainly nothing to be gained from getting angry over it.

Patience, Grasshopper.

i agree very much chosen. we all complain about all the bugs sl has, but hey. if you could do it better, you probably wouldn't be using sl to be complaining about it.

As of Release Candidate 8 for 1.20 series browser the colour picker has been fixed so it is only a short while before it become the main client and all are happy again...

Pol McLaglen.

If you have to do it numerically this page is amazing

http://www.lslwiki.net/lslwiki/wakka.php?wakka=color

"Show color under cursor" in debug under UI is also useful in a different way (I'm adding it here as it will be of interest to many).