C / C++ / MFC Discussion Boards

First Prev Next

Re: Insert text to CRichEditCtrl/View

Carlos Antollini10-Aug-01 11:02

Carlos Antollini

10-Aug-01 11:02

You are a little confussed.

The getView is for get a view pointer from the RichEditDoc.
Please read how you can get a good view from a RichEdit Using the GetDlgItem function. I put an answer before.
After that you can get a pointer to the CRichEditCtrlCtrl

Regards!!! Smile | :)

Carlos Antollini.

Re: Insert text to CRichEditCtrl/View

10-Aug-01 11:06

In what class is this code?

Re: Insert text to CRichEditCtrl/View

11-Aug-01 2:03

It is in the MainFrame class of my SDI appliction, and all I want to do is to insert a line into the CRichEditView

Need help in SPI_SETDESKWALLPAPER!

10-Aug-01 1:48

does anybody know why it doesnt work?

CString str;
str = "c:\\test.bmp";
SystemParametersInfo(SPI_SETDESKWALLPAPER,0,str,SPIF_UPDATEINIFILE);

but the following works:

SystemParametersInfo(SPI_SETDESKWALLPAPER,0,"c:\\test.bmp",SPIF_UPDATEINIFILE);

pleaze help!!!!

Re: Need help in SPI_SETDESKWALLPAPER!

Tomasz Sowinski10-Aug-01 1:52

Tomasz Sowinski

10-Aug-01 1:52

What do you mean by "it doesn't work"? Does not compile?

Tomasz Sowinski -- http://www.shooltz.com

Re: Need help in SPI_SETDESKWALLPAPER!

10-Aug-01 2:14

I get this error:

error C2664: 'SystemParametersInfoA' : cannot convert parameter 3 from 'class CString' to 'void *'

Re: Need help in SPI_SETDESKWALLPAPER!

Tomasz Sowinski10-Aug-01 2:23

Tomasz Sowinski

10-Aug-01 2:23

1) Next time you post a question make clear that you have compiler error

2) The error message is self-describing. 3rd parameter to SystemParametersInfo is void *. You can't directly pass CString object as void *. You need to cast like this:

SystemParametersInfo(
  SPI_SETDESKWALLPAPER, 
  0, 
  (void *)(const char*)strWallpaperFile,
  TRUE);

Tomasz Sowinski -- http://www.shooltz.com

Re: Need help in SPI_SETDESKWALLPAPER!

10-Aug-01 2:39

thank you!!!!! I'm just a newbie in C++, thanks again!!!

proper use of ini-files

Sebastian Blatt10-Aug-01 0:30

Sebastian Blatt

10-Aug-01 0:30

Hi,

almost every one of my programs uses an ini-file.
I have written a class that scans the file at program start and stores all variables in a global dynamically allocated struct.

Because this takes some memory when the program gets larger, I was wondering if scanning the file for a particular entry when it is actually needed wouldn't be the better alternative.

What is the 'proper' way to use ini-files and why?

-Sebastian

Re: proper use of ini-files

Sebastian Blatt10-Aug-01 0:47

Sebastian Blatt

10-Aug-01 0:47

Hi,

I don't want to start a flame war here, but since I'm not using MFC and most of my programs don't have a big GUI, I find it too much a bother to write an options dialog, etc. everytime.

-Sebastian

Re: proper use of ini-files

Tomasz Sowinski10-Aug-01 0:46

Tomasz Sowinski

10-Aug-01 0:46

While the discussion on reading ini at startup versus on-demand would be interesting, I think you should ask yourself if it's worth the trouble. How much memory are you using for this global struct?

Tomasz Sowinski -- http://www.shooltz.com

Re: proper use of ini-files

Sebastian Blatt10-Aug-01 0:54

Sebastian Blatt

10-Aug-01 0:54

Hi,

its not very much for a smaller program, but I was wondering if I should really store every minor option like background colors, switches for controls or windows the whole time the program is running.

Thanks for your time.
-Sebastian

Re: proper use of ini-files

Tomasz Sowinski10-Aug-01 0:58

Tomasz Sowinski

10-Aug-01 0:58

Assume that it's biggest program you're ever going to write. Multiply the struct size by 4. How much memory are you going to allocate?

Tomasz Sowinski -- http://www.shooltz.com

Re: proper use of ini-files

Sebastian Blatt10-Aug-01 1:02

Sebastian Blatt

10-Aug-01 1:02

OK, you're right, it won't use up all my RAM. But is it really good programming practice to have all these unused variables lying around all the time?

-Sebastian

Re: proper use of ini-files

