Re: How to use string ID in MessageBoxW () ?
From: Alexander Grigoriev (alegr_at_earthlink.net)
Date: 10/23/04
- Next message: Bansi: "Using windows INI files"
- Previous message: Alexander Grigoriev: "Re: Bug in win xp: Auto-detaching modeless dialog."
- In reply to: Ian Semmel: "Re: How to use string ID in MessageBoxW () ?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 22 Oct 2004 21:30:44 -0700
The difference is most noticeable when you're trying to add several handlers
or variables to the class. In VS7, you have to go back after every item. It
just plain sucks.
"Ian Semmel" <isemmel@removejunkmailrocketcomp.com.au> wrote in message
news:2004102334433.290617@rocket-hp...
Well, apart from the fact that it is incredibly slow to react (on my
machine), the absence of ClassWizard is to me the major problem.
Sure, the info is there, but not in the convenient property *** form of
VS6 where you have a concise picture of the control variables you have added
and messages being used. In VS6, right-clicking in a source window will
bring up a menu allowing you to activate ClassWizard. In VS7, it appears you
only have the choice of 'Synchronise Class View'. I can then see my control
variables but I then have to right-click on one of them and select
'Properties' to see what resourceID it applies to. Perhaps they could have
added this info to Object Browser (which is good)
I don't understand why some things were changed. Why, eg, was something as
simple as 'Set Active Project' changed. Other things like the gratuitous
breaking of the CTime class really annoy me.
I am making an effort to use VS7 now.
Like it's almost there. If only they could have spoken to someone who
actually uses MFC before releasing the product.
On Fri, 22 Oct 2004 19:11:22 +1000, Mihajlo Cvetanovic wrote:
> Joseph M. Newcomer wrote:
>> CStringW in VS7; it doesn't exist in VS6 (this is one the great
>> improvements in MFC for
>> VS7, which is why I resent the totally screwed up GUI that makes it so
>> hard to use the
>> nice features that MFC and the C compiler now support)
>
> I'm so used to new GUI that I honestly can't find anything wrong with
> it. It took me approx. 5 mins to find any item that changed its place
> from VC6 (exception was the Project Properties, for a few days I thought
> it disappeared from VS7). What's so bad about new GUI?
- Next message: Bansi: "Using windows INI files"
- Previous message: Alexander Grigoriev: "Re: Bug in win xp: Auto-detaching modeless dialog."
- In reply to: Ian Semmel: "Re: How to use string ID in MessageBoxW () ?"
- Messages sorted by: [ date ] [ thread ]