C / C++ / MFC Discussion Boards

Ryan B.27-Jun-02 5:36

27-Jun-02 5:36

Thank you so much..
(i had tried to use the a2ole macro before, but could noit find information on which library it was in, or how to implement it..

THANK YOU ....

Ryan Baillargeon
Software Specialist
Fuel Cell Technologies Inc.

Re: Simple String Conversion

Le centriste27-Jun-02 7:36

Le centriste

27-Jun-02 7:36

You're welcomed. Btw, where do u live in Canada? Me, I live and work in Hull, near Ottawa.

Michel

It is a lovely language, but it takes a very long time to say anything in it, because we do not say anything in it, unless it is worth taking a very long time to say, and to listen to.

- TreeBeard

How do I find the task bar color

Rama Krishna Vavilala27-Jun-02 4:42

Rama Krishna Vavilala

27-Jun-02 4:42

Any XP theme gurus please help me to know how to find the task bar color in the current theme? I don't even know where to look at Cry | :((

I have never wasted time worrying about such insignificant things. Keep your eye upon the donut and NOT upon the hole. - Bill Sergio about posting in the right forum. The Lounge - June 23, 2002

Re: How do I find the task bar color

Scott H. Settlemier27-Jun-02 7:43

Scott H. Settlemier

27-Jun-02 7:43

Checkout the SystemParametersInfo and the GetSysColor
functions. They control how windows ui stuff works and looks.

Self Termination

27-Jun-02 4:34

Is there a way to self terminate an application after a period of time.

Thanks

Re: Self Termination

27-Jun-02 4:53

Do a PostMessage with WM_CLOSE - PostMessage(WM_CLOSE, 0 , 0)

Re: Self Termination

Rage27-Jun-02 5:00

Rage

27-Jun-02 5:00

use a CTimer for the "period of time" and then ... exit(0); Big Grin | :-D

~RaGE();

Re: Self Termination

_Magnus_27-Jun-02 5:04

_Magnus_

27-Jun-02 5:04

main()
{
Sleep(TIME);
exit(0);
}

Smile | :)

/Magnus

Re: Self Termination

Roger Allen27-Jun-02 6:22

Roger Allen

27-Jun-02 6:22

Now that is what I call a usefull program! Wink | ;)

Roger Allen
Sonork 100.10016

If I had a quote, it would be a very good one.

Re: Self Termination

Scott H. Settlemier27-Jun-02 7:59

Scott H. Settlemier

27-Jun-02 7:59

Sure. Zillions. Smile | :)

Here's a frighteningly unfriendly way; it hangs a sword of Damocles over
the process:

~~~~~

// the basic killer thread
DWORD WINAPI _MySleeper(LPVOID msWaitPeriod)
{
Sleep((DWORD)msWaitPeriod);
TerminateProcess(GetCurrentProcess(),0);
return 0;
}

// hang the sword
DWORD ThreadId;
DWORD ms=10*1000; // 10 seconds
CloseHandle(CreateThread(0,0,_MySleeper,(LPVOID)ms,0,&ThreadId));

~~~~~

Now that process has 10 seconds to live.
It'll suffer a brutal death, probably leaving leaving lots of
open resources improperly closed. Dead | X|

Better to just set a flag, and post a quit message during idle
or something.

Intellisense in VS.NET

Steve Thresher27-Jun-02 4:30

Steve Thresher

27-Jun-02 4:30

I am having a problem getting intellisense to work with the header files for my libraries. I thought that all you needed to do was add an include path for the location of my header files and away you go but that doesn't seem to be the case. All intellisense will recognise are macros to the standard functions such as fxd_mem_copy() which macros to memcpy(). Nothing at all is offered for my own functions eg fxd_mem_format(). I use makefile solutions to build my programs with the source files attached to the project so they are easily editable in VS.NET. Can anybody provide suggestions as to what the problem is?

Thanks for any help you can provide

Steve.

Systems AXIS Ltd - Software for Business ...

Re: Intellisense in VS.NET

Mike Nordell28-Jun-02 9:20

Mike Nordell

28-Jun-02 9:20

S^teve T^{hresher wrote:}I am having a problem getting intellisense to work with the header files for my libraries.

Many have. Head over to nntp://microsoft.public.dotnet.languages.vc. Maybe even better, check that NG from a Google Groups search.

++luck;

serializing issue

27-Jun-02 4:01

hi,
I have two classes.
CData
CHelper.

CData has an array (CArray) of CHelper.
CHelper has a pointer to CData so that nesting is possible.

Now,how to serialize CData so that even the nested things,any number and however deep it may be ,will also be serialized and importantly,retrieved.

Does inheriting CData from CObject help or should I bear the headache of the job?

PS:I am in the middle of a project and dont have much time to experiment all by myself.

Waiting..... OMG | :OMG:

Re: serializing issue

Joaquín M López Muñoz27-Jun-02 4:12

Joaquín M López Muñoz

27-Jun-02 4:12

During the output process, keep an array (using for instance std::vector) of pointers to the CDatas serialized so far. When it comes to output a CData, first check whether it's been already serialized (do a linear search on the vector), and if so write some check variable to 1 informing about this circumstance, followed by the index of the object in the vector. If the object hasn't been serialized yet, write 0 as the check variable and proceed with serialization.
On the input stage, do the opposite, constructing the vector on the fly as well.
This scheme has some weak points, like the linearity of the search for serialized objects, but this could be remedied if the need arises.

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

