|
-
March 3rd, 2003, 09:20 AM
#1
MFC Static link vs MFC Shared DLL Issues
My program is behaving differently when I link with MFC statically vs. when I link with MFC as a shared DLL. (In both cases I an using a debug build, so this is not a debug/release issue.)
The first issue I noticed is with the CRectTracker. When I use a RectTracker while linking with a shared DLL everythink works correctly. The cursor changes when over the rect to a cross and the user can move the rect around the screen. But, when linking with with static MFC the rect tracker does not behave correctly. After the rect tracket is displayed, moving the cursor over the rect makes the cursor disapear. It does not change to the cross, it just disappears when over the tracking rect.
Any ideas what I can be doing wrong? Any ideas why this is and what I can do about it? Thanks!
Craig Smith
-
March 3rd, 2003, 09:39 AM
#2
Your best bet would be to post a small sample project that displays this behavior. As it is, I'm not even sure where to begin guessing...
bytz
--This signature left intentionally blank--
-
February 11th, 2011, 02:46 PM
#3
-
February 11th, 2011, 04:59 PM
#4
Re: MFC Static link vs MFC Shared DLL Issues
Good post in some way Sasha but these days most programmers have abandoned VS6 for something more compliant.
-
February 11th, 2011, 10:24 PM
#5
Re: MFC Static link vs MFC Shared DLL Issues
Wow, this thread died years ago, I'm surprised that anyone would post to it.
bytz
--This signature left intentionally blank--
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|