IsWindow()! IsWindow()! Not IsWindowEnabled()!

[scs0]

I have the misfortune of using the buggy software embarrassment known
as Visual Studio.NET 2003. One of the things that drives me insane
with this software is how I cannot type the function IsWindow(). As
soon as I try typing that word the UI "helps" me by turning it into
IsWindowEnabled(). I type in the letter of the function name and then
hit Shift+9 to insert the '(' and BAM! It often becomes
IsWindowEnabled(). I think it's part of that tool that pops up the
members within an object, you know, that little menu that pops up just
enough for you to get used to its functionality but not enough that it
actually works reliably?

It's bad enough I have to code to this halfassed API on this buggy
VS.NET POS, but does the editor really need to actively write bugs
into my code? Is this what Microsoft has come to now?

[Mattias Sjögren]

>I have the misfortune of using the buggy software embarrassment known
as Visual Studio.NET 2003. One of the things that drives me insane
with this software is how I cannot type the function IsWindow(). As
soon as I try typing that word the UI "helps" me by turning it into
IsWindowEnabled(). I type in the letter of the function name and then
hit Shift+9 to insert the '(' and BAM! It often becomes
IsWindowEnabled(). I think it's part of that tool that pops up the
members within an object, you know, that little menu that pops up just
enough for you to get used to its functionality but not enough that it
actually works reliably?

Since you're calling IsWindow I'm going to assume that you're coding
in C or C++. Since the IntelliSense behavior and settings differ
between languages, I suggest you post your question to the VC++
newsgroup microsoft.public.dotnet.languages.vc.
Mattias

--
Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.