|
I know this is not my thread, but I have to ask this...
Last time I checked this out, I walked away thinking I could not do this and utilize MFC extension librairies. Is this still the case?
Not saying this would impact the OP's project but if this is still a limitation, it might be worth mentioning.
|
|
|
|
|
Thank you both
36. When you surround an army, leave an outlet free.
...
Do not press a desperate foe too hard.
SUN-TZU - Art of War
modified on Sunday, July 17, 2011 11:34 PM
|
|
|
|
|
I am using VS2003. I need to implement hover effect on a button. I tried with VS2008 using owner draw button and its working fine.
But VS2003 do not recognize below messages:
ON_WM_MOUSEHOVER()
ON_WM_MOUSELEAVE()
Without these messages how to implement hover effect over a button. please suggest...
|
|
|
|
|
|
That is fine but how call WM_MOUSELEAVE so that I will get to know about mouse is leaving the area.
|
|
|
|
|
Did you look at the example in the link?
|
|
|
|
|
Yes the example also says about WM_MOUSELEAVE event.
Please you also have a look and suggest some alternate...
|
|
|
|
|
If you're asking how to do this in MFC, you must use the ON_MESSAGE macro -
ON_MESSAGE( WM_MOUSELEAVE,OnMouseLeave)
ON_MESSAGE( WM_MOUSEHOVER,OnMouseHover)
|
|
|
|
|
I know how to use, I have implement the hover effect using VS 2008 but the above said messages are not supported by VS2003.
Can suggest me how to do same task in VS2003
|
|
|
|
|
Thanks superman, Its done.
Thanks for help
|
|
|
|
|
Hi
I am opening my VC++6.0 application in VS2008 and getting the above error. what setting needs to be done for this to port this application in VS2008.
Also if I am porting this application to VS2008, will it work in Visual Studio Pro 2010?
SNI
|
|
|
|
|
SNI wrote: I am opening my VC++6.0 application in VS2008 and getting the above error. what
setting needs to be done for this to port this application in VS2008.
Have you tried this?
SNI wrote: Also if I am porting this application to VS2008, will it work in Visual Studio Pro 2010?
Possibly, but much like porting from VS6 to VS2008, you may encounter conversion problems, though they may be fewer.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Some people are making such thorough preparation for rainy days that they aren't enjoying today's sunshine." - William Feather
|
|
|
|
|
Hello,
In Visual Studio, while creating MFC application, we got Runtime Library setting in C\C++ node in Project Propery Dialog. It have different options, what is exact meaning of these.
|
|
|
|
|
Take a look at the options offered. In my system I have the following options:
- Multi-threaded : a static library that supports threading
- Multi-threaded Debug : as above, that includes debug information
- Multi-threaded DLL : a dynamic library that supports threading
- Multi-threaded Debug DLL : as above, that includes debug information
These are versions of the C/C++ basic runtime libraries, and are purely to support the language. You add extra libraries to your project to support Win32 and MFC/ATL as required. Note that most required libraries are added to your project when it is created by the New Project wizard in Visual Studio.
The best things in life are not things.
|
|
|
|
|
Hello All,
I am C++/MFC devloper. I have been working with dll/com/mfc from few years now, but I always have confusion, what is exact diffrence in Static,Dynamic,Shared library. Moreover when I use shared library it creates lib file and then I link with lib file to reuse source code.
My assumption about 'lib vs dll' was like '.h vs .cpp'. Is my assumption correct?
Wherever I work with multiple project I got huge number of linker errors.
Happy Programming.
|
|
|
|
|
Pranit Kothari wrote: what is exact diffrence in Static,Dynamic,Shared library You may find some useful information at Library (computing) page at Wikipedia[^].
Pranit Kothari wrote: My assumption about 'lib vs dll' was like '.h vs .cpp'. Is my assumption correct? It is a good analogy.
Pranit Kothari wrote: Wherever I work with multiple project I got huge number of linker errors. That's a practical problem that might be solved if you post the exact error message here.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
|
I've to set the 'Loudness Equalization' property of the speakers to true. I'm referring to the MSDN DOC file (Vista_SysFX.Doc) from here[^]. But the compiler give error for CreateAudioMediaType() function saying it requires 3 parameter (prototype
STDAPI CreateAudioMediaType(const WAVEFORMATEX* pAudioFormat, UINT32 cbAudioFormatSize, IAudioMediaType** ppIAudioMediaType) ).
But when I follow this prototype, it gives me linker error for this function. Is there any SDK mismatch or version mismatch in DLLs?
Or is there any other alternative API to set the system speakers 'Loudness Equalization' property.
Thanks in advance.
|
|
|
|
|
Malli_S wrote: it gives me linker error for this function.
I'm guessing at what your error is since you did not add the details here. Have you included the required library in your project as detailed here[^]?
The best things in life are not things.
|
|
|
|
|
Yes, I tried that.
The funniest part is any of the files (Mtype.h or Streams.h) isn't found when included, neither the lib. But when I change the function for 3 parameter, it gets compiled and fails to link. Even I was wondering about this prototype mismatch.
|
|
|
|
|
Malli_S wrote: fails to link.
Well you mentioned that already, but you still have not posted any error messages which might help us to help you.
The best things in life are not things.
|
|
|
|
|
for this
hr = CreateAudioMediaType(&wfx.Format, &pAMTOut);
I get this error :
error C2660: 'CreateAudioMediaType' : function does not take 2 arguments
And when i change the code to this
hr = CreateAudioMediaType(&wfx.Format, wfx.Format.cbSize, &pAMTOut);
it gets compiled. But gives this linker error:
error LNK2019: unresolved external symbol _CreateAudioMediaType@12 referenced in function "void __cdecl useAPO(void)" (?useAPO@@YAXXZ)
|
|
|
|
|
Malli_S wrote: error C2660: 'CreateAudioMediaType' : function does not take 2 arguments
The doc is here[^], and the API takes 3 arguments. The last one is a BOOL, and you're passing the address of pAMTOut, which doesn't look cool.
Malli_S wrote: error LNK2019: unresolved external symbol _CreateAudioMediaType@12 referenced in function "void __cdecl useAPO(void)" (?useAPO@@YAXXZ)
The doc (again) says that you need to link to streambase.lib . If you aren't doing that, you should either change your project settings to link to it, or do it from your code:
#pragma comment(lib, "streambase.lib")
"Real men drive manual transmission" - Rajesh.
|
|
|
|
|
Yes, the MSDN doc says the last parameter is BOOL. And when I googled, I found three different prototypes.
|
|
|
|
|
Malli_S wrote: Yes, the MSDN doc says the last parameter is BOOL. And when I googled, I found three different prototypes
I think it would be wise to go with what MSDN says.
"Real men drive manual transmission" - Rajesh.
|
|
|
|