C / C++ / MFC

Roger Allen3-May-02 2:48

Roger Allen

3-May-02 2:48

For dialog boxes, I dont think the OnCommandUI handler work. Try mapping the WM_INITMENUPOPUP message and enabling/disabling the menu items there.

Roger Allen
Sonork 100.10016

If I had a quote, it would be a very good one.

Tom Archer3-May-02 3:14

3-May-02 3:14

As Roger states you need to handle the WM_INITMENUPOPUP message without the doc/view architecture there to help you. Here's the code to do that (it will also make sure that your commandui handlers are called before the menu appears).

BEGIN_MESSAGE_MAP(CDialogContextMenuDlg, CDialog)
 ...
 ON_WM_INITMENUPOPUP()
END_MESSAGE_MAP()

...

void CYourDlg::OnInitMenuPopup( CMenu* pMenu, UINT index, BOOL )
{
 CCmdUI CmdUI;
 CmdUI.m_nID = pMenu->GetMenuItemID(index);
 CmdUI.m_nIndex = index;
 CmdUI.m_nIndexMax = pMenu->GetMenuItemCount();
 CmdUI.m_pMenu = pMenu;
 CmdUI.DoUpdate(this,FALSE);
}

Cheers,
Tom Archer
Author, Inside C#

A total abstainer is one who abstains from everything but abstention, and especially from inactivity in the affairs of others.

Roger Allen3-May-02 4:52

Roger Allen

3-May-02 4:52

Cool Tom,

I would have done it a slightly different way. Namely handled the calls to enable/check etc myself in the handler. I will have to remember this.

Big Grin | :-D

Roger Allen
Sonork 100.10016

If I had a quote, it would be a very good one.

Tom Archer3-May-02 5:18

Am i defining this struct wrong?

3-May-02 5:18

No problem. I definitely like this way because it then allows you to use the same command and updateui code that you would use in a normal doc/view class. This handler (InitMenuPopup) then simply routes everything the way it should be.

Cheers,
Tom Archer
Author, Inside C#

A total abstainer is one who abstains from everything but abstention, and especially from inactivity in the affairs of others.

3-May-02 1:34

typedef struct _ID3Info
{
	char		Title[33];
	char		Artist[33];
	char		Album[33];
	char		Year[5];
	char		Genre;
	char		Comment[33];
} ID3Info, *pID3Info;

when i define it that way Visual C++ compiler says: "error C2011: '_ID3Info' : 'struct' type redefinition"

what am i doing wrong?

Thanks

.::RockNix::.3-May-02 1:44

.::RockNix::.

3-May-02 1:44

Delete the struct name in the first line :

typedef struct
{
.
.

So far ... RockNix///

------------------------------------
www.klangwerker.de

Need some articles about Threading,
Subclassing, Double Buffering ?
Go for it ...

Look out for free Win32
Serial Communication Module
for VC++ or Borland C++ Builder

Visit us on www.klangwerker.de
------------------------------------

Tom Archer3-May-02 3:17

3-May-02 3:17

The name after the struct is a "tag". The posters problem is elsewhere.

Cheers,
Tom Archer
Author, Inside C#

A total abstainer is one who abstains from everything but abstention, and especially from inactivity in the affairs of others.

Maxwell Chen3-May-02 1:58

Maxwell Chen

3-May-02 1:58

I think what you wrote is correct. I used to code NI's drivers with many of such struct typedefs.

And 3 minutes ago I copied your struct and pasted onto a console project and a MFC project, both of them compiled without an error!

Maybe you post the entire build log, and we could find out what happened.....

Maxwell Chen
No code is good code.

3-May-02 2:47

Where is the entire build log located?

Maxwell Chen3-May-02 2:52

Maxwell Chen

3-May-02 2:52

You may rebuild all again, and copy the content in the Build tab of the Output window.

Or you may copy what in the .plg file....

Maxwell Chen
No code is good code.

Navin3-May-02 3:00

Navin

3-May-02 3:00

Anonymous wrote:
when i define it that way Visual C++ compiler says: "error C2011: '_ID3Info' : 'struct' type redefinition"

From the looks of it, it seems that _ID3Info is somehow aready defined. It could be that:
1. You have a struct of that name defined somewhere else
2. Perhaps you don't have "include guards" in the header file that defines the struct, and it is getting pulled in twice. I always do something like this to ensure that #2 does not happen:

#ifndef _whatever_your_h_file_name_happens_to_be_
#define _whatever_your_h_file_name_happens_to_be_

(code of the include file goes here)

#endif

No generalization is 100% true.
Not even this one.

Brian Delahunty3-May-02 4:11

Brian Delahunty

3-May-02 4:11

Navin wrote:
#ifndef _whatever_your_h_file_name_happens_to_be_
#define _whatever_your_h_file_name_happens_to_be_

(code of the include file goes here)

#endif

You could also use:

#pragma once

instead of the above ... however the above woudl be the more standard way of doing things Big Grin | :-D

(-_-)

Navin3-May-02 4:27

Navin

3-May-02 4:27

Brian Delahunty wrote:
#pragma once

Yes, my way would be more "standard", but yours is prettier. Big Grin | :-D

No generalization is 100% true.
Not even this one.

Brian Delahunty3-May-02 4:40

Brian Delahunty

3-May-02 4:40

Navin wrote:
Yes, my way would be more "standard", but yours is prettier.

Thanks Wink | ;)

