C / C++ / MFC

CrazySkydiver7-Aug-02 7:45

CrazySkydiver

7-Aug-02 7:45

Any chance of posting some code to do that ?

Pretty please with sugar on top (this is good magic sugar and it's not bad for your teeth) Smile | :)

Cheers.
P.S. If you're not living life on the edge you're taking up too much room.
From Crazy Skydiver.

C^hris L^osinger7-Aug-02 7:47

7-Aug-02 7:47

void CMainWindow::Whatever()
{
   CDialogA a;
   a.DoModal();
   if (a.m_flag==1)
   {
      CDialogB b;
      b.DoModal();
   }
}


....


void CDialogA::OnMagicButton()
{
   m_flag = 1;
   OnOK();
}

WWJD? JWRTFM.
found on /.

CrazySkydiver7-Aug-02 9:12

CrazySkydiver

7-Aug-02 9:12

I am wondering if I have gone about this project the wrong way round.

I firstly designed the displays. One intro window with some buttons, each button would take you to a different window depending on what you pressed and those windows would all have different functions and applications.
Only problem is that I can't seem to link the command button on the intro screen to open the next level.

First menu is IDD_SKYDIVE. It has several command buttons. One of which is labled Carear.

The code for it is:-

void CSkydiveDlg::OnCarear()
{
//so when the button is clicked it does whats in here..... am I right so far, and if I am right what code goes in here ?
}

I want it to open another Dialog called IDD_CAREARMODE and shut down it's own window. I think this is where I am getting mixed up.... yet I'm not exactly sure how.

Cheers.
P.S. If you're not living life on the edge you're taking up too much room.
From Crazy Skydiver.

7-Aug-02 8:00

Well, why don't you create a new object of the class of the dialog box that you want to open?

e.g.
put this code in the command handler of the button:

CMyDialog mydlg;
mydlg.DoModal();

Why do your need a flag after all?!

Cheers

C^hris L^osinger7-Aug-02 8:06

7-Aug-02 8:06

because he said he wants the first dialog to go away before the second one comes up.

WWJD? JWRTFM.
found on /.

CrazySkydiver7-Aug-02 8:58

CrazySkydiver

7-Aug-02 8:58

No, I mean I have my windows designed and laid out and I just want to code the button so it closes down the window it was clicked in and opens up another window specific to the button that was clicked..... Does that make sense ?

** I am really new to Visual C++..... I am supposed to make a basic game in it. **

(Still not got the thing to work though)

Cheers.
P.S. If you're not living life on the edge you're taking up too much room.
From Crazy Skydiver.

Is WinAPI programming prereq for MFC

JohnnyG7-Aug-02 9:17

JohnnyG

7-Aug-02 9:17

I haven't done this in MFC yet but I think it would be something like this.
In the button handler for the first dialog, DlgA....

void DlgA::OnButton1Click()
{
   CMyDialog MyDialog();                    // this is the 2nd dialog
   MyDialog.Create(..parameters if needed); // create it
   MyDialog.ShowWindow(true);               // then show it

   // quit or close this dialog... Post WM_QUIT or DestroyWindow() or whatever
   // so that this dialog, DlgA, closes.  It will happen so fast before DlgB
   // displays itself
 }

TigerNinja_7-Aug-02 7:29

TigerNinja_

7-Aug-02 7:29

I bought this book "Windows 98 Programming" by Schildt [osborne/mc graw hill] on sale for $5, and this guy says you must learn Win32 API before learning MFC, is this true ?

I thought MFC was an abstraction away from WinAPI calls. Confused | :confused:

Soliant | email

"The whole of science is nothing more than a refinement of everyday thinking." -Albert E.

C^hris L^osinger7-Aug-02 7:37

7-Aug-02 7:37

you will still need to learn some of the Win32 API. MFC doesn't hide all of the details. plus it certainly helps to understand what the various MFC classes are actually doing (especially when it comes to GDI objects).

-c

WWJD? JWRTFM.
found on /.

User 66587-Aug-02 7:46

User 6658

7-Aug-02 7:46

Well, you needn't, but it makes life alot easier if you have at least basic knoledge in Win32 API. MFC is not a very deep abstraction of the API, e.g. many funcions like adding an entry into a combobox AddString() do nothing else but directly calling Win32 API (SendMessage e.g.)

I have my own philosophy: I use MFC to create dialogs or MDI/SDI apps, but still use very much API calls directly.
Furthermore not every single API call is encapsulated by an MFC class, that's why you often must use API to get things to work.

reagards
Greg

modified 12-Sep-18 21:01pm.

TigerNinja_7-Aug-02 8:02

TigerNinja_

7-Aug-02 8:02

Thanks guys, you think Jeff Prosise "Programming MFC" is a good way to go?

Soliant | email

"The whole of science is nothing more than a refinement of everyday thinking." -Albert E.

Rob Caldecott7-Aug-02 9:18

Rob Caldecott

7-Aug-02 9:18

Yes, yes, YES! One of the best books - possibly THE best one. You will not be disappointed.

Cheap sex and sad films. Help me get where I belong.

Rob Caldecott7-Aug-02 9:15

Rob Caldecott

7-Aug-02 9:15

It'll be a MASSIVE advantage as MFC is only a very thin wrapper for the Win32 API.

Stop sending letters. Letters always get burned.

Ravi Bhavnani7-Aug-02 9:44

Ravi Bhavnani

7-Aug-02 9:44

Soliant wrote:
you must learn Win32 API before learning MFC, is this true ?

"Yes", if you want to fully understand MFC and program in it.

"No", if you're coming from an X/Motif/Mac/Qt/Tcl background and just want to create a one-off Windows app.

/ravi

Let's put "civil" back into "civilization"
http://www.ravib.com
ravib@ravib.com

Christian Graus7-Aug-02 10:04

Christian Graus

7-Aug-02 10:04

Not at all - I think it's better to learn MFC then learn what the Win32 API is doing for you, because you can learn incrementally instead of all at once.

Christian

We're just observing the seasonal migration from VB to VC. Most of these birds will be killed by predators or will die of hunger. Only the best will survive - Tomasz Sowinski 29-07-2002 ( on the number of newbie posters in the VC forum )

Cats, and most other animals apart from mad cows can write fully functional vb code. - Simon Walton - 6-Aug-2002

zeki yugnak7-Aug-02 10:16

zeki yugnak

7-Aug-02 10:16

hi
how way to follow learn to mfc."programing windows jeff prosise" this book is very good.but other good books are which? Unsure | :~

Shog⁹7-Aug-02 10:25

Shog⁹

7-Aug-02 10:25

zeki wrote:
but other good books are which?

Here's one for ya! Smile | :)

---

Shog⁹
If I could sleep forever, I could forget about everything...

zeki yugnak7-Aug-02 13:44

zeki yugnak

7-Aug-02 13:44

sorry...

may english is not good..

Cry | :((

Shog⁹7-Aug-02 13:51

Shog⁹

7-Aug-02 13:51

Hey, no worries - don't take it as a slam, it really *is* a good book! Smile | :)

---

Shog⁹
If I could sleep forever, I could forget about everything...

Tomasz Sowinski7-Aug-02 10:17

Tomasz Sowinski

7-Aug-02 10:17

Soliant wrote:
I thought MFC was an abstraction away from WinAPI calls.

Yes, but (fortunately) the abstraction is just a pretty thin wrapper on API. I'd say API knowledge is big advantage.

Tomasz Sowinski -- http://www.shooltz.com

What is "scratch" and why can everything be made from it?

Michael P Butler7-Aug-02 22:16

Michael P Butler

7-Aug-02 22:16

You don't need to know it. For my first year back in 1993, I pretty much managed without knowing too much API. Over the years though, you soon realise it's nice to know the API too - especially when hitting the limits of MFC's scope.

Michael Smile | :)

Time flies like an arrow. Fruit flies like a banana

VC++ SAX integration

act_x7-Aug-02 7:23

act_x

7-Aug-02 7:23

I am trying to use SAX in my Dialog Based Application .

I have a SAXHandler class that derives from the DocumentHandler that SAX provides.

My Dialog Class has a SAXHandler object and a SaxParser Object .

Cry | :((

I am having problems when I link the project.
Errors I get are of the type

SAXdev.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: virtual __thiscall SAXParser::~SAXParser(void)" (__imp_??1SAXParser@@UAE@XZ)

SAXdevDlg.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: virtual __thiscall SAXParser::~SAXParser(void)" (__imp_??1SAXParser@@UAE@XZ)

SAXdevDlg.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: __thiscall SAXParser::SAXParser(class XMLValidator * const)" (__imp_??0SAXParser@@QAE@QAVXMLValidator@@@Z)

What is the correct method to add the files ?

Please help

Re: VC++ SAX integration

C^hris L^osinger7-Aug-02 7:39

7-Aug-02 7:39

did you implement a constructor and a destructor for your SAXParser object ?

-c

WWJD? JWRTFM.
found on /.

Re: VC++ SAX integration

act_x7-Aug-02 7:51

act_x

7-Aug-02 7:51

I did not . The SAXParser class is in a .hpp class and is as follows :
class PARSERS_EXPORT SAXParser :

public Parser
, public XMLDocumentHandler
, public XMLErrorReporter
, public XMLEntityHandler
, public DocTypeHandler
{
public :
// -----------------------------------------------------------------------
// Class types
// -----------------------------------------------------------------------
enum ValSchemes
{
Val_Never
, Val_Always
, Val_Auto
};

// -----------------------------------------------------------------------
// Constructors and Destructor
// -----------------------------------------------------------------------

/** @name Constructors and Destructor */
//@{
/** Constructor with an instance of validator class to use for
* validation.
* @param valToAdopt Pointer to the validator instance to use. The
* parser is responsible for freeing the memory.
*/
SAXParser(XMLValidator* const valToAdopt = 0);

/**
* Destructor
*/
~SAXParser();
//@}

It was said that in SAX one needs to only implement the Handler class that derives from Documenthandler

then we need to invoke

parser.SetDocumentHandler(& handlerobject)
parser.Parse();

The sample code I referred from a Text book did not have any initialization for the parser object .

Please help

Re: VC++ SAX integration

C^hris L^osinger7-Aug-02 8:08

7-Aug-02 8:08

you can't declare a constructor (or destructor) and not implement it.

at the very least make them do nothing:

~SAXParser()
{
}

SAXParser::SAXParser(XMLValidator* const valToAdopt = 0)
{
}

WWJD? JWRTFM.
found on /.