ATL / WTL / STL

How to Add String in MultiColumn ListBox

23-Feb-07 8:17

Sounds like you've changed compiler options somehow - do a Build->Rebuild - that should do it.

Pankaj.Jain22-Feb-07 0:04

Pankaj.Jain

22-Feb-07 0:04

Hi All
I m working on a ATL Project. I have to add string in a multi column List box using SendDlgItemMessage() but I dont get any idea about that.
I m using it like this

SendDlgItemMessage(IDC_LIST1, LB_INSERTSTRING, (WPARAM) 0, (LPARAM)"Hi");
SendDlgItemMessage(IDC_LIST1, LB_INSERTSTRING, (WPARAM) 1, (LPARAM)"All");

But it is not working. I want to Add "Hi" in one column and "All" other.
If u have any Idea Please suggest me

Thanks & Regards
Pankaj Jain

prasad_som22-Feb-07 1:04

22-Feb-07 1:04

PK Jain wrote:
But it is not working.

What is exact problem ?

PK Jain wrote:
I want to Add "Hi" in one column and "All" other.

WPARAM value refers to item index, not column index.

Prasad
Notifier using ATL | Operator new[],delete[][^]

Pankaj.Jain22-Feb-07 1:49

Pankaj.Jain

22-Feb-07 1:49

Thanks,
But my query is not solved
How to Add String in MultiColumn ListBox using SendDlgItemMessage

Pankaj Jain

prasad_som22-Feb-07 2:13

22-Feb-07 2:13

PK Jain wrote:
But my query is not solved

For that you need to answer questions asked. I asked, what do you mean by not working ?

PK Jain wrote:
How to Add String in MultiColumn ListBox using SendDlgItemMessage

Same as you written in in your original post.

I think you mistaken multicolumn with number of columns as in list box. In case of list box, multi column means, there will be no vertical scrolling as number of string keeps increasing.
Instead, string will be added to next column and so on, and horizontal scroll bar will appear.
I hope this clear your doubts.

Prasad
Notifier using ATL | Operator new[],delete[][^]

Re: How to Add String in MultiColumn ListBox [modified]

Pankaj.Jain22-Feb-07 18:45

Pankaj.Jain

22-Feb-07 18:45

Thanks Prasad,
Thanks to clear my doubts

Pankaj Jain

Stuart Dootson22-Feb-07 2:27

Re: CString::AllocSysString

22-Feb-07 2:27

A MultiColumn ListBox doesn't give that functionality - you want a ListView instead. To add text to a ListView in the way you want, use something like:

// Set up the columns
LVCOLUMN col = {0};
SendDlgItemMessage(IDC_LIST2, LVM_INSERTCOLUMN, 0, (LPARAM)&col);
col.iSubItem = 1;
SendDlgItemMessage(IDC_LIST2, LVM_INSERTCOLUMN, 1, (LPARAM)&col);

LVITEM item = {0};
item.mask = LVIF_TEXT;
item.iSubItem = 0;
item.pszText = "Hi";
int itemIndex = (int)SendDlgItemMessage(IDC_LIST2, LVM_INSERTITEM, 0, (LPARAM)&item);
item.iSubItem = 1;
item.pszText = "All";
SendDlgItemMessage(IDC_LIST2, LVM_SETITEMTEXT, itemIndex, (LPARAM)&item);

SendDlgItemMessage(IDC_LIST2, LVM_SETCOLUMNWIDTH, 0, LVSCW_AUTOSIZE);
SendDlgItemMessage(IDC_LIST2, LVM_SETCOLUMNWIDTH, 1, LVSCW_AUTOSIZE);

[Updated to correct code, add column sizing]

Last modified: 17mins after originally posted --

CString::AllocSysString

Q2A19-Feb-07 17:17

Q2A

19-Feb-07 17:17

