Astonishing bug (XP)
-
From the MS NGs
_"Nobody" <nobody@cox.net> wrote in message news: OS effected: all flavors of Windows XP Steps to reproduce: 1) Make sure XP themes are turned ON 2) Open up an application (ex. Notepad) 3) Open up a modal dialog (ex. About box) 4) Turn themes off by setting to Classic mode. App and modal dialog will change to classic mode. Do NOT close dialog. 5) Now WITHOUT closing the modal dialog, switch back to themes You will notice that the app and the dialog are in some bizzare "25% themed mode". If you do not have a modal dialog open, changing back and forth works correctly. I notice this is not only notepad or MFC, but pretty much every application. Is there any possible work around for this bug? ** some interesting notes ** 1) if you start the app in non themed mode and switch back and forth it works fine. Only if you START in themed mode does this problem come up. 2) I tried creating a popup window in a completely different thread and trying it again. Even this popup window can not change between themed and non themed correctly if a modal dialog is open in the main thread. 3) If you start in themed mode and after changing to classic mode close the dialog box and reopen THEN change to themed mode, everything works correctly. Any ideas? besides of course closing the dialog box. Thanks. I've tried posting messages, using timers, SetWindowTheme, etc. Nothing seems to work._Regards, Nish :wtf: -
From the MS NGs
_"Nobody" <nobody@cox.net> wrote in message news: OS effected: all flavors of Windows XP Steps to reproduce: 1) Make sure XP themes are turned ON 2) Open up an application (ex. Notepad) 3) Open up a modal dialog (ex. About box) 4) Turn themes off by setting to Classic mode. App and modal dialog will change to classic mode. Do NOT close dialog. 5) Now WITHOUT closing the modal dialog, switch back to themes You will notice that the app and the dialog are in some bizzare "25% themed mode". If you do not have a modal dialog open, changing back and forth works correctly. I notice this is not only notepad or MFC, but pretty much every application. Is there any possible work around for this bug? ** some interesting notes ** 1) if you start the app in non themed mode and switch back and forth it works fine. Only if you START in themed mode does this problem come up. 2) I tried creating a popup window in a completely different thread and trying it again. Even this popup window can not change between themed and non themed correctly if a modal dialog is open in the main thread. 3) If you start in themed mode and after changing to classic mode close the dialog box and reopen THEN change to themed mode, everything works correctly. Any ideas? besides of course closing the dialog box. Thanks. I've tried posting messages, using timers, SetWindowTheme, etc. Nothing seems to work._Regards, Nish :wtf:Is this a joke? regards, Paul Watson South Africa The Code Project Pope Pius II said "The only prescription is more cowbell. "
-
Is this a joke? regards, Paul Watson South Africa The Code Project Pope Pius II said "The only prescription is more cowbell. "
Paul Watson wrote: Is this a joke? :) Actually, what I found astonishing is how the bug went unnoticed during the MS internal testing. Any basic test to see if themes work okay, would involve rapid switching on/off themes with windows open. Nish
-
Is this a joke? regards, Paul Watson South Africa The Code Project Pope Pius II said "The only prescription is more cowbell. "
No, I was able to reproduce it as well. :) Weird bug. :omg: Vikram.
http://www.geocities.com/vpunathambekar "Argue for your limitations, and sure enough, they're yours." – Richard Bach, "Illusions". "I think the internet has been online for too long." – Joesox.
-
No, I was able to reproduce it as well. :) Weird bug. :omg: Vikram.
http://www.geocities.com/vpunathambekar "Argue for your limitations, and sure enough, they're yours." – Richard Bach, "Illusions". "I think the internet has been online for too long." – Joesox.
Oh I know it happens, easy to reproduce once you know the completely un-likely set of steps. That is why I asked if it was a joke. A joke in that surely it is not an astonishing bug. I doubt anyone but developers doing some testing would run into this bug. regards, Paul Watson South Africa The Code Project Pope Pius II said "The only prescription is more cowbell. "
-
Oh I know it happens, easy to reproduce once you know the completely un-likely set of steps. That is why I asked if it was a joke. A joke in that surely it is not an astonishing bug. I doubt anyone but developers doing some testing would run into this bug. regards, Paul Watson South Africa The Code Project Pope Pius II said "The only prescription is more cowbell. "
Paul Watson wrote: I doubt anyone but developers doing some testing would run into this bug. Isn't that the point? Developers should test software before it's released? I'm with Nish on this one. Basic testing of the XP theme engine should have picked this up.
-
From the MS NGs
_"Nobody" <nobody@cox.net> wrote in message news: OS effected: all flavors of Windows XP Steps to reproduce: 1) Make sure XP themes are turned ON 2) Open up an application (ex. Notepad) 3) Open up a modal dialog (ex. About box) 4) Turn themes off by setting to Classic mode. App and modal dialog will change to classic mode. Do NOT close dialog. 5) Now WITHOUT closing the modal dialog, switch back to themes You will notice that the app and the dialog are in some bizzare "25% themed mode". If you do not have a modal dialog open, changing back and forth works correctly. I notice this is not only notepad or MFC, but pretty much every application. Is there any possible work around for this bug? ** some interesting notes ** 1) if you start the app in non themed mode and switch back and forth it works fine. Only if you START in themed mode does this problem come up. 2) I tried creating a popup window in a completely different thread and trying it again. Even this popup window can not change between themed and non themed correctly if a modal dialog is open in the main thread. 3) If you start in themed mode and after changing to classic mode close the dialog box and reopen THEN change to themed mode, everything works correctly. Any ideas? besides of course closing the dialog box. Thanks. I've tried posting messages, using timers, SetWindowTheme, etc. Nothing seems to work._Regards, Nish :wtf:I tried this and got the same result, but I've noticed a few more "funnies" since which also seem to suggest MS testing may have been less than comprehensive. A child window in SQL query analyser that was open during the change acquired a blue border. And I opened a fresh copy of calc and the menu items have a lighter coloured block around them. Strange but true.
-
From the MS NGs
_"Nobody" <nobody@cox.net> wrote in message news: OS effected: all flavors of Windows XP Steps to reproduce: 1) Make sure XP themes are turned ON 2) Open up an application (ex. Notepad) 3) Open up a modal dialog (ex. About box) 4) Turn themes off by setting to Classic mode. App and modal dialog will change to classic mode. Do NOT close dialog. 5) Now WITHOUT closing the modal dialog, switch back to themes You will notice that the app and the dialog are in some bizzare "25% themed mode". If you do not have a modal dialog open, changing back and forth works correctly. I notice this is not only notepad or MFC, but pretty much every application. Is there any possible work around for this bug? ** some interesting notes ** 1) if you start the app in non themed mode and switch back and forth it works fine. Only if you START in themed mode does this problem come up. 2) I tried creating a popup window in a completely different thread and trying it again. Even this popup window can not change between themed and non themed correctly if a modal dialog is open in the main thread. 3) If you start in themed mode and after changing to classic mode close the dialog box and reopen THEN change to themed mode, everything works correctly. Any ideas? besides of course closing the dialog box. Thanks. I've tried posting messages, using timers, SetWindowTheme, etc. Nothing seems to work._Regards, Nish :wtf:Try this out. Open an MFC MDI application e.g. Spy++ for those with VC++ installed(Doesn't seem to happen with non MFC). Run Task Manager and select the processes tab. Make sure that you've got the 'GDI Objects' column activated. Take note of the number of GDI objects for the app that you've elected to run. Open a new MDI child window (document). The GDI object count for the app naturally goes up. close the opened document. The object count goes down, but not to the original number before the doc was opened. Repeatedly open and close a new document and note how the gdi object count keeps getting higher and higher. Resource leakage ? Cheers Garf
-
Oh I know it happens, easy to reproduce once you know the completely un-likely set of steps. That is why I asked if it was a joke. A joke in that surely it is not an astonishing bug. I doubt anyone but developers doing some testing would run into this bug. regards, Paul Watson South Africa The Code Project Pope Pius II said "The only prescription is more cowbell. "
As unlikely as this is to happen, windows volume means it will happen enough. For some of the websites I've worked on, once in a million events happend 1-2 times a day just because of the volume of traffic on the site. That's another thing in the whole Linux/Windows debate that doesn't get brought up as much. Windows has more users so more strange bugs like this are discovered, making it look buggier. At least it isn't brought up as much as spyware and security issues.
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
-
Paul Watson wrote: I doubt anyone but developers doing some testing would run into this bug. Isn't that the point? Developers should test software before it's released? I'm with Nish on this one. Basic testing of the XP theme engine should have picked this up.
-
hauptman wrote: It's not a bug, it's a feauture -.- Only a game tester would appreciate the ironic hunor of that. :laugh: Jerry He said this was like painstakingly assembling the first layer of a house of cards, then boasting that the next 15,000 layers were a mere formality.--The Code Book, pp. 331 Toasty0.com DotNetGroup.org
-
From the MS NGs
_"Nobody" <nobody@cox.net> wrote in message news: OS effected: all flavors of Windows XP Steps to reproduce: 1) Make sure XP themes are turned ON 2) Open up an application (ex. Notepad) 3) Open up a modal dialog (ex. About box) 4) Turn themes off by setting to Classic mode. App and modal dialog will change to classic mode. Do NOT close dialog. 5) Now WITHOUT closing the modal dialog, switch back to themes You will notice that the app and the dialog are in some bizzare "25% themed mode". If you do not have a modal dialog open, changing back and forth works correctly. I notice this is not only notepad or MFC, but pretty much every application. Is there any possible work around for this bug? ** some interesting notes ** 1) if you start the app in non themed mode and switch back and forth it works fine. Only if you START in themed mode does this problem come up. 2) I tried creating a popup window in a completely different thread and trying it again. Even this popup window can not change between themed and non themed correctly if a modal dialog is open in the main thread. 3) If you start in themed mode and after changing to classic mode close the dialog box and reopen THEN change to themed mode, everything works correctly. Any ideas? besides of course closing the dialog box. Thanks. I've tried posting messages, using timers, SetWindowTheme, etc. Nothing seems to work._Regards, Nish :wtf:Just yesterday I read Raymond Chen explaining the why on his blog :rolleyes:
Pandoras Gift #44: Hope. The one that keeps you on suffering.
aber.. "Wie gesagt, der Scheiss is' Therapie"
boost your code || Fold With Us! || sighist | doxygen -
From the MS NGs
_"Nobody" <nobody@cox.net> wrote in message news: OS effected: all flavors of Windows XP Steps to reproduce: 1) Make sure XP themes are turned ON 2) Open up an application (ex. Notepad) 3) Open up a modal dialog (ex. About box) 4) Turn themes off by setting to Classic mode. App and modal dialog will change to classic mode. Do NOT close dialog. 5) Now WITHOUT closing the modal dialog, switch back to themes You will notice that the app and the dialog are in some bizzare "25% themed mode". If you do not have a modal dialog open, changing back and forth works correctly. I notice this is not only notepad or MFC, but pretty much every application. Is there any possible work around for this bug? ** some interesting notes ** 1) if you start the app in non themed mode and switch back and forth it works fine. Only if you START in themed mode does this problem come up. 2) I tried creating a popup window in a completely different thread and trying it again. Even this popup window can not change between themed and non themed correctly if a modal dialog is open in the main thread. 3) If you start in themed mode and after changing to classic mode close the dialog box and reopen THEN change to themed mode, everything works correctly. Any ideas? besides of course closing the dialog box. Thanks. I've tried posting messages, using timers, SetWindowTheme, etc. Nothing seems to work._Regards, Nish :wtf:I don't find it in the slightest bit surprising. I have found much more obvious bugs in XP. John Carson Q: How many Bush Administration officials does it take to replace a light bulb? A: None. As the President and Secretary Rumsfeld have made clear, the light bulb is doing a great job and we and our coalition allies are encouraged by the progress it is making. Mike Carlton
-
Paul Watson wrote: I doubt anyone but developers doing some testing would run into this bug. Isn't that the point? Developers should test software before it's released? I'm with Nish on this one. Basic testing of the XP theme engine should have picked this up.
Graham Bradshaw wrote: Developers should test software before it's released? is this a joke? of course NOT! that's what TESTERS are for. my guess is that's how the (not very few) Microsoft bugs make it into the production releases: only use for testing the developers and feed-back from the beta versions. great for lower costs, and you can see the results for yourself: when was the last time a major Microsoft piece of software worked reasonably without a couple of service packs? OGR