C / C++ / MFC

#ifdef _UNICODE
    CString strText = (This piece of code returns a CStringA from the back-end of my program)

    if (strText.GetLength() <= 0)
       return false;

    char *convertThis = new char(strText.GetLength());
    sprintf(convertThis, "%s", strText);
    int nLen = lstrlenA(convertThis);
    BSTR unicodeStr = SysAllocStringLen(NULL, nLen);
    MultiByteToWideChar(CP_ACP, 0, convertThis, nLen, unicodeStr, nLen);
    m_EditControl.SetWindowText(unicodeStr);
    SysFreeString(unicodeStr);
    delete convertThis;
#else

CStringA strText = (CStringA)function();
CString strTextGeneric(strText);    
m_EditControl.SetWindowText(strTextGeneric);

KellyR wrote:

I need the BSTR because MultiByteToWideChar will not compile if I define the type as wchar_t, and SetWindowText would require a conversion if I defined the type as LPWSTR

Mark Salsbery
Microsoft MVP - Visual C++

Mark Salsbery wrote:

Using a generic string type, implemented as a template no less, on a back end that could be used
by a front end with a different type....bummer. I don't know what to say about that

Mark Salsbery wrote:

Regardless, I suppose using the square brackets and leaving room for null terminators should
help a lot.

KellyR wrote:

It's horrible.

Mark Salsbery
Microsoft MVP - Visual C++

KellyR wrote:

Now I'm working on an MFC app (using VC++ .NET 2005) and it seems to crash when I try to free the memory

char *a = new char[100];
a = a + 1;
// or
a = "Hello";
delete [] a; // will crash

char *a = new char(100);

char *a = new char[100];

--Mike--
Visual C++ MVP
LINKS~! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

"That's what's great about doing user interface work. No matter what you do, people will say that what you did was idiotic." -- Raymond Chen

Rhymhoont wrote:

pDlg->icmp.SetDoLookup(false);
pDlg->icmp.SetMaxTimeOuts(1);
pDlg->icmp.Ping( "10.0.2.60" , 1500, 32, 2);

/* static */ UINT PingAddress( LPVOID pParam )
{
    CBinDlg *pDlg = (CBinDlg *) pParam;
    return pDlg->PingAddress();
}
 
UINT CBinDlg::PingAddress( void )
{
    PostMessage(some_user_defined_message); // map this to the function below
    return 0;
}
 
LRESULT CBinDlg::OnPostedMessage( WPARAM, LPARAM )
{
    icmp.SetDoLookup(false);
    icmp.SetMaxTimeOuts(1);
    icmp.Ping("10.0.2.60" , 1500, 32, 2);
 
    return 0;
}

/* static */ UINT PingAddress( LPVOID pParam )
{
    CBinDlg *pDlg = (CBinDlg *) pParam;
    pDlg->PostMessage(some_user_defined_message); // map this to the function below
}
  
void CBinDlg::OnPostedMessage( WPARAM, LPARAM )
{
    icmp.SetDoLookup(false);
    icmp.SetMaxTimeOuts(1);
    icmp.Ping("10.0.2.60" , 1500, 32, 2);

Wxffles wrote:

There appears to be two possible sorts of behaviour for selecting an item in a drop down combobox list:
2: Click and hold to get the list to drop down, move to selection, release to select it.

Wxffles wrote:

There appears to be two possible sorts of behaviour for selecting an item in a drop down combobox list:

The Extended User Interface

Drop-down combo boxes and drop-down list boxes support an alternative keyboard interface called the extended user interface. By default, the F4 key opens or closes the list, and the DOWN ARROW changes the current selection. In a combo box with the extended user interface, however, the F4 key is disabled and pressing the DOWN ARROW key opens the drop-down list. In addition, the mouse wheel, which normally scrolls through the items in the list, does not have any function when the extended UI is set.

To select the user interface for a combo box, an application can send the CB_SETEXTENDEDUI message to the combo box. A TRUE value for the wParam parameter enables the extended user interface; a FALSE value sets the default user interface. To determine whether a combo box uses the extended user interface, an application can send the CB_GETEXTENDEDUI message to the combo box.