Ok, so before you ask why on earth would you bother let me explain 🙂

As part of my work over at ClarionAddins I am always looking for way to improve the user experience as well as stretching my knowledge of .Net programming. I thought it might be nice to use WPF but since the Clarion IDE is targeting v2.0 of the .Net framework this is not so easy. Hence this example!

Of course there are many resources out there related to this topic, see below, but nothing I could discover specific to v2.0 so for me it took a little work to get there. I learnt a lot about reflection along the way!

This code assumes that the v3.5 Framework is installed on the target machine. For production it would of course be necessary to test for this and react accordingly.

Here is a screenshot of this technique being used in an addin I am working on:

WPF UserControl in an Addin Pad!



This one came to my attention a while back because of something that happens in the “Make all toolbars the same size” feature of my MainToolbarExtras addin. When the addin first adjusts the toolbar sizes it would trigger the HtmlHelp2 template to refresh its indexes. While not much of an issue depending on your hardware, this takes at least a little time and is annoying. Also, having a gazillion Pads in the IDE for a help system that is of no use just seems silly.

Normally you can just go to the AddinManager, select “Show Pre Installed Addins” and disable the addin you don’t want.


However, the HtmlHelp2 addin is a little bit special. It contains a special property in the addin definition; addInManagerHidden = "true" so you cannot actually see it in the Addin Manager!

The way to get rid of it is to delete or rename the HtmlHelp2 addin files.

  1. Close the IDE
  2. Navigate to \Clarion8\Bin\Addins\Misc\HtmlHelp2
  3. Delete or rename the two *.addin files (if you choose to rename them, rename the extension e.g. HtmlHelp2.addin.bak)
  4. Next time you start the IDE the HtmlHelp2 Menu items and Pads will no longer be there!


Of course you will have to redo this each time you load a new release from SoftVelocity…

Interestingly it should be possible for SV to “register” their help file so that it displays in the HtmlHelp2 UI but for some reason they have not done this.


PropertyPadExtras is available over at http://www.clarionaddins.com/addins/PropertyGridExtras.html

NOTE: This is still a work in progress but I plan to have it ready for release next week.

So far it is working for all the main property grids except those in reports. I am very excited to have got this code working and I think it will be a huge productivity boost.

The property grid state is saved on a per "context" basis. This means that, for example, all buttons in the window designer will have the same expanded/contracted categories in their property grid. Same with lists, prompts, etc.

This week I will be concentrating on stabilising and testing this new feature as well as making sure it also works in all areas of the IDE! If I get a chance some other ideas are: expand/contract all buttons, filter grid items, hide grid items.

Here is a short video showing how it works.



I am astonished it has taken me this long to post an announcement here, it just goes to show how busy I have been I think. Anyway, a long time in the making with loads of little tweaks required I am now proud to announce that my new website, dedicated to Addins for the Clarion IDE has been released for public consumption! 🙂


I plan to continue to blog here, the new site is more about making the addins easier to find and support.


This appears to be fixed now. I had recently installed the "Quick Cache" plugin for wordpress which was messing with the downloads. If you still have problems please let me know.

I am really sorry about this, I thought I had it fixed a few months back but it seems to have returned. Thanks to Alan or helping me track down the problem. It could be IE or it could be the plugin I am using for downloads. I will have another look into it tomorrow and hopefully find the cause.

In the meantime, Firefox seems to be fine and I guess other browsers too.

Oh, and I am still working like mad to get the new website up… this one is specifically for the addins and I am very excited about it. It is surprising how long the little details take though!