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
Seek by clicking on video progress bar
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="osre" data-source="post: 1117248" data-attributes="member: 150866"><p>I have recognized some "confusion" with types for Point, Size, ...</p><p>In some classes the WinFoms System.Darwing.PointF, ... are used (like InputManager)</p><p>In other classes the (UIElement, ...) the SharpDX.Vector2 is used by defining "using PointF = SharpDX.Vector2;"</p><p>This brings a bit confusion and unnecessary conversions with it.</p><p>What is the intended type to use?</p><p>From my point of view both are not my 1st choice:</p><p>When using the WinFoms type, any plugin who needs to interact must reference WinForms (not a big deal, but not really necessary).</p><p>When using SharpDX types, then every Plugin needs to reference SharpDX, which might be a bit more of a problem, if the renderer should be exchangeable.</p><p>I would recommend to create some MP2 own types for these (like WPF does). By this a point can be called Point, ... Only in the rare classes where WinForms interop is needed, the name Point is a bit "ugly" b/c WinFoms has also a Point with in coordinates.</p></blockquote><p></p>
[QUOTE="osre, post: 1117248, member: 150866"] I have recognized some "confusion" with types for Point, Size, ... In some classes the WinFoms System.Darwing.PointF, ... are used (like InputManager) In other classes the (UIElement, ...) the SharpDX.Vector2 is used by defining "using PointF = SharpDX.Vector2;" This brings a bit confusion and unnecessary conversions with it. What is the intended type to use? From my point of view both are not my 1st choice: When using the WinFoms type, any plugin who needs to interact must reference WinForms (not a big deal, but not really necessary). When using SharpDX types, then every Plugin needs to reference SharpDX, which might be a bit more of a problem, if the renderer should be exchangeable. I would recommend to create some MP2 own types for these (like WPF does). By this a point can be called Point, ... Only in the rare classes where WinForms interop is needed, the name Point is a bit "ugly" b/c WinFoms has also a Point with in coordinates. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Submit: Code Patches
Seek by clicking on video progress bar
Contact us
RSS
Top
Bottom