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: 1117262" data-attributes="member: 150866"><p>I started to implement the Qualified event names. The XAML parser runs into the attached properties section (as expected). I thought I could use part of the logic there (even the comments mention events already, so I guess it's intended).</p><p>For my 1st try I added "UIElement.MouseDown=..." to my XAML screen.</p><p>When it comes to resolving the type name UIElement the code runs into "MpfNamespaceHandler" which uses Mpf.ObjectClassRegistrations.</p><p>This dictionary contains only non abstract types, which makes sense since it's used for which types can be instantiated in XAML.</p><p>I think a nice extension would be to have abstract classes too, and have an optional parameter if abstract types are wanted as well.</p><p>Also the dictionary could be filled automatically, using reflection.</p><p>Do you think it's ok to implement changes like this to MpfNamespaceHandler?</p><p>Currently I'm stuck here, because events from abstract classes must be able to use.</p></blockquote><p></p>
[QUOTE="osre, post: 1117262, member: 150866"] I started to implement the Qualified event names. The XAML parser runs into the attached properties section (as expected). I thought I could use part of the logic there (even the comments mention events already, so I guess it's intended). For my 1st try I added "UIElement.MouseDown=..." to my XAML screen. When it comes to resolving the type name UIElement the code runs into "MpfNamespaceHandler" which uses Mpf.ObjectClassRegistrations. This dictionary contains only non abstract types, which makes sense since it's used for which types can be instantiated in XAML. I think a nice extension would be to have abstract classes too, and have an optional parameter if abstract types are wanted as well. Also the dictionary could be filled automatically, using reflection. Do you think it's ok to implement changes like this to MpfNamespaceHandler? Currently I'm stuck here, because events from abstract classes must be able to use. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Submit: Code Patches
Seek by clicking on video progress bar
Contact us
RSS
Top
Bottom