Page 1 of 1
DCBROWSE change row color during scrolling
Posted: Wed Nov 29, 2017 10:45 am
by Piotr D
Hi,
One of my customer report me, that during scrolling an DCBROWSE, the row change color. The row was bright and after scrolling it's change to dark. This was under Windows 10 Pro (64-bit), Alaska 2.0.832. Any idea?
Piotr

- zacienianie sigid.jpg (464.9 KiB) Viewed 10665 times
Re: DCBROWSE change row color during scrolling
Posted: Wed Nov 29, 2017 7:18 pm
by rdonnay
This was reported by Steve Poore in the UK about a year ago.
One of his customers reported the problem but Steve could not reproduce it.
Re: DCBROWSE change row color during scrolling
Posted: Fri Dec 01, 2017 2:16 am
by reganc
rdonnay wrote:This was reported by Steve Poore in the UK about a year ago.
One of his customers reported the problem but Steve could not reproduce it.
Just to add (I work with Steve Poore, he is our CEO) we have had this problem internittently for a couple of years.
I did a search in our code for anything that uses the same color and came up blank. We generally only use the GRA_CLR_* defines and that color that appears is not one of them.
Exiting and restarting the application is the only way to get it back to normal.
Re: DCBROWSE change row color during scrolling
Posted: Fri Dec 01, 2017 7:42 pm
by sdenjupol148
Hi All,
This is an issue I have experienced as well.
I actually reported this to Roger before Steve and we spent a very small amount of time on it but since we couldn't reproduce the problem with any accuracy we let it go.
The only time I could ever force it to happen is if I scrolled quickly or if I kept scrolling with the mouse wheel for a long time.
But even then, it did not happen 100% of the time.
What I have noticed is that since switching over to XBase++ 2.0, it very rarely happens.
All my applications are multi-threaded, so if the color changes in the thread of one browse, it does not necessarily affect another browse in a different thread.
In those cases, simply closing the window and re-opening it solves the problem.
Still, I wish I could isolate the cause.
Bobby