When you click on an edit control, the message goes to the edit control window, not to the dialog window. You could derive a class from CEdit and use that class to subclass the edit controls. When your CEdit-derived class gets a WM_LBUTTONDOWN message, it could notify its parent by posting an app-specific message. Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

I don't know of a simple test, but you can use floor(), ceil() or fmod() to help. e.g. if (f == floor(f)) {} if (f == ceil(f)) {} float intPart; if (fmod(f,&intPart) == 0) {} I don't know what is most efficient if speed is important. Peter "Until the invention of the computer, the machine gun was the device that enabled humans to make the most mistakes in the smallest amount of time."

Move your window from the main frame, not the document. "Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

You may want to use Spy++ (it comes with Visual Studio) to see what messages are being passed to windows ;) Florin Crişan

DestroyWindow is the counterpart to Create and is about the windows-window, the thing you see on screen. delete is the counterpart of new and is about C++ classes and memory management. Let's think the unthinkable, let's do the undoable, let's prepare to grapple with the ineffable itself, and see if we may not eff it after all. Douglas Adams, "Dirk Gently's Holistic Detective Agency"

The problem with templates is that you can't have the definition in a .h and the implementation in .cpp Templates are like macros in that they are processed before the compilaton proper. There is a reason that I can't remember why that causes the problem... something to do with operating at the file scope rather than program scope There are a few ways around it, one is to write everything into the class defintion in the .h file. Contrary to popular belief this will not stop your code from working, but it is generally not good practice. There are some more elaborate workarounds out there if you look on Google... Hope this helps.

Hi, I did it within the stdafx.cpp, the #include MyDocument.h should be in stdafx to do this CMyDoc* pMyDoc; In your CMyView::OnInitialUpdate () just make extern CMyDoc* pMyDoc; pMyDoc = GetDocument (); ASSERT (pMyDoc); if it is made correctly, you have Doc access from every class using it. I.E. class CMyObject : public CObject { public: void MyMethode (); } void CMyObject::MyMethode () { extern CMyDoc* pMyDoc; any_local_variable = pMyDoc->a_document_variable; return; } Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you “The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson ;)

The scope of the variable pYY itself is limited to X::SomeFunction. However, given that the object that pYY is pointing to has been allocated on the heap that object continues to exist beyond X::SomeFunction. You could for instance return pYY from X::SomeFunction and use it at the caller site. -- gleat http://blogorama.nerdworks.in[^] --

Oliver123 wrote: I want to create my own WM_MESSAGE in my own code, assign an ID to it, and use Wizard to assign that ID to a particular function in a class. look at WM_APP and WM_USER in your local copy of MSDN or you could refer this article[^] by Mr Joseph M. Newcomer "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture cheers, Alok Gupta VC Forum Q&A :- I/IV Support CRY- Child Relief and You

I combined the header files and everything works. First I created class X with X.cpp and X.h Then created class Y with Y.cpp, but changed the default header file to X.h. So both class X and class Y had their headers in the same file. Forward reference worked. Both X and Y are created in Z. Z then passes pointers to X and Y by invoking a function of X and a function of Y. In X, a pointer to Y allows me to execute Y functions. In Y, a pointer to X allows me to execute X functions. The only peculiarity is when creating functions in Y. I right click Y in the class window in the workspace, then select ADD MEMBER FUNCTION. The new function is declared in class Y in file X.h, but the implememtation goes into X.cpp. Deleting the skeleton implementtion in X, and pasting it into Y.cpp solves the problem. Thanks for the help.

Oliver123 wrote: Is this a correct approach? No. Try: CTestDlg* aDlg = new CTestDlg(this); //code is in CSDITest1Doc Remember to create an appropriate CTestDlg constructor. "Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

I think yes some times ago I add some controls on the forum but then compiler shows a message that you cant insert controls to forum. WhiteSky

It has been a while, but essentially you just need to start a timer that calls a timer message handler of you choice. The timer handler keeps doing the increment until you release the button. When you release the button, then you need to release the timer. This is very similar as to how one selects lines in a text editor (or web page), that is a timer is used to make the window scroll when you mover the mouse cursor near the edge of the window when selecting text. INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra

Hello _AnShUmAn_ wrote: A variable may have a different value in the release and in the debug build, causing the differing behaviour Well , to add to it I say you most probably have a code optimization problem in the section of code which looks suspecious to you . You may find the values of variables in release by classical AfxMessageBox(value) displays . I have come across a situation where in release mode a string = "systarg" was represented in stack as "g|a|sys|t" which resulted in change of code flow . I did the following to solve it Try this add the following pramas around the section of code which looks problamatic #ifndef _DEBUG #pragma optimize("", off) #endif ..... your code which works fine in debug #ifndef _DEBUG #pragma optimize("", on) // désactivation de toutes les optimisations #endif redindian

Thanks. I inserted the \r\n into the string and it works fine. RawString.Format("%s %s %s**\r\n**%s %s %s", F1, F2, F3, F4, F5, F6); GetDlgItem(IDC_EDIT_RawBidAsk)->SetWindowText(RawString);

Here's a quick, general introduction to user-defined messages. I'm assuming you're using MFC here. 1. Define a message identifier. You can base it off of WM_USER or WM_APP: #define WM_MY_MESSAGE (WM_APP + 1) 2. Declare a message handler in your dialog class: afx_msg LRESULT OnMyMessage(WPARAM wParam,LPARAM lParam); 3. Add an entry to the message map for your dialog class: BEGIN_MESSAGE_MAP(...) // ... ON_MESSAGE(WM_MY_MESSAGE,OnMyMessage) // ... END_MESSAGE_MAP() 4. Define your message handler: LRESULT MyDialogClass::OnMyMessage(WPARAM wParam,LPARAM lParam) { // ... } 5. Finally, send the message when needed: my_dialog->SendMessage(WM_MY_MESSAGE, (WPARAM)first_parameter, (LPARAM)second_parameter); where first_parameter and second_parameter are whatever values you want to send with the message. Software Zen: delete this; Fold With Us![^]

Oliver123 wrote: I'm not sure what g_Spec().Xyz()really is. From its name it semms to be a global, and from its use I think it could be a global function, returning the reference to a singelton-instance of a class providing a function called Xyz, which takes a parameter that very well could be a LinkPtr. Oliver123 wrote: void WINAPI Abc(LinkPtr pData) { ((CNewDlg*)AfxGetApp()->m_pMainWnd)->Xyz(pData); <---I don't like this } Have you considered sending a user defined message? Failure is not an option - it's built right in.

Another important thing is: sometimes you'll need to call GetBuffer() or another function of that kind, if you do that, you must remember to call also ReleaseBuffer() just before exiting the scope of the CString variable. Hope this helps

How are you checking to see if you get the requested size? You could try checking the created font to see the attributes of the created font: CFont font; font.CreatePointFont(920, "Garamond"); LOGFONT logfont; font.GetLogFont(&logfont); Is that the way you've coded to create the font? If so, if "font" goes out of scope then the fonts handle (HFONT) is destroyed. Mark

I always try to define a variable like that only one time (outside the loop). It shouldn't make a difference unless it's a more complex type that has a lengthy constructor/destructor. I'm old, and set in my ways. "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