Home Dashboard Directory Help
Search

MFC Ribbon buttons no longer working with touchscreen monitor. by Philippe Candelier


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 731161
Opened: 3/14/2012 7:59:57 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Button controls in an MFC Ribbon were working fine with touchscreen monitors in VS 2008. Since we've upgraded to VS 2010, they don't.

We have a touchscreen monitor (from ELO system). The ribbon buttons work fine with the mouse but are irresponsive when using the touchscreen. The monitor is in "Emulate mouse actions" mode. All controls work fine works except the ribbon buttons. It seems like the button will ignore "click" action unless the button is highlighted (i.e. yellow with the default blue interface). A button is normally highlighted when there is a mouse-over on it. The touchscreen doesn't do mouse-over, it directly attempt to click on the button.

The only workaround I have found is to "double-touch" the button to highlight it, then I can touch it again to trigger it.

Note : The "application menu" button and Quick Access Toolbar buttons work fine.
Details
Sign in to post a comment.
Posted by Philippe Candelier on 3/21/2012 at 5:27 AM
That fix is good news ! As this functionality is important for a lot of our customers we were hoping to get an ETA on the public availability of the fix. Or at least know if it is planned to be in an update, service pack or only in the next VS ? Best Regards.
Posted by MS-Moderator07 [Feedback Moderator] on 3/14/2012 at 11:18 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by MS-Moderator01 on 3/14/2012 at 8:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.