Skip to main content

How to convert Color code into RGB

I had a problem recently where I had to convert a color code selected by a user using GETCOLOR ( ) into an RGB setting for use in a report.

I am across this code and then rewrote it into VFP.

Update - until of course, Ted, took me here instead where I should have started all along, in the Wiki.

(don't bother reading below unless you want to see the other ways people do this.

LPARAMETERS tnColor,tcVal

LOCAL R1, G1, B1
LOCAL R2, G2, B2
LOCAL A As Long

R2 = 0
G2 = 0
B2 = 0

If tncolor = -1
&& DEfault to 255 regardless
RETURN 255
ENDIF

For B1 = 0 To 255
A = RGB(R2, G2, B1)
DO CASE
CASE A > tnColor
B2 = (B1 - 1)
Exit
CASE A = tnColor
B2 = B1
Exit
Endcase
Next B1

For G1 = 0 To 255
A = RGB(R2, G1, B2)
DO CASE
CASE A > tnColor
G2 = (G1 - 1)
Exit
CASE A = tnColor
G2 = G1
Exit
Endcase
Next G1

For R1 = 0 To 255
A = RGB(R1, G2, B2)
IF A = tnColor
R2 = (R1)
Exit
EndIf
Next R1

DO CASE
CASE tcVal = "R"
RETURN r2
CASE tcVal = "G"
RETURN g2
CASE tcVal = "B"
RETURN b2
ENDCASE

It works great but I was surprised that there wasn't a built-in way to do this in VFP. Of course, the above code isn't very intelligent but it relies on the fact that a PC can process 255 x 3 extremely quickly and thus return the correct result.

I then came across this code which looked a little more algorithmically correct and as a result MUCH faster.

LPARAMETERS lnColor, tcType

DO CASE
CASE tcType = "R"
RETURN INT(MOD(lnColor ,0x100))
CASE tcType = "G"
lnColor = lnColor/0x100
RETURN INT(MOD(lnColor ,0x100))
CASE tcType = "B"
lnColor = lnColor/0x100
lnColor = lnColor/0x100

RETURN INT(MOD(lnColor ,0x100))

ENDCASE

Same results and the performance is good on both but obviously the second one is the

Keep in mind that RGB colors can't be used reliably for all color settings but at least on the VFP FRX , they work well.


How to convert Color code into RGB - visual basic, vb, vbscript

Comments

Ted Roche said…
The source,Andrew, use the source:

http://fox.wikis.com/wc.dll?Wiki~VFPFunctionRGB~VFP

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...