Articy Forum

While reading the MacroPlugin API docs, I saw this in MacroPLugin.Initialize: "If your plugin uses own WPF resource dictionaries you need to register them within this method using RegisterResource(String)"

I have limited experience with WPF. Does this mean I can add custom UI to Articy? If not, what is the usecase for adding in your own WPF resource dictionaries?

Yes you can add custom UI! This is mostly useful for settings, custom views etc. The only limitation is that the plugin ui can only be in their own window.
In the coming weeks we will release a plugin that will show you how you can utilize WPF for creating a settings dialog for your plugin.

Best regards

Nico

That sounds great. I look forward to the plugin.

[Nevigo] Nico Probst wrote:Yes you can add custom UI! This is mostly useful for settings, custom views etc. The only limitation is that the plugin ui can only be in their own window.
In the coming weeks we will release a plugin that will show you how you can utilize WPF for creating a settings dialog for your plugin.

Best regards

Nico

Hi, new here. I'm quite competent at WPF and having recently learned of Articy, I'd love to know more about this feature. This reply was back in March - has there been any updates or info on these custom UI windows?

Hi,

This reply was back in March - has there been any updates or info on these custom UI windows?

No official updates, sorry for that . But the plugin turned out to be bigger than expected, thus the delay. But hopefully we can release the plugin soon.

The tutorial for the WPF integration still has to wait a bit, because i have a lot of other things to do before that.

But i can give you some information to get you started:

• Follow the instructions here to create a new plugin for articy:draft.
• In Visual Studio you can add a UserControl (WPF) that will automatically take care of adding the necessary assembly references. (For some reason you can't add windows at this point, at least in my VS version)
• In both UserControl files (xaml and cs) change the UserControl type to Window. Effectively turning it into a window.
• Now just create a plugin menu button(using MacroCommandDescriptor) to open the window, using ShowDialog() for example.
• (Optional) You could pass in the ApiSession instance from the plugin to the window, to get access to plugin methods inside event handles for buttons for example.
• (Styling) You can even use our custom styles for controls, but you need to know the name of the styles, luckily this is mostly <ControlName>Style. For example TextBoxStyle, ButtonStyle etc.

Hope that gives you a rough idea how to get this to work.

Best regards

Nico

Awesome - thanks a bunch!

I can't wait for the plugin you guys are talking about, would be just great.