|
LVITEM tempdata;
TCHAR textBuf[1024] = { 0 }; // unless your strings may be longer...
// specify which item to copy:
tempdata.iItem = <index of="" item="">;
tempdata.iSubItem = 0;
// specify which data to copy:
tempdata.mask = LVIF_IMAGE | LVIF_INDENT | LVIF_PARAM | LVIF_STATE | LVIF_TEXT;
tempdata.stateMask = -1;
tempdata.pszText = textBuf;
tempdata.cchTextMax = 1023;
CopiedList->GetItem(&tempdata);
int insertIdx = m_SortedList.InsertItem(&tempdata); // idx where item was isnerted
// also, you would need to copy sub item text manually...
for(colIdx=1 to columns) {
CString text = CopiedList->GetItemText( <index of="" item="">, colIdx);
m_SortedList.SetItemText(insertIdx, colIdx, text);
}
--------------
completely different approach:
probably it's to late to change now, but I'd used two virtual list controls for this
Instead of feeding the list control, it asks you what to display when something is to be displayed.
(However, you would need to sort the stuff yourself)
Peter
|
|
|
|
|
Well, finally got it to work just copying every item through a loop. So I guess that'll have to do for now. Thanks for everyone's help. Now I just need to figure out how to render the listview based on the data given to it.. (Don't know if that's possible..) But that's for another thread... 
|
|
|
|
|
Well, I'm trying to send text to a child window. When I do FindWindow(WndClass, NULL); it doesn't like to find the chil window. I have no problem finding the main window... this is how i have it set up right now for getting the parent of the child window i want
CWnd *pMyWindow = FindWindow("AIM_IMessage", NULL);
pMyWindow->GetSafeHwnd();
if (pMyWindow == 0){
AfxMessageBox("Didnt Find IM window");
return;
}
if (pMyWindow != 0){
pMyWindow->SetWindowText("Some Text");
AfxMessageBox("Sent Text.");
return;
}
any suggestions?
|
|
|
|
|
You need to find the parent window, then use that window handle to find the child window. I would suggest something like this.
HWND hParent = FindWindow("AIM_IMessage", NULL);
if (hWnd != NULL) {
HWND hChild = FindWindowEx(hParent, NULL, "ChildWindowClassName", NULL);
if (hChild != NULL) {
::SetWindowText(hChild, "some text");
}
} else {
::MessageBox(NULL, "Could not find IM window", "Error", MB_ICONINFORMATION);
}
"Why kill time, when you can kill yourself?"
- Cabaret Voltaire
|
|
|
|
|
If destructors are called when an object goes outta scope, is the following legit:
CButton* pControls
pControls = new CButton[12];
pControls[0].Create(blah);
pControls[1].Create(blah);
pControls[n].Create(blah);
delete [] pControls;
when delete is called on the controls pointer do all the CWnd destructors get called automatically...???
Would I have to call the controls destroyWindow functions..??
Is the above acceptable or will it cause leaks...?
TIA!
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
The way I understand it, anything created with new should be deleted, the destructors in CWnd will be called. Then again, I never tried what your doing. Run the app through the debugger while the app creates these controls. Then exit the app, you will see any memory leaks in the output window if any.
|
|
|
|
|
Call me lazy, but thats why I'm asking...thats why I always ask.
Learn from other peoples mistakes kinda thing...
I ain't getting memory leak detection in output window.
I'm deleting the array...this is OK...but if any of those elements are created controls...i'm curious if I have to call the DestroyWindow().
If when the array is deleted it calls all the destructors then I have nothing to worry about. This is what I don't know. Theres no leaks in the output...so I would have to reply on other tools like stress and resource meter manually watch them go up and down plus i'm super anal and would need to do it and verify about 100 times before I trusted my readings...very time consuming...
So i'm hoping someone will know for sure.
Thanx!
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
Deleting the array will call the destructors on all the objects, but I have found that in the past sometimes calling delete on a window and not calling DestroyWindow first causes problems. Having said that, it must be in certain circumstances only, because DestroyWindow is not guarenteed to be called by the MFC framework on it's own windows.
Christian
The tragedy of cyberspace - that so much can travel so far, and yet mean so little.
|
|
|
|
|
Don't the CWnd destrcutors call destroywindow() automatically...??
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
Not according to MSDN, DestroyWindow destroys the window the CWnd encapsulates, but not the CWnd itself.
Christian
The tragedy of cyberspace - that so much can travel so far, and yet mean so little.
|
|
|
|
|
Christian Graus wrote:
Not according to MSDN, DestroyWindow destroys the window the CWnd encapsulates, but not the CWnd itself.
In his case, when his parent window is destroyed all the child windows are destroyed too. And he calls delete to delete the CWnd object in the destructor. So things should be okay.
Nish
My most recent CP article :-
A newbie's elementary guide to spawning processes
www.busterboy.org
|
|
|
|
|
|
HockeyDude wrote:
when delete is called on the controls pointer do all the CWnd destructors get called automatically...???
Yes they will be called but IMO before that you will have to remove the windows from screen.
From MSDN:
"In the MFC framework, when the user closes the frame window, the window’s defaultOnClose handler callsDestroyWindow."
HockeyDude wrote:
Would I have to call the controls destroyWindow functions..??
From MSDN:
"Do not use the C++ delete operator to destroy a frame window or view. Instead, call the CWnd member function DestroyWindow. Frame windows, therefore, should be allocated on the heap with operator new."
Atul
|
|
|
|
|
|
Yes Nish you are correct I was talking about CButton. 
I was positive that destructors were called with delete, but you and christian have helped me verify with myself.
Although what Christian said about DestroyWindow not being called kinda has me worried, i'd hate to have a bunch of HWND's lingering around after there CWnd is bye bye.
Ahh..to hell with it...i'm take the leakage if there is any...
Thanx !
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
|
All I needed to hear...
Thanx Nish!
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
Oops a daisy!...you are right...
Sorry...must have been daydreaming...
Atul
sleep...sleep...sleep...
|
|
|
|
|
I set my pointer to a window by doing
CWnd * Handle=FindWindow("AIM_IMessage",NULL);
and now i want to do a
SetWindowText("Some text") ;
or a
::SendMessage(HWND Hand...);
Only thing is, I don't know how to specify that I want my pointer to be where it sends the text... Or for that matter send it to a child window of the window that the pointer is pointing to...
Either way
Can anyone help me out?
|
|
|
|
|
Hi,
I'm not quite sure what you're asking, but if your CWnd * is valid (ie it's not NULL), then you can either do:
CWnd *pMyWindow = FindWindow("AIM_IMessage", NULL);
pMyWindow->SetWindowText("Some Text");
or
pMyWindow->SendMessage(params)
By the way, if you need a HWND for the window you've got a pointer to, just call:
pMyWindow->GetSafeHwnd();
------------------------
Derek Waters
derek@lj-oz.com
|
|
|
|
|
|
Hi, I have a dialog with a couple of textboxes on it, and I want to change
the font size on one of the terxtboxes. I can't seem to find out how. Any
input would be great. Thanks
|
|
|
|
|
Have you tried SetFont?
void CMyDialogClass::SetTheFonts()
{
m_fntBigFont.CreatePointFont(24, _T("Arial"));
m_fntLittleFont.CreatePointFont(6, _T("Arial"));
m_edtBigEditControl.SetFont(&m_fntBigFont);
m_edtLittleEditControl.SetFont(&m_fntLittleFont);
}
------------------------
Derek Waters
derek@lj-oz.com
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
