Hi,
I have 6.35.0 AB x64 and i've noticed a slight Flicker as if something is refreshing or updating in Quote Editor window.
This is a local Database in which i import some IEOD data, so no data plugins or external source of data.
It consistently flashes once every 4-5 secs when the window is opened.
I'm sure i didnt see this in older versions.
Does this occur with other users too ?
This is a GIF.
Thanks.
It is just the consequence of the fact that double buffering has been disabled for all lists views when black theme for list views support was added as Windows double buffering does not work well with that. But I can turn on double buffer on this particular list as it does not use black theme at all.
Thanks for the reply.
I am using the Black theme but as you said, it doesn't apply for QE so maybe you can take action that you think is most suitable.
I already turned double buffering for QE back on in development version.
Dear @Tomasz
I thought this next minor issue is also related to the new Black Theme and Listviews so it would be appropriate to just add it here.
This time it is the Watch Window in FE (Formula Editor)
The Watch Window has a Dark background and the Name and Type are White. (Correctly inverted colors as opposed to black font over white)
While debugging, the arrow that debugs the current line will populate the Array variable with run-time values but the color is Black or Dark and hard to read.
It takes you to step into next line before the font changes to white.
Kindly look into this.
Thanks.
Wasn't able to edit the previous post and ask this.
PS:
Is there a reason why Treeviews (other listviews like Symbol) have a white background or rather we dont have Dark theme for it yet?
The reason is that Microsoft is lazy. Instead of implementing "Dark Theme" correctly (in compatible way so it can be used say starting from Windows XP), they implemented it in absurd (non-backward compatible) way so it works only on Win10 1809 or higher. All the people who deliberately choose NOT to upgrade Win10 (because of bugs that arrive with each update) could not use it.
This should be as easy as calling one function but it is NOT.
The only way to have dark mode in earlier versions of Windows for the developer is to rewrite Windows controls to use 100% owner-draw (you draw everything, Windows does NOTHING). Which means doing lots of work (like weeks of coding) that should be done by Microsoft. I did that for LIST VIEWS (they are completely owner drawn in AmiBroker). But I did not do that for tree.
Microsoft is absurdly lazy and they just don't care. I am the opposite. I am supporting every Windows version starting from XP (not so long ago I was supporting even Windows 95)
Thanks for the detailed response.
It makes perfect sense. No wonder they were struggling themselves with File Explorer, the Control panel and all the other UI from before System dark mode.
Guess they had to write a lot of code for their controls like in File explorer etc because its one of the most used things. And they decided to scrap the old control panel among other things.
For the benefit of other readers: I found this MS blog
https://insider.windows.com/en-us/community-news/dark-theme-in-file-explorer/
Why did it take us some time to get it applied in File Explorer? Compared to more modern parts of Windows, File Explorer was harder to change quickly. While dark mode can be applied to many modern components in Windows quite easily, File Explorer contains some legacy user interface frameworks, which don’t plug into that infrastructure automatically. We had to literally break new ground to bring dark mode to these parts of File Explorer.
No, they hadn't. Microsoft has SOURCE CODE for Windows. If you have SOURCE code for Windows, changing color is a breeze. And I have NO idea why it took them so long, given the number of developers they have. As I wrote, should be one function call. Actual difference is just SetTextColor API function (again IF you have source for Windows). But if you don't have the source code for Windows (as developers OTHER than Microsoft), then you are left dead in the water and you have to rewrite parts of Windows. I have done this and my list views work 100x faster than Microsoft ones and I can have rainbow listviews if I needed. I don't know what people they are hiring but if they are "exited" and "break new ground" to just change colors, then they must be joking.