|
i am posting a wm_destroy.
thanks for the support.
it works fine after i remove the destroy message.
regards,
suresh
|
|
|
|
|
suresh0009 wrote: PostMessage(WM_TIMER,0,0);
Don't make that.
Do you know why your application exits immediately?
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.
|
|
|
|
|
Hi,
I am posting a wm_destroy immediately after creation.
thanks for the support.
timer workd as desired now.
regards,
suresh
|
|
|
|
|
You can't receive a timer notification if you exit your application! 
|
|
|
|
|
Don't use WM_TIMER. Create a thread that posts a custom message at the desired interval. WM_TIMER is the lowest priority message in Windows and you're not guaranteed to get the message.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
I have defined my own list control based on MFC's CListCtrl. When I select items in the list with mouse click, everything works fine, the onItemChanged even has been correctly fired. But when I walk through the list items with arrow keys (up and down), the selected item in the list hasn't been changed.
Does anybody know why?
Maruko
|
|
|
|
|
I finally decided to move an ancient MFC app from VC6 to VS2005. I've had no problems building, but the app (which happens to be dialog based) doesn't seem to honor XP themes. The VC6 version (in which I'd inserted an XML manifest) honors themes and renders buttons correctly[^].
Under VS2005, I started by letting the project wizard generate a minimal dialog based app and selected "manifest support" with the default options. Yet, the app displays buttons like this[^]. I have the usual InitCommonControls() code in the app's InitInstance() but am unable to get it to render controls using the current theme.
I'm probably doing something stupid. A nudge in the right direction would be much appreciated.
Thanks,
/ravi
-- Modified at 13:53 Wednesday 17th January, 2007
Turns out my version of VS2005 is omitting the "Microsoft.Windows.Common-Controls" version="6.0.0.0" entry from the manifest. Manually injecting this into the embedded manifest fixed the problem.
-- End modification
|
|
|
|
|
If your manifest is in your resources, you also have to set the project properties (Manifest/Input and Output tab) to indicate the where to find the manifest resources - as an embedded resource you would point that entry to the $(TargetDir)$(TargetFileName).
Hope that helps.
Karl - WK5M
PP-ASEL-IA (N43CS)
PGP Key: 0xDB02E193
PGP Key Fingerprint: 8F06 5A2E 2735 892B 821C 871A 0411 94EA DB02 E193
|
|
|
|
|
Yes, that's what I did (one for each of the debug/release builds).
Thanks,
/ravi
|
|
|
|
|
Hi,
I have a doubt regarding memory sharing in a COM object.
Background: Recently we shifted to VS2005. Hence the dll written in VC6 is no longer directly useful. I might have to write a COM wrapper to access this dll. The application would be working with huge files and I want only a single copy maintained across my application. The dll should actually read the file and after the error checking send the a pointer of the memory to my application.
My question:
1) Is it possible to do it with COM?
2) What would happen if my COM object memory is on a remote server?
3) Does the COM object copy the memory and send it to the requested application or does it just pass the reference.
My intention is to maintain a single place of memory where the file data would be read and used.
Please let me know how can I achieve this through COM. Any links would be useful.
Regards,
Arti Gujare
|
|
|
|
|
ArtiGujare wrote: Recently we shifted to VS2005. Hence the dll written in VC6 is no longer directly useful.
I don't understand that? Your old C++ code should be able to still do the following in a VS2005 C++ project.
ArtiGujare wrote: The dll should actually read the file and after the error checking send the a pointer of the memory to my application.
led mike
|
|
|
|
|
When I said we shifted to VS2005 I meant that the application using the dll was previosly written in VC6 and dll too was written in VC6. Now the application has to be written in VS2005 and still use the VC6 dll. My typical use case is:
1) Application send the file name to the dll.
2) dll reads the file at that mentioned filepath and does some file checks
3) if the file is in expected format, the dll returns the pointer pointing to the file data to the applictaion.
I hope it looks clear now.
|
|
|
|
|
I see no information in there that would keep you from accomplishing that using VS2005 C++ projects.
led mike
|
|
|
|
|
What about :
2) What would happen if my COM object memory is on a remote server?
3) Does the COM object copy the memory and send it to the requested application or does it just pass the reference.
|
|
|
|
|
For (3): You cannot pass a reference to memory across machines, that makes no sense at all. Therefore the memory is copied.
I have no idea why you are fixated on COM. Nothing in your requirments demands using COM. Without a requirement I would not choose to include the complexity and overhead associated with COM. In other words I would only use COM as a last resort.
led mike
|
|
|
|
|
Hi Led,
I tried adding the VC6dll in my VS2005App using "Add Reference". I could not add it. I got the message
"A reference to "<dllpath>" could not be added. Please make sure that the file is accesible, and that it is a valid assembly or COM component"
I googled around a bit with this message and I found that I cannot simply use the VC6dll in my VS2005App. Many links suggested that I might have to wrap the dll in a COM component in order to use it. Hence the COM usage. Otherwise if there is an alternative to bypass COM wrapping I would be more than happy to do the same.
Any suggestions?
Thanks and Regards,
Arti Gujare
|
|
|
|
|
Is the DLL already implementing a COM object? If so then it should work no problem.
I thought one of the ideas behind com was portable objects.
If it's not a com DLL then there's no "Add Reference" that will load the DLL. You need to link
to it (implicitely or explicitely using LoadLibrary() or similar). If it uses MFC you may have
problems. If it uses the CRT you may have problems as well since you'll have mixed versions
between the app and the DLL.
Mark
|
|
|
|
|
ArtiGujare wrote: I tried adding the VC6dll in my VS2005App using "Add Reference".
"Add Reference" is for adding .NET assemblies in a "Managed" Project. You are in the C++ forum indicating that your project is a "Native" project. Therefore you do not add a reference to the DLL. You link to it using a .Lib file just as before. Using a DLL from a C++ project is pretty basic stuff, why are you having problems with this? Perhaps if you give us more information about your level of experience we might provide more targeted information.
led mike
|
|
|
|
|
Hi!
Does anyone know why would an extension DLL not load when using the following code?
if ( AfxLoadLibrary( "MyDLL.dll" ) == NULL )
AfxMessageBox( "Error loading library." );
So, MyDLL.dll is an extension DLL. AfxLoadLibrary always returns NULL, even though the calling process and MyDLL.dll are in the same directory.
Any help will be greatly appreciated!
Thanks in advance!
|
|
|
|
|
What does your DllMain look like in the extension DLL? Is initialization failing there?
The app and the DLL are using the DLL version of MFC, correct?
Mark
|
|
|
|
|
This is how my DllMain looks like:
extern "C" int APIENTRY
DllMain(HINSTANCE hInstance, DWORD dwReason, LPVOID lpReserved)
{
UNREFERENCED_PARAMETER(lpReserved);
if (dwReason == DLL_PROCESS_ATTACH)
{
TRACE0("MYDLL.DLL Initializing!\n");
if (!AfxInitExtensionModule(MyDLL, hInstance))
return 0;
new CDynLinkLibrary(MyDLL);
}
else if (dwReason == DLL_PROCESS_DETACH)
{
TRACE0("MYDLL.DLL Terminating!\n");
AfxTermExtensionModule(MyDLL);
}
return 1;
}
I even put these lines of code right at the begining of DllMain:
CFile log;
log.Open( "log.001", CFile::modeCreate | CFile::modeWrite, NULL );
log.Write( "@", 1 );
log.Close( );
I ran the program using the new version of mydll.dll and NO log.001 was created.
So DllMain does not get executed.
|
|
|
|
|
You shouldn't need to write a log file. "MYDLL.DLL Initializing!" should show up in your debug
output window. You could put a breakpoint in there as well.
It's a mystery Have you tried David Crow's suggestion?
|
|
|
|
|
Problem solved!!!!!!!!!!
MyDLL.dll was using another dll which did not exist.
Thank you for your time!
|
|
|
|
|
Eikthrynir wrote: MyDLL.dll was using another dll which did not exist.
Cool 
|
|
|
|
|
Eikthrynir wrote: ...even though the calling process and MyDLL.dll are in the same directory.
Just for grins, try specifying an absolute path to mydll.dll.
Is your app multithreaded?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
