for people who dont go through all the posts, and so the title is enough, if not then why have it in the first place? its partially what made me confused in the first place
Does changing the title change anything for real? What do you want me to put there? It's just a title i thought of, nothing official MSFT. The iso's offered are still available, the esd's are still available. the real important info is at the OP, nobody reads it, but it's there.
Not in my case, the blink white bug in dark File explorer (which is what @cuteee is talking about and which I show in this comment, not to be confused with the blinking arrows bug) is still present in the build 17763.104
Nice, This is a good sign. It means that Microsoft and all the people involved in the process (Insiders, testers...) are taking care of all the problems including the cosmetic one's.
What has SAM-R have to do with this? Or Cutee for that matter, he manages to get everything wrong? Nvm, i have to stop getting involved...
Sam? I'm showing the comment made by cuteee, that's the comment that I'm referring to, he talks about the blink white bug in dark File explorer not the blinking bug of the arrows, they are two different things
Sorry I was speaking about the arrows in theTaskmanager. now , I did watch your clip carefully about the white blink in opening Explorer. I do not have this bug in my system. I repeated the opening, closing several times. but no white blink (my graphic card is an NVIDIA GeForce GTX 1080 Ti)
Yep I agree with your comments but many are still waiting for new on public release via Windows Updates & when the new ISO will appear News on this subject seems to have been put on the back burner I Understand they need to fix existing bugs, but by the time the release R5 via windows updates they will so much closer to the next release so why have dates of release for next builds when they often overrun
My guess : Microsoft faces two problems , the "bugs" and the process to validate before releasing. the first problem is easy to solve but the second is not. reshuffling an organization take times.
@Leope You are right. I watched the clips provided by your above links, frame by frame with Adobe Premiere. This makes me remember when I programmed time ago a Screensaver to a friend. I used MS visual studio and C++. Here in our case the painting of Explorer when opened , closed or resized (maximized), the background is erased (color white) before being repainted dark. This transition desktop background to white and white to black gives the noticing flash. The programmer tried to add a Grey in the sequence but it cannot mask the flash. Whatever the speed of the transition our eyes will detect the flash. The sequence used when you Maximize Explorers windows: 1- paint a rectangle around 10% smaller then the full screen 2- copy the minimized windows in the top left corner 3-erase the background 4-paint the background in Grey color 5-clean the drawing 6- paint in black the background (I mean the surface inside the big rectangle) 7- zoom out the rectangle to fit the screen
Please try to maximize and minimize the "Settings" windows . do you see a flash or not? if no then it is better programmed and the guy in charge is in trouble