How do do HSV with a Brush

[ETFVoyageur]

I have some code that works in HSL space. It relies on Color.GetSaturation(), Color.GetHue(), and Color.GetBrightness().

• The Color class is not available in NT8
• I do not see similar functions on Brush
• I have Googled and all examples I find use those Color functions during their calculations

So how do I make that work with just a Brush? I need either that, or else to have access to Color restored so I can use that in my internal calculations.

--EV

[koganam]

I have some code that works in HSL space. It relies on Color.GetSaturation(), Color.GetHue(), and Color.GetBrightness().

• The Color class is not available in NT8
• I do not see similar functions on Brush
• I have Googled and all examples I find use those Color functions during their calculations

So how do I make that work with just a Brush? I need either that, or else to have access to Color restored so I can use that in my internal calculations.

--EV

One can certainly use the System.Drawing namespace if one wanted, but to me, mixing Winforms and WPF is a code smell. You might have to write some converter methods instead, so that you stay in WPF.

[ETFVoyageur]

One can certainly use the System.Drawing namespace if one wanted, but to me, mixing Winforms and WPF is a code smell.

I tried that, but the compiler objected. Intellisense does not even admit that System.Drawing exists. I did not look deeply into what it would take to fix that -- I just assumed that Color was deliberately excluded.

You might have to write some converter methods instead, so that you stay in WPF.

I guess you are correct -- I need to write my own to and from code for Hue, Saturation, Luminance. Things like that sure seem like library matters that should already be there, though. I'm disappointed if the new order does not provide that, so I thought I must just be missing something obvious.

--EV

[koganam]

I tried that, but the compiler objected. Intellisense does not even admit that System.Drawing exists. I did not look deeply into what it would take to fix that -- I just assumed that Color was deliberately excluded.

I guess you are correct -- I need to write my own to and from code for Hue, Saturation, Luminance. Things like that sure seem like library matters that should already be there, though. I'm disappointed if the new order does not provide that, so I thought I must just be missing something obvious.

--EV

Nope. definitely a WPF issue.

[-=Edge=-]

I tried that, but the compiler objected. Intellisense does not even admit that System.Drawing exists. I did not look deeply into what it would take to fix that

Add the system.drawing.dll as a reference...

[ETFVoyageur]

Add the system.drawing.dll as a reference...

I thought of that, and am willing to do so. Is that a problem for others if I were to provide them with my indicator? (That's why I was cautious about doing so.)

--EV

[-=Edge=-]

I thought of that, and am willing to do so. Is that a problem for others if I were to provide them with my indicator? (That's why I was cautious about doing so.)

Yes.. anyone using an indy with that would also have to add that reference as well.. Which is why I've tried to stay away from the system.drawing all together now..

[ETFVoyageur]

Yes.. anyone using an indy with that would also have to add that reference as well.. Which is why I've tried to stay away from the system.drawing all together now..

That's what I figured. I guess the best thing is to look into writing my own conversion routines.

--EV

[koganam]

Yes.. anyone using an indy with that would also have to add that reference as well.. Which is why I've tried to stay away from the system.drawing all together now..

Well, if they used the NT import facility, the reference would get automatically added by AdditionalFiles.txt.

I still do not think it is elegant to mix WinForms and WPF code, but hey, that is just me.

[ETFVoyageur]

Well, if they used the NT import facility, the reference would get automatically added by AdditionalFiles.txt.

I still do not think it is elegant to mix WinForms and WPF code, but hey, that is just me.

I agree with you -- I'll Google for some conversion routines. This is a common enough issue that there must be some publicly available code.

--EV