Re: serializing issue

27-Jun-02 4:16

yah,thought on similar lines but isnt tehre any built in methods to accomplish this?

Re: serializing issue

Joaquín M López Muñoz27-Jun-02 4:20

Joaquín M López Muñoz

27-Jun-02 4:20

There are serialization frameworks that do that automatically, but they are rather intrusive (esentially they require that you replace all your pointers with their own smart pointers that take care of the looping references), so I don't think it'd be a good idea to try to use them if you're in the middle of a project. The solution proposed is local (all the code is inside a function) and it is not that hard to implement.

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

Re: serializing issue

jbarton27-Jun-02 5:27

jbarton

27-Jun-02 5:27

Yes, if you use the serialization support provided in MFC, it will properly handle nested and even cross-linked objects. You need to use CObject as the base class, and add the appropriate DECLARE_SERIAL and IMPLEMENT_SERIAL macros. You also need a Serialize routine for each class.

Best regards,
John

Re: serializing issue

Joaquín M López Muñoz27-Jun-02 6:15

Joaquín M López Muñoz

27-Jun-02 6:15

I don't think MFC automatically supports serialization of linked objects. Basically it provides the barebones framework, all the work is left to the programmer. Please correct me if I'm wrong.

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

Re: serializing issue

jbarton27-Jun-02 7:10

jbarton

27-Jun-02 7:10

MFC has complete support for serialization of linked items. I have used it for years with no problems. Internally it keeps track of which objects have already been serialized by using a map.

As long as you setup your macros correctly (DECLARE_SERIAL / IMPLEMENT_SERIAL), it handles all the details of loading and saving complicated data structures which are interlinked, even with loops of objects.

Best regards,
John

Re: serializing issue

Joaquín M López Muñoz27-Jun-02 8:59

Joaquín M López Muñoz

27-Jun-02 8:59

Oh... You were right, I've read some stuff on the subject and the mechanism actually does what you say (and in a pretty clever way.) I used to think ;FC serialization was dumber than it is.
Regards,

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

Re: serializing issue

Mike Ellertson3-Aug-03 19:35

Mike Ellertson

3-Aug-03 19:35

jbarton,

You seem to have used MFC serialization for a while. Maybe you can help me out with this. I have a class derived from CArray, with not other variables in the class. I'm trying to serialize it to a TXT file. Here's my class definition:

class AFX_EXT_CLASS CFormList : public CArray<CString,CString&> <br />
{<br />
	DECLARE_SERIAL(CFormList);<br />
public:<br />
	CForm Item(CARSConnection &arsConnection, int iIndex); // this array is zero indexed<br />
	void GetForms(CARSConnection &arsConnection, long lType);<br />
	CFormList();<br />
	virtual ~CFormList();<br />
};<br />

And then my implementation code:

IMPLEMENT_SERIAL(CFormList, CArray, 1);

When I compile it, it's giving me this error:

error C2955: 'CArray' : use of class template requires template argument list

Any idea what I'm doing wrong? Confused | :confused:

Thanks much for any help

Mike Ellertson

Re: serializing issue

jbarton4-Aug-03 2:35

jbarton

4-Aug-03 2:35

Hi Mike,

You shouldn't derive from a CArray - it is not designed to be a base class (it does not have a virtual destructor).

Instead, you can make the CArray into a member of your CFormList class

<br />
class AFX_EXT_CLASS CFormList : public CObject<br />
   {<br />
   DECLARE_SERIAL(CFormList);<br />
<br />
   public:<br />
      void Serialize( CArchive& ar )<br />
         {<br />
         CObject::Serialize( ar );<br />
         m_Array.Serialize( ar );<br />
         }<br />
<br />
   private:<br />
      CArray<CString,CString&> m_Array;<br />
   };<br />
<br />
IMPLEMENT_SERIAL( CFormList, CObject, 1 );<br />

Best regards,
John

Re: serializing issue

Mikey_E5-Aug-03 7:08

Mikey_E

5-Aug-03 7:08

Thanks for the input on this. I did just go ahead and derive from CStringList instead. Just for your info, I read an article on MSDN describing the right way to derive from CArray. So it is meant to be derived from.

I'm pretty sure the issue I was having was due to a bug in the way the Visuall C++ preprocessor interprets comma's in macro's. Another codeproject member let me know that and I found a bug report on Microsoft Website. But your solution worked, so I'm off and running.

Thanks!

Mike Ellertson

Re: serializing issue

jbarton5-Aug-03 7:36

jbarton

5-Aug-03 7:36

Hi Mike,

One thing that you should be aware of when serializing CArray (or other MFC collection classes):

Normally, when you need to serialize a CArray of some type, you have to check if the type is a POD. The default serialization support in CArray will do a binary copy of the contents of the CArray to the archive. This works for simple data types, but not for class objects. The correct way to fix this is to override the SerializeElements() function for the specific class that you are serializing. You didn't need to do this for a CArray containing CString objects, because Microsoft already provides an override for SerializeElements specifically for CString. If you change what is in the array to some more complicated object (rather than just a CString), you will need to override the SerializeElements() routine for this object.

Best regards,
John

Re: serializing issue

Joaquín M López Muñoz27-Jun-02 9:02

Joaquín M López Muñoz

27-Jun-02 9:02

John's answer is the way to go (I guess you already were using MFC serialization, so this is very good news to you.) The DDJ's article Inside MFC Serialization I've just read could be of some help for you (it was for me.)

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

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.