Were these Windows 7 bugs fixed in Windows 8?

By gate1975mlm
in The Fast Ring (Insider Previews)

 Share

Recommended Posts

Mentor

gate1975mlm

Posted
  • Author
Posted

Not a "BUG" I I would say is a feature--

The Shadow of the mouse is what you are seeing and if you turn that off in the effects the "BUG" will disappear.

If you notice there is a highlight under your mouse before you "mouse over" the close "X" which follows you to the Close "X"

The same effect can also be seen if you mouse over the start menu orb where it highlights itself to show it can be selected.

In earlier Windows such as XP that effect was called mouse spotlight.

It is not selecting and deselecting anything but showing you it is a click-able item.

If its a feature then my does the Red X not blink in any other windows?

Veteran

neo158

Posted
Posted

Those bug don't exists in 7, your Windows installation is probably messed up (sounds like bad gpu drivers to me).

The flickering Close button is an issue that everyone has, just open the properties of any hardware you have installed and hold the mouse over the close button. It only occurs when it's in focus and TBH how many times are you holding the mouse cursor over the close button.

Veteran

rfirth

Posted
Posted

I reported Bug 1 during the Windows Vista beta back in 2006 on MS Connect. Closed as [Won't Fix].

Then reported Bug 1 during the Windows 7 beta. Closed as [Won't Fix].

Bug 1 definitely happens on all computers, but it's such a minor issue you probably won't ever find it. It certainly doesn't affect the functionality.

In the Windows 8 Developer Preview, the issue still exists - it still has different behavior from all other windows, but it doesn't blink anymore. As I recall, it will only blink once. So you won't notice it in Windows 8 unless you're really looking for it.

Grand Master

George P Global Moderator

Posted
  • Global Moderator
Posted

They'll probably end up fixing bug 1 as they're tweaking and changing the UI itself so they've probably all seen it in the process of making and testing things. We'll just wait for beta to come and see if it's fixed but since it doesn't happen on all windows it really is minor.

Collaborator

Zimmedon

Posted
Posted

Those two bugs have been around for a long time. Also, UI tearing is more noticable on applications that do its own DWM calls (e.g. DwmExtendFrameIntoClientArea) such as Chrome and Firefox.

Button flickering (colors are a bit off):

http://i.imgur.com/XaFku.gif

UI tearing:

http://i.imgur.com/qS22s.png (normal window; barely noticable)

http://i.imgur.com/A1Fwy.png (Explorer)

http://i.imgur.com/ovGzp.png (Chrome)

http://i.imgur.com/3Ly1H.png (Firefox)

Grand Master

neufuse Veteran

Posted
  • Veteran
Posted

1st one I can't even reproduce in windows 7...

2nd one I've been complaining about since windows vista's beta where DWM was announced... it's always been marked as "by design" by microsoft...... every beta build I'd resubmit it and get it as "by design" all the way from longhorn up to 7's rtm....

Community Regular

justmike

Posted
Posted

There is a much larger bug called the Registry, that's the bug that really needs fixed. Tried running Windows 95 on a new machine under XP? It's crazy fast. MS is and has been going the wrong direction for quite a while now. The extended library situation back in the day, would be a crazy amount faster now because of multiple CPU's, GPU's, and the size of memory. What's in memory now? MS bloat in the name of security. The Windows registry should have been separated, and fully protected from 3rd party programs years ago.

Grand Master

+BudMan MVC

Posted
  • MVC
Posted

watch really carefully and the X button kind of gets selected and unselected once every few seconds.

You mean here

post-14624-0-24466400-1325866853.jpg

I left it there a good 30 seconds never saw it flicker, then again why in the world would you hover your mouse there for more than a fraction of second in the first place?

I have never seen this, nor if I did would I more than likely give it a second thought.. Seem pretty nit picky to me ;)

Not showing hover or not working when you click it would be an issue - it flickers "sometimes" if you hover your mouse there long enough -- not so much ;) How do you know its just not a mouse issue, or detection of mouse location problem -- maybe the mouse is right at the border of selection and is moving from on and off the threshold?

