I like to think one of the strengths of the Krypton Toolkit is the way it incorporates feedback from users. For example, today a developer requested a simple addition to the ButtonSpec to make their life a little easier. In response to his thread I have added Tag and Owner properties.

The Tag property allows you to associate any arbitrary object you like to the ButtonSpec instance. Owner is a reference to the component/control that owns that particular ButtonSpec. This allows you to hook multiple ButtonSpec.Click events to the same single event handler, examining the Owner/Tag to decide how to act.

This is easier than having to maintain some extra dictionary lookup to find the control that owns the instance or having to implement a different handler per button spec instance. A simple and quick change but one that makes life just that bit easier for developers.

6 Responses to “ButtonSpec Additions”

  1. Vesuvius Says:

    Any chance of a CTP anytime soon?

  2. Phil Wright Says:

    Not yet, maybe once I have all the proposed Toolkit changed made I will make one up.

  3. Wintermute Says:

    Tag properties always come in very handy when using certain gui controls, I like the idea. Good news, keep it up!

  4. Timo Salomäki Says:

    Hi Phil Wright! I really like Krypton Toolkit and I respect the work you have done for developer community! Two months ago I started an open source project called Cloud Toolkit.Net and it contains many free controls for .net developers. Now I’m asking you for a permission to implement ButtonSpec feature to the controls. Can I do it?

  5. Phil Wright Says:

    Hi

    You certainly don’t need permission to implement the idea of ButtonSpec definitions into your own project. Feel free to go ahead and add the same idea to your Cloud Toolkit.Net.

    Phil

  6. Timo Salomäki Says:

    Well thanks! By the way I really like Krypton Toolkit and I’ve been watching it getting better and better all the time. Release of version 1.7 was really nice Christmas present from YOU.

    Keep going!

    Timo Salomäki (DudeDesign)

Leave a Reply