|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
do you see a range of 0-1 ?
#macro CH2RGB (H)
#local H = mod(H, 360);
#local H = (H < 0 ? H+360 : H);
#switch (H)
#range (0, 120)
#local R = (120- H) / 60;
#local G = ( H- 0) / 60;
#local B = 0;
#break
#range (120, 240)
#local R = 0;
#local G = (240- H) / 60;
#local B = ( H-120) / 60;
#break
#range (240, 360)
#local R = ( H-240) / 60;
#local G = 0;
#local B = (360- H) / 60;
#break
#end
<min(R,1), min(G,1), min(B,1)>
#end
fix:
#local H = mod(H*360, 360)
custom pallet...
Post a reply to this message
Attachments:
Download 'hslhsv.jpg' (170 KB)
Preview of image 'hslhsv.jpg'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
exterminated hsv(.5) bug
1_55 = saturation_hueIteration
alt-tab to full screen pallet,
click color and clipboard the whole thing.
#declare hsv_1_150 = rgb < 0,0.746203,0.9 >;
no need for an include file
Post a reply to this message
Attachments:
Download 'hsvhsl.jpg' (78 KB)
Preview of image 'hsvhsl.jpg'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Some more detailed information about what you are trying to tell us you
are involved in here would be highly appreciated. I have not a clue. :-)
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 12/29/19 2:35 AM, Thomas de Groot wrote:
> Some more detailed information about what you are trying to tell us you
> are involved in here would be highly appreciated. I have not a clue. :-)
>
lol... thank you!!!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas de Groot <tho### [at] degrootorg> wrote:
> Some more detailed information about what you are trying to tell us you
> are involved in here would be highly appreciated. I have not a clue. :-)
>
> --
> Thomas
yes well, this is a color utility script, for the serious color enthusiast, and
more.
need a color? BAM! there it is, and in your clipboard - a visually chosen color.
perhaps more to do. could make a dialog interface for SV SL inputs, to alter the
pallet.
I have been able to do so much with this script. From scratch I am self taught
on camera matrix details til I really started to grok 3D math. mirc has no 3D
tools. That would be up to you. I included much 3D stuff. Without triangulation,
one cannot find their way in 3D.
mIRC is vital to have something this easy, if you need to sort something, or
prepare a data file, etc etc. perfect when I needed to sort lon lat for DEM
placement -- pop into a sort window, you're done in like 10 minutes with writing
a sort task.
Script is not case sensitive, to the 6th decimal. You need around
9-place-accuracy to calc a planetarium. I included math.dll to the 15th, for
when accuracy is a must.
Recommend mirc6.35, not the latest; you dont need it. This will open a new world
of files and programming, if u go online and find me ... heh.
In a read file, some simple instructions to load a script, for 1st timers just
getting mirc.
mIRC running might be all one needs, and of course everything is made for
windows. you NEED windoze 7. win 10 is a virus. I took the laptop back and told
Fry's to delete it and put on win7.
current pallet, 1920 visible colors in 3 sv/sl shades. 320 hue * 6.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas de Groot <tho### [at] degrootorg> wrote:
> Some more detailed information about what you are trying to tell us you
> are involved in here would be highly appreciated. I have not a clue. :-)
Right on. What he said.
Truly, I am thrilled to have someone like you here with so much ... energy. :D
But I'm left exasperated trying to parse and sort a rapid-fire string of 100
stream-of-consciousness blurbs and snippets. In 10 different threads.
I have just smiled and left you to do what you're doing - all while pondering
some diplomatic way to bring up and explain the - issue - and ask - nay, beg -
that you have some mercy and _slow down_ and give a mere half dozen more words
of explanation and context.
I'm thinking that if you've uncovered some sort of bug in the hsv2rgb macro in
colors.inc, then that would be an important find that I, Mike Horvath, clipka,
and many others would be interested in seeing and understanding - and fixing.
As for mIRC. I've only ever briefly used IRC, mostly in the distant past.
Linux Mint has "Xchat" which is some sort of IRC channel reader / messaging app.
Will that do?
As for Windows 10 - I would agree. "It's a virus." :D
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
> Thomas de Groot <tho### [at] degrootorg> wrote:
> > Some more detailed information about what you are trying to tell us you
> > are involved in here would be highly appreciated. I have not a clue. :-)
>
> Right on. What he said.
> Truly, I am thrilled to have someone like you here with so much ... energy. :D
> But I'm left exasperated trying to parse and sort a rapid-fire string of 100
> stream-of-consciousness blurbs and snippets. In 10 different threads.
>
> I have just smiled and left you to do what you're doing - all while pondering
> some diplomatic way to bring up and explain the - issue - and ask - nay, beg -
> that you have some mercy and _slow down_ and give a mere half dozen more words
> of explanation and context.
I'm on the Internet. I'm used to letting things roll past me.
> I'm thinking that if you've uncovered some sort of bug in the hsv2rgb macro in
> colors.inc, then that would be an important find that I, Mike Horvath, clipka,
> and many others would be interested in seeing and understanding - and fixing.
What I'm getting is that the bug was in Melody's utility, and that the "fix"
mentioned in the OP is not for a bug in CHSV2RGB(), but for a desired change in
behavior of CH2RGB().
> As for mIRC. I've only ever briefly used IRC, mostly in the distant past.
> Linux Mint has "Xchat" which is some sort of IRC channel reader / messaging app.
> Will that do?
>
> As for Windows 10 - I would agree. "It's a virus." :D
I avoid Windblows of *any* flavor. But I actually feel more comfortable with
Win10 than with Win7; Win7 was eating into my mental health, and was what
finally pushed me into GNU/Linux.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
guess what i just did hehe - lol
libpthreadGC2.a pthreadGC2.dll
#include <pthread.h>
#include <unistd.h>
C:\mirc614\irc\timer.h|12|warning: control reaches end of non-void function
[-Wreturn-type]|
but that should be expected - its a timer ?
EXECUTE //dll m### [at] hdll testimer@24
Library Loaded
1744830464
waiting - Error = 0
Executing Thread2 after 5
1744830464
^^^^^^^^^^ module
I GOT THREADS in WINDOZE - they said it couldn't be done in C.
used mingw time.h
/* pthread.h remove
struct timespec {
time_t tv_sec;
long tv_nsec;
}; */
struct timespec
{ /* Period is sum of tv_sec + tv_nsec; while 32-bits is sufficient
* to accommodate tv_nsec, we use 64-bit __time64_t for tv_sec, to
* ensure that we have a sufficiently large field to accommodate
* Microsoft's ambiguous __time32_t vs. __time64_t representation
* of time_t; we may resolve this ambiguity locally, by casting a
* pointer to a struct timespec to point to an identically sized
* struct __mingw32_timespec, which is defined below.
*/
__time64_t tv_sec; /* seconds; accept 32 or 64 bits */
__int32 tv_nsec; /* nanoseconds */
};
oh and error handling on the HSV HSL input dialog
Post a reply to this message
Attachments:
Download 'screen.jpg' (131 KB)
Preview of image 'screen.jpg'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Files used are here
ftp://sourceware.org/pub/pthreads-win32/dll-latest
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Cousin Ricky" <rickysttATyahooDOTcom> wrote:
> I avoid Windblows of *any* flavor. But I actually feel more comfortable with
> Win10 than with Win7; Win7 was eating into my mental health, and was what
> finally pushed me into GNU/Linux.
mIRC on Linux
Sorry but mIRC only runs on the Windows operating system, so it will not work on
Linux. There are no plans to make a version of mIRC that will work on Linux at
this time. Linux has quite a few native IRC clients, although none of them are
quite like mIRC.
Cousin Ricky, HELLO .. hehe
win7 is the promised land.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |