C / C++ / MFC

Now why doesn't this COMPILE!?!?!?

31-Jul-02 7:07

If you already have a pointer to the tab control (possibly with GetTabControl), GetWindowRect should return its dimensions. Then you can displace the remaining controls upwards in the OnInitDialog of the sheet just like this:

CWnd *pWnd=GetWindow(GW_CHILD);

while(pWnd!=NULL){
    CRect rect;
    pWnd->GetWindowRect(rect);
    rect.OffsetRect(0,-tabHeight); //tabHeight has been previously obtained
    ScreenToClient(rect);
    pWnd->MoveWindow(rect,FALSE);
    pWnd=pWnd->GetNextWindow();
}

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

Tommy Svensson31-Jul-02 6:43

Tommy Svensson

31-Jul-02 6:43

Hi,

I've been staring at this problem for hours and hours... what is wrong?!
This is what I do:

...snip...

CComModule _Module;

BEGIN_OBJECT_MAP(ObjectMap)
OBJECT_ENTRY(CLSID_Lex, CLex)
END_OBJECT_MAP()

/////////////////////////////////////////////////////////////////////////////
// DLL Entry Point

extern "C"
BOOL WINAPI DllMain(HINSTANCE hInstance, DWORD dwReason, LPVOID /*lpReserved*/)
{
    if (dwReason == DLL_PROCESS_ATTACH)
    {
	TCHAR pszLoader[MAX_PATH];
	GetModuleFileName(NULL, pszLoader, MAX_PATH);
	_tcslwr(pszLoader);
	if (_tcsstr(pszLoader, _T("explorer.exe")))
	    return FALSE;

        _Module.Init(ObjectMap, hInstance, &LIBID_LEXBHOLib);
        DisableThreadLibraryCalls(hInstance);
    }
    else if (dwReason == DLL_PROCESS_DETACH)
        _Module.Term();
    return TRUE;    // ok
}

...snap...

I get this error:

---Configuration: LexBHO - Win32 Unicode Release MinDependency--------
Linking...
   Creating library ReleaseUMinDependency/LexBHO.lib and object ReleaseUMinDependency/LexBHO.exp
LIBCMT.lib(crt0.obj) : error LNK2001: unresolved external symbol _main
ReleaseUMinDependency/LexBHO.dll : fatal error LNK1120: 1 unresolved externals
Error executing link.exe.

LexBHO.dll - 2 error(s), 0 warning(s)

But when I comment these lines out...

/*
	TCHAR pszLoader[MAX_PATH];
	GetModuleFileName(NULL, pszLoader, MAX_PATH);
	_tcslwr(pszLoader);
	if (_tcsstr(pszLoader, _T("explorer.exe")))
	    return FALSE;
*/

...things are working just fine. What is wrong with _tcslwr? Because that's where the problems start...

Help is much appreciated,

/Tommy

Joaquín M López Muñoz31-Jul-02 6:47

31-Jul-02 6:47

Ummm... the configuration you have selected (MinDependency) does not link the C run-time library to save space on the final DLL. So, you cannot use any of the functions provided by this library (like vg. _tcslwr). Either change the configuration or avoid calls to the C run-time library.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

Tommy Svensson31-Jul-02 6:50

Tommy Svensson

31-Jul-02 6:50

No, that's not it, but thanks anyway... I have another project that builds with this piece in ReleaseMinSize. That's what's making this thing so strange! What else can make it behave like this?

/Tommy

Joaquín M López Muñoz31-Jul-02 6:57

31-Jul-02 6:57

(Another shot in the dark) Seems like LIBCRT thinks is being linked against a console program instead of a DLL. Check the /subsystem directive in the linker part of the project settings.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

jeffluckett31-Jul-02 7:09

jeffluckett

31-Jul-02 7:09

Under your project settings, make sure that you have chosen one of the "Using MFC" options.

(IE. "Using MFC in a shared .dll" or "Using MFC in a statically linked .dll")

Tommy Svensson31-Jul-02 7:16

Tommy Svensson

31-Jul-02 7:16

No, it works with a project I have and there's no MFC at all. And there shouldn't be!

It must be something else!

Mail me and I'll send the project to anyone who wants it!

/T

pépé2-Aug-02 0:35

pépé

2-Aug-02 0:35

I had the same problem :
- put an empty main funxion somewhere to keep the linker happy
- don't use LIBC funxions
- tell me if you find another solution

Dialog Box & Property Sheet :: MFC

Vagif Abilov2-Aug-02 0:46

Vagif Abilov

2-Aug-02 0:46

This is a famous one. It is cause by _ATL_MIN_CRT preprocessor definition. Look here[^] for details.

Vagif Abilov
MCP (Visual C++)
Oslo, Norway

If you're in a war, instead of throwing a hand grenade at the enemy, throw one of those small pumpkins. Maybe it'll make everyone think how stupid war is, and while they are thinking, you can throw a real grenade at them.
Jack Handey, Deep Thoughts

valikac31-Jul-02 6:35

31-Jul-02 6:35

Hi. I have some fundamental questions about dialog box and property sheet. Most ultimately have to do with program design and memory management.

Dialog Box:

Is the following good program design?

-----
MyBox mBox;

if (mBox.DoModal == IDOK)

// Is it good program design to get data from a dialog box after it has been closed/distroyed?

DataType = mBox.GetData();
-----

Dialog Box & Property Sheet:

What do you think about declare all dialog box and/or property sheets as private data member rather than local data member?

In general, I want to make sure there is not memory leak with dealing with dialog box and/or property sheet and local data members.

Thanks,
Kuphryn

Joaquín M López Muñoz31-Jul-02 6:43

31-Jul-02 6:43

Question 1: It is not only good style, but also about the only reasonable way to retrieve data entered by the user into the dialog. Go ahead with this solution.

Question 2: I don't know how keeping these private will help you prevent memory leaks. Could you be more specific?

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

valikac31-Jul-02 6:50

31-Jul-02 6:50

Thanks.

If you declare a dialog box locally, what if the function goes out of stack? If it is local, you can create a new box and delete each box every time.

Again, I would like to make sure everything is safe and good program design.

Kuphryn

Joaquín M López Muñoz31-Jul-02 6:55

31-Jul-02 6:55

I'm still not very sure about what your question is, but in general you should prefer to declare variables locally rather than as member variables (unless there are compelling reasons not to do so).

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

valikac31-Jul-02 6:56

31-Jul-02 6:56

Here is an example of the second questions.

-----
Class MyClass()
{
void TestFunc();
privete MyDialogBox *dBox;
}

void MyClass::TestFunc()
{
dBox = new MyDialogBox;

if (MyDialogBox->DoModal == IDOK)
...

delete dBox;
dBox = NULL;
}
-----

In the code above, MyDialogBox is created on the heap instead of being a local call.

Kuphryn

Joaquín M López Muñoz31-Jul-02 6:59

31-Jul-02 6:59

It is much better to do it this way:

class MyClass
{
void TestFunc();
};

void MyClass::TestFunc()
{
MyDialogBox dBox;

if (dBox.DoModal() == IDOK)
...

}

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

valikac31-Jul-02 9:11