ExternalEvent.Raise() should accept parameters

[Anonymous]

I know this can be achieved in other ways, but i want to discuss the fact that this would be much understandable for developers ...

would be nice to have generics involved here having an interface like this:

IExternalEventHandler<T>


ExternalEvent<T> EE =  ExternalEvent.Create(handler IExternalEventHandler<T>);
EE.Raise(T obj);

[jeremytammik]

If you have an issue with the execution sequence, how about adding a millisecond-precise timestamp to each request before sending it, and sorting the requests by timestamp before executing them?

[Anonymous]

Jeremy, the problem is not in the execution sequence. Events are getting executed in the right order. The problem is that since the external event doesn't take an argument, I need to make sure that I am only raising one event at a time after setting the correct arguments in the event handler. The isPending property of event is set to false as soon as the event execution starts but before it finishes, and hence I can not rely on that to raise the next event. What Joshua suggested will work though.

[nice3point]

@Anonymousyou can use these external events, including asynchronous events with return value https://github.com/Nice3point/RevitToolkit#external-events

[matveevri]

This is prefect, i was looking for this solution for year or more and all this time it was here. By this handler i can pass any argument to execute command.

[Kennan.Chen]

Actually, the Revit.Async library is designed specifically to address this issue. Additionally, it provides the functionality to return results to the event caller. This allows you to use external event just like calling an asynchronous function.

Take a look at it here