Reply to thread

Message

First changes are commited here: https://github.com/MediaPortal/MediaPortal-2/commit/5c1f41da3ebc053347da1f1b3f194037f6e48232

The auto complete is working with our own MPF object :
[ATTACH=full]157929[/ATTACH]

Then we can also use "goto to definition" (F12) on any element to jump into code:
[ATTACH=full]157930[/ATTACH]

Leads us to our source code file:
[ATTACH=full]157931[/ATTACH]

Open issues:
MarkupExtensions are not fully working, as they don't derive from System.Windows.MarkupExtension. You get a blue underline warning that it is used like a extension, but is not derived from it. This cannot be fixed easily
ResourceWrapper is using "object" as generic type. This is useful, but now XAML is checking types strictly: like "object" defined versus "Brush" expected. Not fixable for now
MPF-Converters are not known to XAML, it expects WPF-converters that use a different interface. Not fixable for now.
Any way, I'm really happy about the current improvements, it makes working with MPF-XAML much easier!

<blockquote data-quote="morpheus_xx" data-source="post: 1111488" data-attributes="member: 48495">First changes are commited here: <a href="https://github.com/MediaPortal/MediaPortal-2/commit/5c1f41da3ebc053347da1f1b3f194037f6e48232" target="_blank">https://github.com/MediaPortal/MediaPortal-2/commit/5c1f41da3ebc053347da1f1b3f194037f6e48232</a>The auto complete is working with our own MPF object <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />:[ATTACH=full]157929[/ATTACH] Then we can also use &quot;goto to definition&quot; (F12) on any element to jump into code:[ATTACH=full]157930[/ATTACH]Leads us to our source code file:&nbsp;[ATTACH=full]157931[/ATTACH] Open issues:<ol>
<li data-xf-list-type="ol">MarkupExtensions are not fully working, as they don't derive from System.Windows.MarkupExtension. You get a blue underline warning that it is used like a extension, but is not derived from it. This cannot be fixed easily</li>
<li data-xf-list-type="ol">ResourceWrapper is using &quot;object&quot; as generic type. This is useful, but now XAML is checking types strictly: like &quot;object&quot; defined versus &quot;Brush&quot; expected. Not fixable for now</li>
<li data-xf-list-type="ol">MPF-Converters are not known to XAML, it expects WPF-converters that use a different interface. Not fixable for now.</li>
</ol>Any way, I'm really happy about the current improvements, it makes working with MPF-XAML much easier!</blockquote>

[QUOTE="morpheus_xx, post: 1111488, member: 48495"] First changes are commited here: [url]https://github.com/MediaPortal/MediaPortal-2/commit/5c1f41da3ebc053347da1f1b3f194037f6e48232[/url] The auto complete is working with our own MPF object (y): [ATTACH=full]157929[/ATTACH] Then we can also use "goto to definition" (F12) on any element to jump into code: [ATTACH=full]157930[/ATTACH] Leads us to our source code file: [ATTACH=full]157931[/ATTACH] Open issues: [LIST=1] [*]MarkupExtensions are not fully working, as they don't derive from System.Windows.MarkupExtension. You get a blue underline warning that it is used like a extension, but is not derived from it. This cannot be fixed easily [*]ResourceWrapper is using "object" as generic type. This is useful, but now XAML is checking types strictly: like "object" defined versus "Brush" expected. Not fixable for now [*]MPF-Converters are not known to XAML, it expects WPF-converters that use a different interface. Not fixable for now. [/LIST] Any way, I'm really happy about the current improvements, it makes working with MPF-XAML much easier! [/QUOTE]