Re: using OpenFileDialog
- From: burt@xxxxxxxxxxxxxxxxx (Burt Johnson)
- Date: Sat, 23 Apr 2005 06:56:35 GMT
William DePalo [MVP VC++] <willd.no.spam@xxxxxxxx> wrote:
> Some rambling ...
>
> 1) I think I heard that there are "millions" of pages on MSDN. Keeping it
> straight in magnetic or gray matter is a huge undertaking. :-)
>
> Google is good at that sort of thing so I tend to use it to find things on
> MSDN. Just append
>
> site:msdn.microsoft.com
>
> to a google query.
Good suggestion. I'll keep it in mind. I often find references to MSDN
in my Google searches even without adding the site though.
>
> 2) If you don't find what you need, or if you don't go there first, come
> back here. Chances are that someone will help you out.
I was delighted to have the answer in under an hour. :-)
I used to frequent the programming lounges that related to my work (Mac
for 15 years, Java for 7 years, etc). I have been pretty much out of
the game for the past 3 years though (dot-bomb bit me, and suddenly my
35 years of experience was a liability rather than an asset), and am
just getting back into it. This is my first foray into Windows
programming via C++. I've written several Java apps for Windows though.
>
> 3) It is usually best to describe _what_ you want to do and not _how_ you
> want to do it. I was about to answer the question you asked when I realized
> you probably didn't want to go down that path.
I didn't even realize there were separate frameworks for managed and
unmanaged code until this thread. I thought that was just a compiler
flag that redefined Object constructors/destructors to manage memory for
me. Shows how little I know about this new game... I've only been in it
for 2 weeks. :-)
In this case, I knew I wanted to open a file, so I Googled and found
OpenFileDialog. Looked reasonable, so I went to use it and hit a
completely unexpected wall. I never even thought that might not be the
right Class for unmanaged code.
>
> 4) Due to personal bias and experience, I don't usually suggest MFC
> solutions to problems. But _you_ might want to look at its CFileDialog class
> as it probably best approximates the .Net class you happened on in the docs
I have no choice in the matter. The client has almost 10 years of
legacy code that is being enhanced for version 10. There is some C#
work being done on new subsystems, but the section I am in uses VC++
MFC, so that is what I need to learn quickly.
--
- Burt Johnson
MindStorm, Inc.
http://www.mindstorm-inc.com/software.html
.
- Follow-Ups:
- Re: using OpenFileDialog
- From: Ioannis Vranos
- Re: using OpenFileDialog
- References:
- using OpenFileDialog
- From: Burt
- Re: using OpenFileDialog
- From: William DePalo [MVP VC++]
- Re: using OpenFileDialog
- From: Burt
- Re: using OpenFileDialog
- From: William DePalo [MVP VC++]
- using OpenFileDialog
- Prev by Date: Re: using a DLL function in a header file
- Next by Date: Re: invoke problem
- Previous by thread: Re: using OpenFileDialog
- Next by thread: Re: using OpenFileDialog
- Index(es):
Relevant Pages
|