1

I'm wondering if anyone has some pointers and/or a good guide on how to properly do events in the .Net Micro Framework.

I've gotten a Netduino and is playing around making a small wrapper framework around various components and I'm trying to make it sort of event driven. Started doing it the way I'm used to, but discovered there were several classes and interfaces in the Microsoft.SPOT namespace which seems event related, and I haven't used any of them before. For example:

  • Dispatcher
  • DispatcherFrame
  • DispatcherObject
  • DispatcherOperation
  • DispatcherTimer
  • EventHandlersStore
  • EventRoute
  • EventSink
  • IEventListener
  • IEventProcessor
  • RoutedEvent

And several more. How do I use all these properly? Should I use them?

As an example I'd like to create a wrapper around a photo/light sensor which raises an event whenever the light level changes. For this (I suppose?) I need to poll the value of an analog pin and see if it changes. I can do that pretty simply by firing off an observer on a separate thread or something like that. But is there an other way I should do this? I guess for example that I shouldn't have a thread per sensor as that could become quite many and the resources are pretty limited here?

Svish
  • 152,914
  • 173
  • 462
  • 620
  • I've always done netduino events the same way as in regular .net. It looks like some of these class's are useful for .net micro presentation: http://blogs.msdn.com/b/netmfteam/archive/2008/03/04/using-the-dispatcher.aspx – devshorts Dec 26 '12 at 03:10

1 Answers1

1

Use events just like you would in other .net versions.

Declare and use events.

Declare and use delegates if you have a custom method signature you want your subscriber to use.

Build custom event arguments if you want to follow the (sender, args) pattern, etc.

Subscribe/unsubscribe to events with an event handler or inline function.

Bottom line is there is nothing special about micro framework events. You have all the stuff you have in the other versions, so just focus on making a good api for your consumers with events like you typically would.

Paul Fryer
  • 9,268
  • 14
  • 61
  • 93