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
MP2 evr
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="Realkane" data-source="post: 489742" data-attributes="member: 59430"><p>Hi,</p><p></p><p>I took a look into the MP-II source. The EVR-renderer is using the Direct3DDevice from the API. Thats the same in MP-I. I would prefer to build a new UI-Element in MP-II, which includes an own HWND handle and Direct3DDevice for EVR. With this I hope to avoid problems like the "flickering UI-Elements" and think that it could be better for future features (like Picture in Picture or so).</p><p></p><p>What do you thing about this?</p><p></p><p>Greetings,</p><p></p><p>Christian</p></blockquote><p></p>
[QUOTE="Realkane, post: 489742, member: 59430"] Hi, I took a look into the MP-II source. The EVR-renderer is using the Direct3DDevice from the API. Thats the same in MP-I. I would prefer to build a new UI-Element in MP-II, which includes an own HWND handle and Direct3DDevice for EVR. With this I hope to avoid problems like the "flickering UI-Elements" and think that it could be better for future features (like Picture in Picture or so). What do you thing about this? Greetings, Christian [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
MP2 evr
Contact us
RSS
Top
Bottom