ListView how to change color of selected unfocused listview element / row ?

[mLipok]

11 minutes ago, WildByDesign said:

I am curious about this as well. In particular, are there any performance differences between constantly creating/deleting brushes in comparison to the non-brush solution?

Exactly this is what I'm curios too. You just worded it in a better way.

Thanks 

11 minutes ago, WildByDesign said:

I've learned a lot from this thread already.

Good for you

[UEZ]

1 hour ago, mLipok said:

@UEZ I also have a question about @Nine example and my modification .
Nine uses 

_WinAPI_DeleteObject($hBrush)

which was fired each time LV was re-drawn

My questions are about using 

_WinAPI_DeleteObject($hBrush)

in a such kind of multiple usage "like a loop"

Question 1:
Should we delete Brush each time or they can be static ? (which I did in my modification to Nine example)

Question 2:
Are there any advantages or disadvantages of using Brush in comparition to yours "non Brush solution" - of coruse in such scenario (using Brush in WM_NOTIFY especially with big ListView) 

Thank you very much in advance
mLipok

 

1) As a general rule, when you open a resource, you should release it again to avoid a memory leak. For example, if you constantly call _WinAPI_CreateSolidBrush(), you’re reserving memory without freeing it up. Eventually, the memory will run out.
Yes, every call to _WinAPI_CreateSolidBrush() / _WinAPI_DeleteObject() takes processing time, which may become noticeable if there are a large number of calls. I don’t think this plays a major role for “normal” applications.

2) At first glance, it appears that no brush is being used, but I assume that Windows creates a brush internally and then deletes it to prevent a memory leak.

[Nine]

5 hours ago, mLipok said:

What is your opionion on this modification ?

No problem with it.  I do not think it really matters, but it doesn't hurt either.

[mLipok]

3 hours ago, UEZ said:

Yes, every call to _WinAPI_CreateSolidBrush() / _WinAPI_DeleteObject() takes processing time, which may become noticeable if there are a large number of calls. I don’t think this plays a major role for “normal” applications.

On big 4K screen with huge numbers of rows in the listview it can be noticeable.