Tomasz Sowinski10-Aug-01 1:05

Tomasz Sowinski

10-Aug-01 1:05

Good programming practice is to spend your development time on issues that really matter. I don't believe that loading ini settings at startup can hurt you or your performance. If it works for you, leave it, unless you have nothing else to do (in this case, it's better idea to go for some beer).

Tomasz Sowinski -- http://www.shooltz.com

Re: proper use of ini-files

#realJSOP10-Aug-01 3:09

#realJSOP

10-Aug-01 3:09

It's simply a matter of what is prudent within the context of the program's architecture. I think almost all of my programs do it that way (loading the ini data into a struct or object).

There is no "proper" way to do it really beyond obeying the laws of C++ physics. Smile | :)

Re: proper use of ini-files

Ray Kinsella10-Aug-01 3:25

Ray Kinsella

10-Aug-01 3:25

I though ini files where long since dead ...
I put everything in the registry these days....

Regards

Ray

"Je Suis Mort De Rire"

Re: proper use of ini-files

Tomasz Sowinski10-Aug-01 3:27

Tomasz Sowinski

10-Aug-01 3:27

Ray,

You've just started a flamewar...

Cheers,

Tomasz Sowinski -- http://www.shooltz.com

Re: proper use of ini-files

#realJSOP10-Aug-01 6:30

#realJSOP

10-Aug-01 6:30

Oh sure, make me out to be the bad guy...

YOU BASTARD! Smile | :)

I KEEL YOU! I KEEL YOU ALL!!!!

Laugh | :laugh:

Re: proper use of ini-files

#realJSOP10-Aug-01 6:28

#realJSOP

10-Aug-01 6:28

I don't use the registry unless it makes sense to do so. The more data tha's contained in the registry, the longer it takes Windows to load. COM forces registry use, so if a program uses COM, there's no reason not to contribute to the registry bloat, but for simple programs, why bother?

INI files are alive and well - long live INI files.

Smile | :)

CToolbar

10-Aug-01 0:14

I have a CToolBar member in my MDI app, it's a docking enabled toobar. If I float it, the user can click the little "x" button and close it. what actually happens to the toolbar in this case? how can I redisplay it later?

And is there a way I can handle the message generated from clicking that "x" button, without having to derive a class from CToolBar? or is that the only way?

Thanks

Re: CToolbar

Tomasz Sowinski10-Aug-01 0:29

Tomasz Sowinski

10-Aug-01 0:29

what actually happens to the toolbar in this case?

It's only hidden, window is not destroyed.

how can I redisplay it later?

Use CFrameWnd::ShowControlBar.

And is there a way I can handle the message generated from clicking that "x" button, without having to derive a class from CToolBar?

Not exactly. Actually, you'll have to subclass the CMiniFrameWnd window that hosts floating toolbar.

Tomasz Sowinski -- http://www.shooltz.com

How to simulate ALT + SHIFT keys press with code ?

9-Aug-01 23:22

Hi,

I need to simulate the pressing of ALF+SHIFT keys through code...
Any idea to solve this problem?

Thanks!

Re: How to simulate ALT + SHIFT keys press with code ?

Tomasz Sowinski10-Aug-01 0:49

Tomasz Sowinski

10-Aug-01 0:49

Use keybd_event (on all 32-bit Windows versions) or SendInput (on Win98/ME/2000/XP/NT4SP3)

Tomasz Sowinski -- http://www.shooltz.com

ATL hell - import object to MFC project part II

Christian Graus9-Aug-01 20:56

Christian Graus

9-Aug-01 20:56

I'm hoping someone will be able to answer this question with the extra info I have at hand.

I have put my code in a try catch block like this:

try
{
	IFindFilesPtr pIFind(__uuidof(FindFiles));
	pIFind.CreateInstance(CLSID_FindFiles);
	if (pIFind == NULL) return;
//snip
}
catch(const _com_error & err)
{
	CString strError(err.ErrorMessage());
	AfxMessageBox(strError);
	return;
}

And it crashes, telling me the class is not registered. The ATL based project that uses this class can find and use the class, the object is registered. Could anyone suggest what I need to do so that my MFC dialog based project can find my COM object ? I am initialising COM and uninitialising it in InitINstance and ExitInstance respectively.

Thanks.

Christian

Secrets of a happy marriage #27:

Never go to bed if you are mad at each other. It's more fun to stay up and fight.

Last Visit: 31-Dec-99 18:00 Last Update: 28-May-24 7:52

Refresh

ᐊ Prev 1...18096 18097 18098 180991810018101 18102 18103 18104 18105 Next ᐅ

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