http://forum.codejock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Sun, 19 Apr 2026 17:48:30 +0000 Sun, 26 Mar 2017 06:02:38 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 forum.codejock.com/RSS_post_feed.asp?TID=23292 http://forum.codejock.com/forum_images/codejock-logo.gif http://forum.codejock.com/ http://forum.codejock.com/forum_posts.asp?TID=23292&PID=75653&title=dependency-on-feature-ninput-legacymode#75653 Author: MacW
Subject: 23292
Posted: 26 March 2017 at 6:02am

My app uses an embedded WebBrowser Control (HtmlView).
In order to support OpenLayers 3, I had to add the FEATURE_NINPUT_LEGACYMODE registry key for my app to disable legacy keyboard handling.

(See https://msdn.microsoft.com/en-us/library/ee330732(v=vs.85).aspx)

When this key exists in the registry, XTP menus and combo boxes work differently. When I open a menu, the "highlight" indicating the element under the mouse cursor no longer follows the mouse cursor.

Drop-down boxes in XTP control bars / toolbars no longer allow to select elements with the mouse, only with the keyboard.

Does XTP use any uncommon mouse move handling that may interfere with the WebBrowser control or that depends on the

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_NINPUT_LEGACYMODE

registry key?

As soon as I remove my app from this key, XTP behaves as before.


]]> Sun, 26 Mar 2017 06:02:38 +0000 http://forum.codejock.com/forum_posts.asp?TID=23292&PID=75653&title=dependency-on-feature-ninput-legacymode#75653