C / C++ / MFC

David Crow17-Jan-07 8:18

David Crow

17-Jan-07 8:18

If you remove the call to SetTimer(), does it behave normally?

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

suresh000917-Jan-07 8:25

17-Jan-07 8:25

Hi,

I am posting a wm_destroy immediately after creation.

Thanks for that.

It works fine now.

Regards,
suresh

CPallini17-Jan-07 8:21

CPallini

17-Jan-07 8:21

suresh0009 wrote:
The program dose a normal exit as there is no other code after settimer.

Noooooooooo, this is not true. MFC application keeps running but you have to return 0:

wind::OnCreate(LPCREATESTRUCT lpCreateStruct)
{
 SetTimer(test,1000,NULL);
 return 0;
}

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.

suresh000917-Jan-07 8:20

17-Jan-07 8:20

Hi,

If i place a messagebox after the settimer the application works as desired.

<br />
wind::OnCreate(LPCREATESTRUCT lpCreateStruct)<br />
{<br />
  SetTimer(test,10,NULL);	<br />
  AfxMessageBox("HI........timer is set",MB_OK,NULL);<br />
}<br />

here the messagebox is making sure that the program dosent exit.

can u give some suggestion.

thanks,
Ramachandra raju KK

suresh000917-Jan-07 8:28

17-Jan-07 8:28

i am posting a wm_destroy.

thanks for the support.
it works fine after i remove the destroy message.

regards,
suresh

CPallini17-Jan-07 8:15

CPallini

17-Jan-07 8:15

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.

suresh000917-Jan-07 8:26

17-Jan-07 8:26

Hi,

I am posting a wm_destroy immediately after creation.

thanks for the support.
timer workd as desired now.

regards,
suresh

Mark Salsbery17-Jan-07 8:42

Mark Salsbery

17-Jan-07 8:42

You can't receive a timer notification if you exit your application! Smile | :)

My own List Control in MFC doesn't respons conrrectly to the keyboard

#realJSOP17-Jan-07 11:36

#realJSOP

17-Jan-07 11:36

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

Chibi Maruko S17-Jan-07 7:04

Chibi Maruko S

17-Jan-07 7:04

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

VS2005 MFC app and XP themes [modified]

Ravi Bhavnani17-Jan-07 6:02

Ravi Bhavnani

17-Jan-07 6:02

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

This is your brain on Celcius
Home | Music | Articles | Freeware | Trips
ravib(at)ravib(dot)com

Re: VS2005 MFC app and XP themes

krmed17-Jan-07 9:48

krmed

17-Jan-07 9:48

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

Re: VS2005 MFC app and XP themes

Ravi Bhavnani17-Jan-07 9:53

Ravi Bhavnani

17-Jan-07 9:53

Yes, that's what I did (one for each of the debug/release builds).

Thanks,

/ravi

This is your brain on Celcius
Home | Music | Articles | Freeware | Trips
ravib(at)ravib(dot)com

Newbie - Memory sharing in COM

jayart17-Jan-07 5:44

17-Jan-07 5:44

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

led mike17-Jan-07 5:53

17-Jan-07 5:53

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

jayart17-Jan-07 6:00

17-Jan-07 6:00

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.

led mike17-Jan-07 6:23

17-Jan-07 6:23

I see no information in there that would keep you from accomplishing that using VS2005 C++ projects.

led mike

jayart17-Jan-07 6:43

17-Jan-07 6:43

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.

led mike17-Jan-07 6:57

17-Jan-07 6:57

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

jayart17-Jan-07 7:11

17-Jan-07 7:11

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

Mark Salsbery17-Jan-07 8:48

Mark Salsbery

17-Jan-07 8:48

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

led mike18-Jan-07 4:37