Yet Another Stupid NET Fault
-
I really do like .NET, but just like the James Bond films says "We've inserted hundreds of bugs so the Users will be forced to pay for expensive upgrades for years to come". The fault Okay. Create a form, with a label, then set the opacity of the form to 80% (any number other than 100% will do). Now reposition the label using code (I was actually repositioning the label to follow the mouse on each mousemove). Note that any window behind your semi-opaque form is corrupted by the label each time it gets moved. This is probably because the semi-opaque form, or perhaps the label itself, is keeping a background image which is used to restore areas of hidden windows as they are re-exposed. It is probably this image which is erroneously written back to the wrong area of the screen because the label itself has now moved. If this is yet another microsoft feature, it's a strange one. Only change is constant
-
I really do like .NET, but just like the James Bond films says "We've inserted hundreds of bugs so the Users will be forced to pay for expensive upgrades for years to come". The fault Okay. Create a form, with a label, then set the opacity of the form to 80% (any number other than 100% will do). Now reposition the label using code (I was actually repositioning the label to follow the mouse on each mousemove). Note that any window behind your semi-opaque form is corrupted by the label each time it gets moved. This is probably because the semi-opaque form, or perhaps the label itself, is keeping a background image which is used to restore areas of hidden windows as they are re-exposed. It is probably this image which is erroneously written back to the wrong area of the screen because the label itself has now moved. If this is yet another microsoft feature, it's a strange one. Only change is constant
Alastair Stell wrote: The fault LOL cool fault :rolleyes: Not only that but on mine the label (or a textbox I tried after that) disapears itself. Even going to the app with the corrupted display does not fix it, I have to move the window to get it back. BTW is there a bug/intended-behavouir/feature list somewhere online for .NET? I still like .NET btw :) regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
-
Alastair Stell wrote: The fault LOL cool fault :rolleyes: Not only that but on mine the label (or a textbox I tried after that) disapears itself. Even going to the app with the corrupted display does not fix it, I have to move the window to get it back. BTW is there a bug/intended-behavouir/feature list somewhere online for .NET? I still like .NET btw :) regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
The one I hate is when the properties window refuses to show itself and I have to stop and start visual studio to make it reappear :mad: :mad: :mad: :mad: :mad: - happens both at home and at work
Stupidity dies. The end of future offspring. Evolution wins. - A Darwin Awards Haiku
-
Alastair Stell wrote: The fault LOL cool fault :rolleyes: Not only that but on mine the label (or a textbox I tried after that) disapears itself. Even going to the app with the corrupted display does not fix it, I have to move the window to get it back. BTW is there a bug/intended-behavouir/feature list somewhere online for .NET? I still like .NET btw :) regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
Yes, so do I:) And I expect that a radical new product is going to have faults. But it makes you wonder: a) what kind of QA department does microsoft have for .NET? A lazy one? Or was this a premature release forced by management? b) why didn't microsoft set up a mechanism for reporting errors? Incidentally, Delphi 7 is available if you ever want to develop applications which run on Lunix as well as Microsoft platforms! btw. how is life in SA these days? I used to live in Springs, outside Jo'burg on the Gencor mining properties, but I left back in 1986 for Australia, then Britain, then America... Only change is constant
-
The one I hate is when the properties window refuses to show itself and I have to stop and start visual studio to make it reappear :mad: :mad: :mad: :mad: :mad: - happens both at home and at work
Stupidity dies. The end of future offspring. Evolution wins. - A Darwin Awards Haiku
Old one this one. Shift Left Click the tab to get it to show again. It is seemingly caused by having Properties and Dynamic Help as Slideouts at the same docking spot. I personally made the help external, and closed the Dynaimc help window, and never saw the problem again. Steve. if(E_NOINTERFACE == pThat->QueryInterface(IID_IUnknown,(void**)&pUnk)) { // I aint no pUnk bitch! }
-
Yes, so do I:) And I expect that a radical new product is going to have faults. But it makes you wonder: a) what kind of QA department does microsoft have for .NET? A lazy one? Or was this a premature release forced by management? b) why didn't microsoft set up a mechanism for reporting errors? Incidentally, Delphi 7 is available if you ever want to develop applications which run on Lunix as well as Microsoft platforms! btw. how is life in SA these days? I used to live in Springs, outside Jo'burg on the Gencor mining properties, but I left back in 1986 for Australia, then Britain, then America... Only change is constant
Alastair Stell wrote: Or was this a premature release forced by management? I would say that is the actual case. BillyG was very pushy about getting .NET out on the time he said, and I would hate to be the project manager who has to tell BillyG that his baby is not quite ready for prime time. :-D Alastair Stell wrote: how is life in SA these days? I love it here, but then I have a good job and live in Cape Town. I would say we are on the right track, but it is going to take time. How is/was Australia/Britian/America? :) regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
-
The one I hate is when the properties window refuses to show itself and I have to stop and start visual studio to make it reappear :mad: :mad: :mad: :mad: :mad: - happens both at home and at work
Stupidity dies. The end of future offspring. Evolution wins. - A Darwin Awards Haiku
Shaun Wilde wrote: hate is when the properties window refuses to show itself and I have to stop and start visual studio to make it reappear That is odd. That happened to me a lot when I was using BETA 2, but it has not happened since I obtained the release version. Though I must admit I am more careful with the tabs than before. One thing I wish VS.NET had was a Tab Preset. i.e. In Macromedia Fireworks I open up all the Toolwindows/Tabs I want and then I can press Tab to hide or show them all at once. That way I can very quickly swap between a nice uncluttered full screen while coding/designing and then when I need a tool or window I just hit tab. Might be a good idea to make a macro like that actually :) regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
-
I really do like .NET, but just like the James Bond films says "We've inserted hundreds of bugs so the Users will be forced to pay for expensive upgrades for years to come". The fault Okay. Create a form, with a label, then set the opacity of the form to 80% (any number other than 100% will do). Now reposition the label using code (I was actually repositioning the label to follow the mouse on each mousemove). Note that any window behind your semi-opaque form is corrupted by the label each time it gets moved. This is probably because the semi-opaque form, or perhaps the label itself, is keeping a background image which is used to restore areas of hidden windows as they are re-exposed. It is probably this image which is erroneously written back to the wrong area of the screen because the label itself has now moved. If this is yet another microsoft feature, it's a strange one. Only change is constant
Question: Do the faults outweigh the good stuff? And if so, by how much? Question: Have you ever really stood back for a minute and took in the size of the framework? Not just the size in terms of all the classes it comes with, but also the size in terms of the ideas they've thrown in. Question: Have you ever stopped to think that this is actually a first release (and a pretty good one at that) for the framework and that it can only get better with time? I think alot of these bugs will be worked out soon enough. For now we have to settle for a few workarounds instead, just like always :-) ASP.NET can never fail as working with it is like fitting bras to supermodels - it's one pleasure after the next - David Wulff