This is where std::stringstream (or wstringstream for unicode) comes in handy. Regarding splitting strings, std::string isn't particular good at this kind of manipulation. In general, regarding the windows api its useful to google their all caps typedefs and figure out what they really are. GetWindowText(m_window_handle, const_cast(title.c_str()), title.capacity()) Title.reserve(GetWindowTextLength(m_window_handle) + 1) Testing that out just a moment ago, this works: std::wstring title

Regarding when unicode is enabled on your build, you have to use a wstring or equivalent. Welcome any more 'correct' answers, though. Returns: *(begin() + pos) if pos (s.c_str()), len - 1) It would not be guaranteed if you did str.begin() or &*str.begin(), but for &s the standard defines operator as: Notice that the &s thing is always guaranteed to work by the C++11 standard, even in the 0-length string case. In practice, neither I nor Herb Sutter know of an implementation that does not use contiguous storage. I don't really know of one that is not hacky, but it can be done casting of the constness of c_string() from std::string.Ī std::string's allocation is not guaranteed to be contiguous under the C++98/03 standard, but C++11 forces it to be. To obtain the exact length of the text, use the WM_GETTEXT, LB_GETTEXT, or CB_GETLBTEXT messages, or the GetWindowText function.This answer may be of use to you in devising a solution. For more information on ANSI and ANSI functions, see Conventions for Function Prototypes. It can also occur when an application uses the ANSI version of GetWindowTextLength with a window whose window procedure is Unicode, or the Unicode version of GetWindowTextLength with a window whose window procedure is ANSI. This behavior can occur when an application uses both ANSI functions and common dialogs, which use Unicode. The return value, however, will always be at least as large as the actual length of the text you can thus always use it to guide buffer allocation. This occurs with certain mixtures of ANSI and Unicode, and is due to the system allowing for the possible existence of double-byte character set (DBCS) characters within the text. Under certain conditions, the GetWindowTextLength function may return a value that is larger than the actual length of the text. If the target window is owned by the current process, GetWindowTextLength causes a WM_GETTEXTLENGTH message to be sent to the specified window or control. To determine success or failure, clear the most recent error information by calling SetLastError with 0, then call GetLastError. This function does not clear the most recent error information.

Gizmo getwindowtext