|
It seems as if you call SetDlgItemText() before the window/control is created.
AFAIK, the earliest time you can (programmaticly) set text to a window is in OnInitDialog().
|
|
|
|
|
hello
i cann't do it..
becoz when a call comes to my PC i have to show the caller id in it.
yes i'm feeling the same becoz when i trace it then i found that hWnd value is NULL.
plz tell me how to recify this error.
thanx
|
|
|
|
|
The simple solution would be to just do a null-check on the m_hWnd handle. If it is null, skip the set call. A more thorough solution might be to figure out why you are trying to set a window's text prior to creation to begin with. I've seen many people deal with communication-type code where they initialize the communications port (serial, ethernet, etc) in the application's InitInstance method and wonder why they have problems (a better solution in many cases is to do that initialization from the OnInitDialog/OnInitialUpdate method in the dialog or view class).
If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week
Zac
|
|
|
|
|
You can test ::IsWindow(m_hWnd) yourself. If ::IsWindow(m_hWnd) returns FALSE, then you can buffer the message(s). (Or write them to a file).
Then, in the OnInitDialog, you can update the window with the buffered messages.
But it seems a bit peculiar to me that the app exists and is running, but the window doesn't exist (yet) ... 
|
|
|
|
|
hello
yes this is exactly i'm not getting if appication is running but the window does not exist at all.and hwnd=NULL.
My Application is a Dialog Based Application.
i cannot do as u said becoz in my application when Any one will call to My PC then when i will set the Caller id.
plz help me how to reinitialize the hwnd.
byee
|
|
|
|
|
Have a look at the response from Zac Howland. It should give you the solution to your problem.
|
|
|
|
|
kakan wrote: AFAIK, the earliest time you can (programmaticly) set text to a window is in OnInitDialog().
Make sure the base implementation (of OnInitDialog()) has been called first. That's when the controls get created.
"The largest fire starts but with the smallest spark." - David Crow
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
yes i have defined the OnintDialog() Before the function calling.
in my case when a call come to my PC then my sipx tapi event generate & its call the handleoffring function which is defined by me in a dialog class and in this function i get the caller id.
now i want to display this id in the text box that "this number is calling".
thats it.
Plz tell me the solution
thanx
|
|
|
|
|
aavesh wrote: Plz tell me the solution
The solution is to simply not update a control that does not exist. Check the control's window handle and act accordingly.
"The largest fire starts but with the smallest spark." - David Crow
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
the control which is i'm updating do exist.
now how to reinitialize the m_hwnd which is NULL when getcallid function called.
byeee
thanx
|
|
|
|
|
aavesh wrote: the control which is i'm updating do exist.
Not according to this assertion:
ASSERT(::IsWindow(m_hWnd));
"The largest fire starts but with the smallest spark." - David Crow
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
this is exactly i want to know how to update the control according to this.
|
|
|
|
|
You must wait until the window exists before it can be updated. What part of that are you not understanding?
"The largest fire starts but with the smallest spark." - David Crow
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
hi
this is exactly i'm not getting becoz when my dialog is initialized and my button events are working nice.....after this when any call comes then m_hwnd variable value got NULL.
how this is happenning?
i don't think so this problem should take much time..
but i'm not getting proper solution plz help me.
thanx
|
|
|
|
|
aavesh wrote: ...after this when any call comes then m_hwnd variable value got NULL.
Where is this m_hwnd coming from? I would start there (to see why a NULL window handle is being sent to your code).
"The largest fire starts but with the smallest spark." - David Crow
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
i have used follwing code :-
void CTESTsipXtapiDlg::handleOffering(SIPX_CALL hCall)
{
SetWindowText(IDC_Realm,"Hello");
}
it does not show the text in the text box.
do u suggest6 me any other way..could u give me ur yahoo id so we chat directly.
thanx
|
|
|
|
|
aavesh wrote: SetWindowText(IDC_Realm,"Hello");
Is IDC_Realm a valid window handle (not a resource id)? Have you tried:
GetDlgItem(IDC_Realm)->SetWindowText("Hello");
"The largest fire starts but with the smallest spark." - David Crow
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Make IDC_STATIC_NEW_CALL as a control variable of type CStatic and then try SetWindowText on it .
Regards,
FarPointer
Blog:FARPOINTER
|
|
|
|
|
hello
if i use this then m_hwnd will reinitialize itself.
becoz always at the time of calling a function it gets NULL.
i'm trying now.
byeeee
|
|
|
|
|
Hello
This Code is not working.
when i use this code then it hangs my system.
plz help me.
thanx
|
|
|
|
|
Hi,
Is there any way to get the size of an allocated memory buffer knowing only the its address?
Thank you all 
|
|
|
|
|
|
No 
it doesn't worked for me !!!
The _msize function returns the size, in bytes, of the memory block allocated by a call to calloc, malloc, or realloc.
Thank you anyway
|
|
|
|
|
In case of objects allocated with new operator, the number of items seems to be stored in a word before the pointer:
MyClass * a = new MyClass[10];
__int32 size = *(((__int32*)a) - 1);
This works only when the class contains destructor.
The size does not seem to be stored in such manner for destructor-less objects and for fundamental types. But for this cases, _msize appears to return the size in bytes.
|
|
|
|
|
The short answer, is no. The long answer is that if you know something about the memory, you may be able to. For example, if it is a BSTR you can look 4 bytes before its "handled" address or use SysStringLen(...).
If you know that the memory came from a particular heap (or heap manager), you may be able to crack the heap structures used to maintain memory allocations. You also need to know where the memory came from in order to use functions like _msize(...), _msize_dbg(...), GlobalSize(...), etc.
Peace!
-=- James
If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
DeleteFXPFiles & CheckFavorites (Please rate this post!)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
