home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
Improvement Suggestions
Increase the number of key that can be used
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="metalmasterx" data-source="post: 8235"><p>Hi *,</p><p></p><p>first of all, I want to thank anyone working on this fantastic project. GREAT WORK!!!!!!!</p><p></p><p>No to my (little) feature request. Although it's not really a new feature but an extension of an existing one...</p><p></p><p>I have a USB remote control from shuttle (PN31, see <a href="http://eu.shuttle.com/en/DesktopDefault.aspx/tabid-123/554_read-1622/" target="_blank">http://eu.shuttle.com/en/DesktopDefault.aspx/tabid-123/554_read-1622/</a>). It is a great one because you don't need a driver, it's just like a combination of a wireless keyboard and a mouse in one control. </p><p></p><p>Of course, not all keyboard keys are available on the remote, but just a subset of the most commonly used ones (0-9, enter, backspace, esc, tab, volume+, volume-, pageup, pagedown). Additionally, it features a some of the "multimeda keys" that are also available on modern keyboards.</p><p></p><p>It would be very nice if I could configure them in MediaPortal! Otherwise, they are quite useless... If I press these buttons in the keys configuration dialog, the keystroke is recognized, but a weird special character is displayed. Also the ".", "-", "+" keys available on my remote (and my keyboard as well!!!) are not recognized correctly.</p><p></p><p>Technical note:</p><p>In the .NET System.Windows.Forms.Keys enumeration (see <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemWindowsFormsKeysClassTopic.asp" target="_blank">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemWindowsFormsKeysClassTopic.asp</a>), the following keys are the ones that I meant: </p><p></p><p>MediaTrackNext</p><p>MediaPlayPause</p><p>MediaTrackPrevious</p><p>MediaStop</p><p>Decimal </p><p></p><p>Other people might want to use e.g.</p><p>BrowserBack</p><p>BrowserSearch</p><p></p><p>or other "special" keys on the keyboard. </p><p></p><p>All these keys are recognized in the keys configuration dialog, but displayed as some special character. And, they cannot be used when they are configured (just ignored).</p><p></p><p>Do you see a chance to include these keys??? </p><p></p><p>Technical proposition: I think (correct me if I'm wrong) in .NET any keystrokes are handled using this Keys enumeration mentioned above.</p><p></p><p>Why not use the following pieces of c# code to convert between a key and its string representation that can be used in the xml file and in the config dialog?</p><p></p><p>#1: key->string</p><p>System.Windows.Forms.Keys key = Keys.MediaTrackNext;</p><p>string stringRepresentation = key.ToString();</p><p></p><p>#2: string->key</p><p>string stringRepresenation = "MediaTrackNext";</p><p>System.Windows.Forms.Keys key = System.Enum.Parse(typeof(Keys), stringRepresentation);</p><p></p><p>By this, you could avoid a "hardcoded" list of supported keys and any key you can think of could be used and configured. (Maybe it's just rubbish that I'm writing, correct me if I'm wrong!)</p><p></p><p>Thanks for reading this LOONG post. What do you think?</p><p></p><p>metalmasterx</p></blockquote><p></p>
[QUOTE="metalmasterx, post: 8235"] Hi *, first of all, I want to thank anyone working on this fantastic project. GREAT WORK!!!!!!! No to my (little) feature request. Although it's not really a new feature but an extension of an existing one... I have a USB remote control from shuttle (PN31, see [url]http://eu.shuttle.com/en/DesktopDefault.aspx/tabid-123/554_read-1622/[/url]). It is a great one because you don't need a driver, it's just like a combination of a wireless keyboard and a mouse in one control. Of course, not all keyboard keys are available on the remote, but just a subset of the most commonly used ones (0-9, enter, backspace, esc, tab, volume+, volume-, pageup, pagedown). Additionally, it features a some of the "multimeda keys" that are also available on modern keyboards. It would be very nice if I could configure them in MediaPortal! Otherwise, they are quite useless... If I press these buttons in the keys configuration dialog, the keystroke is recognized, but a weird special character is displayed. Also the ".", "-", "+" keys available on my remote (and my keyboard as well!!!) are not recognized correctly. Technical note: In the .NET System.Windows.Forms.Keys enumeration (see [url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemWindowsFormsKeysClassTopic.asp[/url]), the following keys are the ones that I meant: MediaTrackNext MediaPlayPause MediaTrackPrevious MediaStop Decimal Other people might want to use e.g. BrowserBack BrowserSearch or other "special" keys on the keyboard. All these keys are recognized in the keys configuration dialog, but displayed as some special character. And, they cannot be used when they are configured (just ignored). Do you see a chance to include these keys??? Technical proposition: I think (correct me if I'm wrong) in .NET any keystrokes are handled using this Keys enumeration mentioned above. Why not use the following pieces of c# code to convert between a key and its string representation that can be used in the xml file and in the config dialog? #1: key->string System.Windows.Forms.Keys key = Keys.MediaTrackNext; string stringRepresentation = key.ToString(); #2: string->key string stringRepresenation = "MediaTrackNext"; System.Windows.Forms.Keys key = System.Enum.Parse(typeof(Keys), stringRepresentation); By this, you could avoid a "hardcoded" list of supported keys and any key you can think of could be used and configured. (Maybe it's just rubbish that I'm writing, correct me if I'm wrong!) Thanks for reading this LOONG post. What do you think? metalmasterx [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
Increase the number of key that can be used
Contact us
RSS
Top
Bottom