 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
// #declare X11_Web_Purple = rgb <0.501961, 0, 0.501961>;
// #declare farge_Purple_Web = rgb <0.501961, 0, 0.501961>;
// #declare farge_Patriarch = rgb <0.501961, 0, 0.501961>;
which ones should I delete ?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
jscolor 1.4.2
All previously described quirks are gone.
No reopening to get the data, and consistently.
Have not seen an error for some time.
So I get the new one, 2.0.5
It's way different. Hacking with
if (this.valueElement.value) MYColor = '#'+this.valueElement.value;
this.show() is a good time to set vars, to get the color on open. WORKS!!
OK set a color with picker, fail permanently, menu reload, still broken, no
errors from the console. Must command line reload to restore limited function.
This must be rare, bugless interface with multiple jsColor pickers.
Running in Firefox 25, 45 and latest Chrome. here's jsColor 1.4.2 ...
Setting MYColor in 1.4.2 from only two places. everything working.
this.fromHSV()
function redrawPad()
No errors.
Click upper right field to copy picker-output in 3 forms! sweet.
ctrl shift alt click to send palette selection to 3 picker fields and translate.
And jscolor knows all about it; so that's your color on open.
Post a reply to this message
Attachments:
Download 'povcolorselect1.0.zip' (88 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
This came together in only hours not days,
with all the previous work behind it.
Smaller faster using element events.
Still had to have the open/close trigger.
Using jscolor 2.0.5. Element events seem to have improved.
Knows which picker was opened and in use, and which picker was used.
Got to toss out 10 functions.
Post a reply to this message
Attachments:
Download 'povcolorselect2.0.zip' (49 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
only thing worse than posting junk is not coming back to fix it.
learned a lot, like, can't just add class= in the input tag,
and access properties.
rather than hacking a couple globals, which was all I needed;
instead, added this.open property. more complicated.
u have to do it all yourself that way.
showOnClick = false;
use the input tag events.
show and hide each picker yourself.
only picker that can set .open to false must be closed first.
just opening another picker only transforms the picker,
didn't actually call .hide(); so u have to do it.
i mean if u want it right.
Post a reply to this message
Attachments:
Download 'povcolorselect2.2.zip' (99 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
and it was being skiddish, which made me study it,
back to class ID method, updates have to be handled, as before.
end of send2picker() {
call newpicker();
}
just do all.
dont know the property for updating one. I got enough to remember.
that's all folks.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
the first one ... doh.
goes in send2picker() {
// newpicker();
JC[wkey].value = e.value;
}
its never done
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
"Sven-Erik Andersen" <sve### [at] gmail com> wrote:
> Releases a large update. The include-files have been split into separate files.
> Added more named colors, a total now of 6568 colors.
>
> Also improved the simple documentation with a separate HTML-file for each
> include-file that shows the color name, the RGB HEX-value, a color sample and a
> button that will copy the color name to the clipboard.
>
> Updated version is available on GitHub at
> https://github.com/SvenErik1968/Farger.inc/
>
> Brgds,
> Sven-Erik
I see that you've added 'Xona_com_Peacock', but the colour is different from
"peacock blue"; suggest adding:
farge_Peacock_Blue = rgb <0.199219,0.628906,0.785156>
(values from BRLCAD's colour db).
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> I see that you've added 'Xona_com_Peacock', but the colour is different from
> "peacock blue"; suggest adding:
> farge_Peacock_Blue = rgb <0.199219,0.628906,0.785156>
>
> (values from BRLCAD's colour db).
>
>
> regards, jr.
Hi jr,
sorry for not seeing and answering this before.
I took a look at the rgb.txt file from the BRLCAD's source files, and the
Peacock color there is defined as RGB 51, 161, 201.
If you convert that to a POV-Ray style format, that would be rgb <0.2,
0.631372549019608, 0.788235294117647> since you have to divide with 255 that is
the max value and equals 1 (with 0 being the minimum value), and not divide with
256 as you have done here, since that would give you 257 possible color
values...
Brgds,
Sven-Erik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Just wanted to say that I have released a new version.
Last year, I stumbled upon a Github repository
(https://github.com/meodai/color-names) that contains a massive collection of
named colors, currently 27351 unique color names.
So I have created a new include-file that contains the colors from that
repository. Had to do some conversion of the names in order to get POV-Ray to
accept them since many contain non-ASCII or UNICODE characters or various
punctuation marks.
I have attached the new release, and the latest version you can also find at
https://github.com/SvenErik1968/Farger.inc
Happy New Year, everyone!
Brgds,
Sven-Erik
Post a reply to this message
Attachments:
Download 'farger.inc-5.0.zip' (932 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
"Sven-Erik Andersen" <sve### [at] gmailcom> wrote:
> Just wanted to say that I have released a new version.
>
> Last year, I stumbled upon a Github repository ...
> that contains a massive collection of
> named colors, currently 27351 unique color names.
:-)
nice! thanks. plan to have a look in the coming days.
re the peacock blue you're probably right, cannot remember now what I did. :-)
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