Hi All,
I use AllocSysString like this
1) - CString myStr="ABCD";
int i=SomeFunction(myStr.AllocSysString());
Later in the code I free the memory as SysFreeString(_com_util::ConversStringToBSTR(myStr));
After using a memory profiling tool now, I don't get a mem. leak in this manner.
Is this the correct approach or should I use
2) - CString myStr="ABCD";
BSTR myStrBSTR=myStr.AllocSysString();
int i=SomeFunction(myStrBSTR);
and then use SysFreeString. While googling I found out the use of CComBSTR.
Can someone here tell me if I am using the right approach or should I use the second one, or use CComBSTR that manages allocation/deallocation by itself.

prasad_som19-Feb-07 18:29

19-Feb-07 18:29

Q2A wrote:
1) - CString myStr="ABCD";
int i=SomeFunction(myStr.AllocSysString());
Later in the code I free the memory as SysFreeString(_com_util::ConversStringToBSTR(myStr));
After using a memory profiling tool now, I don't get a mem. leak in this manner.

This approach will definitely cause memory leak, instead use CComBSTR.

CString str(_T("Some Value");
CComBSTR bsStr(str.AllocSysString());
int i=SomeFunction(bsStr);

or Use CComBSTR.

CComBSTR bsStr(_T("Some Value"));
int i=SomeFunction(bsStr);

Here, you dont need to worry about memory leak, CComBSTR will take care of those.

Prasad
Notifier using ATL | Operator new[],delete[][^]

CComBSTR Question

Like2Byte19-Feb-07 5:40

Like2Byte

19-Feb-07 5:40

Hello,

What's the difference between these?

CComBSTR a[256]; //note: square brackets
CComBSTR b(256); //note: parenthesis

Re: CComBSTR Question

prasad_som19-Feb-07 6:13

19-Feb-07 6:13

Like2Byte wrote:
CComBSTR a[256]; //note: square brackets

It is array of CComBSTR. 256 elements.

Like2Byte wrote:
CComBSTR b(256); //note: parenthesis

It is a single CComBSTR object, initialized to initial character size of 256.

Prasad
Notifier using ATL | Operator new[],delete[][^]

Re: CComBSTR Question

Like2Byte19-Feb-07 7:02

Like2Byte

19-Feb-07 7:02

Thanks, Prasad!

That makes things clearer for me. Smile | :)

Release vs. Debug in WTL

mirano19-Feb-07 5:13

mirano

19-Feb-07 5:13

Hi.
The application I coded is ATL/WTL windows app, now everything is fine in debug, when I compile it in release it compiles with no errors, however strings for label and other controls are cut off, it shows like only the first letter or nothing.
I get the strings from string table in the local resource, and it works fine in debug mode, I also checked the encoding and it is MBCS defined in both release and debug versions.
What can cause this behavior?

Thanks.

Sarajevo, Bosnia

prasad_som19-Feb-07 6:20

19-Feb-07 6:20

Check if you have missed any setting.
Have a look at difference betn debug and release[^] for possible cause. Though this article may not be very useful in this context, but may be you get some idea.

Prasad
Notifier using ATL | Operator new[],delete[][^]

mirano19-Feb-07 6:27

mirano

19-Feb-07 6:27

Thanks, but nothing to help me there, as it pertains mainly to MFC programming. I think I will have to go through Michael Dunn's article about string encodings, hope to find something useful there.

Thanks.

Sarajevo, Bosnia

Stuart Dootson19-Feb-07 20:36

19-Feb-07 20:36

It's likely that you've not initialised a variable - when I've had Release/Debug issues, that's what it's usually been.

I always make sure that I include Debug information in Release builds - that way I can use the debugger with Release builds reasonably meaningfully - as long as you keep optimisations turned on and you use the Release version of the C run-time, you've still got a Release build.

mirano19-Feb-07 21:06

mirano

19-Feb-07 21:06

Thanks, I'll give it a try. I am not sure about having debug info in the release build, but I will use it at least for the sake of finding out what the problem is.

Thank you.

Sarajevo, Bosnia

Stuart Dootson20-Feb-07 2:05