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 2
Submit: Code Patches
Default Keyboard Shortcuts
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="morpheus_xx" data-source="post: 1220084" data-attributes="member: 48495"><p>I indeed forgot about this patch, sorry. </p><p></p><p>We need to check this more in detail, because I can imagine behavior changes due to the global key mappings. Did you try your modifications inside media list views?</p><p></p><p>As you now bind "m" to "Key.Mute", this probably breaks navigation inside the list (usually you would jump to the first media item starting with "m").</p><p></p><p>Would your way also work, if you move the code into an own plugin? This would be my preferred solution.</p></blockquote><p></p>
[QUOTE="morpheus_xx, post: 1220084, member: 48495"] I indeed forgot about this patch, sorry. We need to check this more in detail, because I can imagine behavior changes due to the global key mappings. Did you try your modifications inside media list views? As you now bind "m" to "Key.Mute", this probably breaks navigation inside the list (usually you would jump to the first media item starting with "m"). Would your way also work, if you move the code into an own plugin? This would be my preferred solution. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Submit: Code Patches
Default Keyboard Shortcuts
Contact us
RSS
Top
Bottom
