C++ string in a windows function

Hi.
For example:

If I use GetWindowText, I use it as follows:

Code:

---

char WindowCaption [ 1024 ];

GetWindowText ( Window, WindowCaption, 1024 );

---

Easy, but let's say I want to do something with the string, to easly work with it, I put it in a C++ string, I prefer to work with C++ strings.

Code:

---

std :: string Caption = WindowCaption;

---

Done, only the thing is I need to use two strings.
I am able to directly use a C++ string in the following code:

Code:

---

MessageBox ( Window, "Message Box Text", Caption.c_str(), MB_OK );

---

As you can see I used the c_str() function, but when I try the following, the c_str() function wont help:

Code:

---

std :: string WindowCaption;

GetWindowText ( Window, WindowCaption.c_str(), 1024 );

---

It will give me a compile error so I tried a lot of things but they all didn't work.
I actually have this problem quite long but I never bothered about it, I always just used two strings.
Only now I really would like to only use one C++ string with GetWindowText, can someone help me how to that?

Thank you, Yuri.

I find your signature highly offensive. You may want to change it.

What do you mean? What has that to do with my problem?

Look pal, I'm not even going to go down to your level and explain to you what you know already.

Your signature is highly offensive. And I'm sure you wouldn't like to see the same bold and neon red text on my signature, but this time talking about netherlands.

Could you stop complaining about my signature, there is nothing wrong with it, you just hate dutch people, really, what is your problem against me?

You cannot pass the string to that function to be filled since string doesn't provide access to modify its internal character data, the c_str() function allows only read access.

There are different ways to handle the issue. The simplest one is to call GetWindowText as you did with the char WindowCaption[1024] variable, then assign WindowCaption to your string after the call.

Another one is to use vector<char> WindowCaption(1024), then pass &WindowCaption[0] to the function and assign WindowCaption to your string afterwards. If you know that you will be using 1024, then this is probably overkill, but if the size is dynamic then the vector is a better solution.

tsk... children.

'It doesn't provide acces to modify it's internal character data', ok, but why it doesn't?
To fill a C++ string you are able to use std :: cin >> String; and getline ( cin, String );, in a console application though.

tsk... discriminating elderly people.

Those functions are part of the string interface. GetWindowText is not. Those functions are either friends, or they use the same technique that you must use.

It doesn't provide that access because the original string class designors and/or the standards committee decided it was too unsafe. Part of the point of the string class is to provide safer string funcionality than C style strings, but provide a pointer to internal data makes buffer overruns and other safety issue much more likely. Also, not providing such a pointer might make it easier for library designers to use tricks to optimize the string class.

The best idea is to wrap GetWindowText in a function that first calls GetWindowTextLength (I think it's called), allocates a std::vector of appropriate size, calls GetWindowText to read the text into that buffer and then returns a string that is a copy of the contents of the vector:

Code:

---

template<typename Ch> void getWindowText(HWND hwnd, Ch *buffer, std::size_t len);
template<> void getWindowText<char>(HWND hwnd, char *buffer, std::size_t len)
{
  return ::GetWindowTextA(hwnd, buffer, len);
}
template<> void getWindowText<wchar_t>(HWND hwnd, wchar_t *buffer, std::size_t len)
{
  return ::GetWindowTextW(hwnd, buffer, len);
}

template<typename Ch> std::basic_string<Ch> getWindowText(HWND hwnd)
{
  std::size_t len = ::GetWindowTextLength(hwnd);
  std::vector<Ch> buffer(len);
  getWindowText(hwnd, buffer, len);
  return std::basic_string<Ch>(buffer.begin(), buffer.end());
}

---

Syntax errors possible.