(-_-)

Tom Archer3-May-02 3:20

3-May-02 3:20

Like Navin, your struct compiles fine in my code. I think if you follow his advice you'll find the source of your problem.

Cheers,
Tom Archer
Author, Inside C#

A total abstainer is one who abstains from everything but abstention, and especially from inactivity in the affairs of others.

Link problem (using avifile)

Brian Delahunty3-May-02 4:12

Brian Delahunty

3-May-02 4:12

Navin wrote:
#ifndef _whatever_your_h_file_name_happens_to_be_
#define _whatever_your_h_file_name_happens_to_be_

(code of the include file goes here)

#endif

You could also use:

#pragma once

instead of the above ... however the above woudl be the more standard way of doing things Big Grin | :-D

(-_-)

Zizilamoroso3-May-02 1:23

3-May-02 1:23

Again some newbie-problems Poke tongue | ;-P

I want to use the AVIFile API in my c++ project. Including the "Vfw.h" header file is not a problem, the various datatypes such as PAVIFILE can be used.

But when the project tries to link to the windows dll (mswfv32.dll), the linker says:

Linking...
AviKaka.obj : error LNK2001: unresolved external symbol _AVIFileInit@0
AviKaka.obj : error LNK2001: unresolved external symbol _AVIFileExit@0
Debug/MultiKaka.exe : fatal error LNK1120: 2 unresolved externals

I've already tried to add the dll manualy in project->settings->debug->additional_dlls

So, I guess this is probably a how-to-call-a-dll-topic Confused | :confused:

Inluding the headerfile is not enough Confused | :confused:

[VISUAL STUDIO 6.0] [MFC] [WIN98/2]

Bluute tette! Dead | X|

3-May-02 1:37

Are you sure that the definition and prototype of _AVIFileInit is the same?

Zizilamoroso3-May-02 1:52

3-May-02 1:52

Yep, source found on msdn library.

[VISUAL STUDIO 6.0] [MFC] [WIN98/2]

Bluute tette! Dead | X|

.::RockNix::.3-May-02 1:37

.::RockNix::.

3-May-02 1:37

There are two ways to use a DLL:

1) static use

You need a header-file and a lib-file added to your project. Than you can directly call the functions declared in the header file.

(Due to the linker errors it seems the lib-file is missing in your project, adding only the dll won`t work)

2) dynamic use

You only need the dll-file. From your source you load the dll by calling LoadLibrary() and get the function pointers by calling GetProcAdress().

So far ... RockNix///

------------------------------------
www.klangwerker.de

Need some articles about Threading,
Subclassing, Double Buffering ?
Go for it ...

Look out for free Win32
Serial Communication Module
for VC++ or Borland C++ Builder

Visit us on www.klangwerker.de
------------------------------------

Zizilamoroso3-May-02 1:55

3-May-02 1:55

the lib-file is not missing. checked it.

Is there a way to view the dll member functions, (not the headerfile)? maybe they've changed.

If I use it dynamicaly, can I use the dll-functions more or less in the same manner?

[VISUAL STUDIO 6.0] [MFC] [WIN98/2]

Bluute tette! Dead | X|

Maxwell Chen3-May-02 2:01

Maxwell Chen

3-May-02 2:01

frisco wrote:
Is there a way to view the dll member functions

Use the depends.exe tool comes with your VC++.

Maxwell Chen
No code is good code.

.::RockNix::.3-May-02 2:08

.::RockNix::.

3-May-02 2:08

Within Visual Studio 6.0 there is a tool called "DUMPBIN".

Copy this to your DLL Path and type the following line from a console:

dumpbin /exports yours.dll

A list of the exported functions should be shown.

So far ... RockNix///

------------------------------------
www.klangwerker.de

Need some articles about Threading,
Subclassing, Double Buffering ?
Go for it ...

Look out for free Win32
Serial Communication Module
for VC++ or Borland C++ Builder

Visit us on www.klangwerker.de
------------------------------------

3-May-02 3:42

Add vfw32.lib in Project|Settings|Link, Object/Library modules. It's not a static lib but an import lib (you can tell because it contains only names). Your exe will link at runtime to the right dll and more importantly will compile ok too. tried just now with this fantastic test program:

#include <windows.h>
#include <vfw.h>

int WINAPI WinMain(HINSTANCE,HINSTANCE,LPSTR,int) {
AVIFileInit();
AVIFileExit();
return 0;
}

(I think you can only do the thing with putting libs into your project with static libraries, which contain code as well as import names, but I'm not sure.)

Zizilamoroso3-May-02 2:42