I use the short format of the DateTime Control. So, I want only 2 digits for the year. But if I place the cursor in the year, it becomes 4 digits. Is there a possibility to avoid this? To recreate the OnDraw/OnKey logics is not so rational :sigh:

Yourwelcome. :) > The problem with computers is that they do what you tell them to do and not what you want them to do. < > If it doesn't matter, it's antimatter.<

Thanks for your answer :) I resolve it with multiple threads, like your idea ;) Greetings

use getchar() on windows CE. http://msdn.microsoft.com/en-us/library/ms859646.aspx[^] -PaulH

In fact, your rectangle is empty: CRect constructor accepts, as parameters, rectangle's {left,top, right, bottom}. See CRect constructor at MSDN. :) 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. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke [My articles]

I'm not sure i completely understand but why don't you just let OnPaint do it's job and afterwards draw your border? E.g. like this: CMyGreatEdit::OnPaint() { __super::OnPaint(); //Let the base do the complete drawing of the control CDC *dc = GetDC(); //draw your border wherever you need to using the dc... ReleaseDC(dc); } > The problem with computers is that they do what you tell them to do and not what you want them to do. < > Computers are evil, EVIL i tell you!! <

Try to see what GetLastError returns immediately after the call to __access, it might tell you something. There's a tool in Visual Studio that will give you the error text for each error id. There is sufficient light for those who desire to see, and there is sufficient darkness for those of a contrary disposition. Blaise Pascal

Maybe, you could create the childs invisible (~WS_VISIBLE) and then call ShowWindow(..) for them ? :) virtual void BeHappy() = 0;

I think he meant which code calls the heap allocator? Try IBM Rational Purify. They have 30-day license I believe. It should keep track of allocations and deallocations, leaks, etc, complete with the stack of the callers.

thanks for your answer. I'll try to find another workaround to fix this "problem" if i can't find a solution, i drop it :-D

Knowing how frames work for normal windows, I suspect you want to look for WM_NCLBUTTONDBLCLK, i.e. the non-client area equivalent of WM_LBUTTONDBLCLK Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

It is a user setting. In the control panel, under mouse properties, pointer options tab, there is an option to hide the mouse pointer while typing. You may be right I may be crazy -- Billy Joel -- Within you lies the power for good - Use it!

Yes, it's a last possibility to "resolve" it, but if the user holds down the Mouse-Key (for example to continue the sizing) it seems pretty ugly :doh: But thanks for your answer :)

I'm not sure if this will improve the speed, but what I'm saying is that, instead of placing the 100 odd controls in the form view directly, place them in a new dialog and then place this dialog in the form view as a child dialog. The child dialog will need its border set to none. «_Superman_»

Hi baerten, I agree with Luc. However you may be able to use a pre-defined macro[^] something like below:VOID FunctionB(int iVal,char *caller,int line) { char szBuf[MAX_PATH]; sprintf(szBuf,"I was called by %s on line %d",caller,line); MessageBoxA(NULL,szBuf,0,0); } VOID FunctionA() { FunctionB(1,__FUNCTION__,__LINE__); } baerten wrote: i can't write over 100 Debug-Lines into the code A stack trace is several times more expensive at runtime. Best Wishes, -David Delaune

Yes it should, since each request fires will not wait the previous one to complete, so multi of them will end up in the same time for example, in the addetion, there are two ways now to use asyncrounous calls with sockets now, the old one Begin/End aspect... and the new one which is introduced in .NET Framework 3.5, which is supposed to be faster and holds better performance ideas as well. Sincerely Samer Abu Rabie Note: Please remember to rate this post to help others whom reading it.

Okay, i see ... If the working view gets the focus, i show up the modeless dialog. Because if i don't do it, the user couldn't see to which view has a "waiting dialog" Thanks for the idea :)