A pop up window with controls, unknown control IDs

Hi,

I'm using MS VC++ 6.0.
I've been following a tutorial to create a pop up window with 3 buttons: Open, Cancel and Connect. In the resource file I'm trying to define these controls but I keep getting an error:

Code:

---

SelectBafFile DIALOG 0, 0, 300, 200

CAPTION "BAF File Selection"

STYLE DS_MODALFRAME | WS_VISIBLE | WS_CAPTION | WS_SYSMENU

{

// Controls for the dialog will go here

        DEFPUSHBUTTON "Cancel", IDCANCEL,174,35,50,14,WS_VISIBLE | WS_CHILD | WS_TABSTOP

        PUSHBUTTON "Open" ,IDB_OPEN,174,18,50,14,WS_VISIBLE | WS_CHILD | WS_TABSTOP
        PUSHBUTTON "Connect" ,IDB_CONNECT, 174, 52, 50, 14, WS_VISIBLE | WS_CHILD | WS_TABSTOP

}
  AND THE ERROR:

       

Code:

       

---

error RC2104 : undefined keyword or key name: IDB_OPEN
Error executing rc.exe.

---

---

If I use IDOK or IDCANCEL it is fine, otherwise it gives an error. what did I forget to add?
Thanks.

I simply had to add thi sin the resource.h for the project:

Code:

---


#define IDB_CONNECT                                                1013
#define        IDB_OPEN                                                1014
#define        IDB_CANCEL                                                1015

---

that did it. I'm just not sure where the 1013-1015 will come into play.

If you are manually creating all of your resources/controls, it won't make a difference. The values just need to be unique identifiers. IDYES and IDNO worked because they are defined in the MFC headers. If you manually add controls to a MSVC-generated resource file things can get a little messy, but there really isn't much more to it than you've discovered.

That's what I thoughtt too.

Thanks for acknowledgement.

AS.

>>I'm just not sure where the 1013-1015 will come into play.

Each controls/dialog or window has an int ID number that distingushes it. When the OPEN button is pressed your app generates a message (a BN_CLICKED = Button Notification Clicked).
This message is sent to the parents (owners) function for processing messages (callback).
The callback must then decide which button was pressed and so what it must do.

There are two ways of telling which button was pressed, the buttons HWND or its ID. The HWND will change each time the app is run but the ID remains constant.

Programmers understand case IDB_OPEN:
the code understands case 1014:

That makes a lot of sense thanks.

AS.