Grand Master

Ambroos

Posted
Posted

There is a much larger bug called the Registry, that's the bug that really needs fixed. Tried running Windows 95 on a new machine under XP? It's crazy fast. MS is and has been going the wrong direction for quite a while now. The extended library situation back in the day, would be a crazy amount faster now because of multiple CPU's, GPU's, and the size of memory. What's in memory now? MS bloat in the name of security. The Windows registry should have been separated, and fully protected from 3rd party programs years ago.

There is nothing wrong with the registry. Stop disabling stuff like UAC and you won't have any issues with the registry, ever.

Grand Master

neufuse Veteran

Posted
  • Veteran
Posted

There is a much larger bug called the Registry, that's the bug that really needs fixed. Tried running Windows 95 on a new machine under XP? It's crazy fast. MS is and has been going the wrong direction for quite a while now. The extended library situation back in the day, would be a crazy amount faster now because of multiple CPU's, GPU's, and the size of memory. What's in memory now? MS bloat in the name of security. The Windows registry should have been separated, and fully protected from 3rd party programs years ago.

for the 10 millionth time the registery is not a problem, whats the alternative? config files? the registry is a transactional database, it can support concurrent usage, changes, and is better with corruption and can self recover from it.... all things a text config file can not do

Grand Master

neufuse Veteran

Posted
  • Veteran
Posted

You mean here

post-14624-0-24466400-1325866853.jpg

I left it there a good 30 seconds never saw it flicker, then again why in the world would you hover your mouse there for more than a fraction of second in the first place?

I have never seen this, nor if I did would I more than likely give it a second thought.. Seem pretty nit picky to me ;)

Not showing hover or not working when you click it would be an issue - it flickers "sometimes" if you hover your mouse there long enough -- not so much ;) How do you know its just not a mouse issue, or detection of mouse location problem -- maybe the mouse is right at the border of selection and is moving from on and off the threshold?

these problems only happen when DWM is running in "aero" mode

Experienced

Matthew_Thepc

Posted
Posted

You mean here

post-14624-0-24466400-1325866853.jpg

I left it there a good 30 seconds never saw it flicker, then again why in the world would you hover your mouse there for more than a fraction of second in the first place?

I have never seen this, nor if I did would I more than likely give it a second thought.. Seem pretty nit picky to me ;)

Not showing hover or not working when you click it would be an issue - it flickers "sometimes" if you hover your mouse there long enough -- not so much ;) How do you know its just not a mouse issue, or detection of mouse location problem -- maybe the mouse is right at the border of selection and is moving from on and off the threshold?

I'm not saying that I think it's a huge problem (in fact, I use Device Manager daily and have never noticed this), but I was merely admitting it's existence :) And I know it's not a mouse issue or detection of location problem because (1) my cursor stays in the same place (2) this doesn't happen with any other windows. Try turning on Aero and try it, i think it might only happen in Aero.

  • 3 weeks later...
Mentor

DeadEndAccount

Posted
Posted
for the 10 millionth time the registery is not a problem, whats the alternative? config files? the registry is a transactional database, it can support concurrent usage, changes, and is better with corruption and can self recover from it.... all things a text config file can not do.

Bro, no use explaining the facts to some people. There is nothing wrong with the registry, as you've stated, with the only thing wrong have been third parties abusing the registry (using it as the dumping ground for random sh-t that doesn't need to be in the registry) and Microsoft themselves admitting that they failed to give clear guidelines on how the registry should be used and what shouldn't be put in there.

What I would like to see is for third parties to have better uninstallers and file tracking functionality so that when you uninstall their software it completely removes all the files and registry changes made - that is one thing I'd like to see Microsoft really emphasise when it comes to Windows 8 application certification. To attack the registry as justmike does is simply attacking a symptom rather than the real source of the problem.

In reference to Zimmedon's post - they're just a side affect of GDI's crappiness which can only be fixed by Microsoft moving their Common Control/Dialogue infrastructure from GDI to Direct2D/DirectWrite; don't hold your breath for that to happen given that Microsoft is focused on Metro at the moment.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.