Priority support forum (read-only if you do not have a valid tech support subscription)

Hi!

WHERE IS THE SUPPORT????

Have you found a solution in the meantime?

I’m still waiting for an answer/solution.

!!!!    IT’S REALLY URGENT !!!!!

I read in the forum that other people have the same problem.

So whats up?

> Dear Michael,

> >>

> >> You asked an interesting question. We modified the following part of the

> >> CExtMenuControlBar::TranslateMainFrameMessage() method:

> >>

> >>         if(        (    bAlt

> >>                 ||    (    m_bFlatTracking

> >>                     &&    vkTCHAR != VK_LEFT

> >>                     &&    vkTCHAR != VK_RIGHT

> >>                     &&    vkTCHAR != VK_UP

> >>                     &&    vkTCHAR != VK_DOWN

> >>                     &&    vkTCHAR != VK_F4

> >>                     &&    vkTCHAR != VK_RETURN

> >>                     &&    vkTCHAR != VK_SPACE

> >>                     &&    vkTCHAR != VK_ESCAPE

> >>                     &&    vkTCHAR != VK_TAB

> >>                     )

> >>                 )

> >>             &&    (!bDockSiteCustomizeMode)

> >>             )

> >>         { // if VK_ALT + VK_... pressed

> >> //            if( g_bCancelNearestAltUp ) // (+ v.2.23)

> >> //                return FALSE;

> >>             if( bKeyUp )

> >>             {

> >> //                return TRUE; // COMMENTED

> >>                 return FALSE; // ADDED

> >>             }

> >>

> >> And we set breakpoints on all the return TRUE; code lines in this method.

> >> There were no return TRUE; code lines invoked after typing ALT+0160 after

> >> this modification. But WM_CHAR messages are still not received, though the

> >> CExtMenuControlBar::TranslateMainFrameMessage() is no longer filters

> >> keyboard events during ALT+0160 input.

> >>

> >> It looks like GetKeyboardState() and/or GetKeyboardLayout() API

> >>

> invocations

>

> >> are breaking ALT+0160 input. But we cannot avoid the usage of these APIs.

> >> So, we continue our experiments by modifying the

> >> CExtMenuControlBar::TranslateMainFrameMessage() method for correct

> >>

> ALT+0160

>

> >> input.

> >>

> >>

Hi,

>>

>> I’ve got a problem to handle an ALT+0160 (non-breaking space) keyboard

>> input.

>> The view do not receive the WM_CHAR message if I use in

>> CMainFrame::PreTranslateMessage(...)

>> the m_wndMenuBar.TranslateMainFrameMessage() call.

>>

>> See the enclosed and modified StyleEditor Sample.

>>

>> to reproduce that behaviour:

>> - Make a breakpoint in CChildView::OnChar()

>> - press and hold the ALT key and type on num pad 0160 ( ALT + 0160 )

>> --> CChildView::OnKeyUp() is called but not CChildView::OnChar()

>>

>> now comment the lines

>> //    if( m_wndMenuBar.TranslateMainFrameMessage( pMsg ) )

>> //        return TRUE;

>> in CMainFrame::PreTranslateMessage(...)

>>

>> and repeat the steps above.

>>

>> --> CChildView::OnKeyUp() is called AND CChildView::OnChar() is called

>>

>>

>> Only ALT + 0160 is not working. All other combinations seems ok.

>>

>> Any idea?

Forum