Jordi Cabot via Pinterest
AU 2022 classes are available online now, as well as a new Dynamo book and resources project.
I also present some ongoing nitty-gritty discussions on external events and Idling:
Andrea @dre_tas Tassera shared his presentation at #AU2022 on #DevoOps for @AutodeskRevit, Deploy Better Plugins Faster Through CI/CD and Unit Testing in Azure DevOps:
At Woods Bagot we managed to cut the deployment time of our tools from days to minutes, while increasing quality and reliability, by repurposing common concepts and tools from the Software Development world. By implementing a DevOps philosophy in your workflow, not only do you deliver automation tools quicker, but you also empower your teams from the start, improving communication and collaboration and promoting professional growth. You increase quality and reliability of the software product deployed, thanks to automated testing and a faster feedback cycle. Moreover, with the ability of more frequent faster releases, backed up by live monitoring systems, developers can deploy tools that are tailored to the users and really respond to their needs. The session will showcase how Woods Bagot has developed a full workflow for their Revit toolbar through the use an Azure DevOps pipeline, but the principles can be applied to any platform that benefits from automation tools.
Paul F. @paulfaubin Aubin discussed Taming Parametric Curvature in the Revit Family Editor, complete with downloadable sample files and a step-by-step handout:
Have you ever tried to control the shape of a curved form parametrically in the Family Editor? If so, you’ve no doubt discovered that flexing them sometimes throws you a curveball. In this session we’ll explore several techniques to tame your unruly parametric curves. We’ll look at examples of circles, arcs, quarter round, half round, arches, and we’ll even check out some splines. We’ll look at both simple and compound curves. We’ll work primarily in the traditional Family Editor but most techniques apply to the massing Family Editor environment as well. We’ll explore curvature and rotation, using both armatures (or rigs) and formulas to constrain flexing behavior. We’ll even throw in some trigonometry for good measure! After this session, I cannot guarantee that you’ll never have another misbehaving curve in your family content, but what I can promise is that you’ll come away with several useful tools to help you tame them when curve-mischief strikes!
Chuong Ho initiated the online book project Awesome Dynamo.
The Awesome Dynamo project celebrates and aggregates authors, essential and complete content with a large contribution from the community, the main purpose of which is to store Dynamo core values and make it easy to learn, apply to work and explore power of Dynamo.
I'm in the process of working and perfecting it, so please help me if you can:
Several recent Revit API discussion forum threads deal with questions on chaining sequences of functionality, e.g., I would like to launch a command after the export file form closes:
Question: I have a custom button that launches the DXF Export window. I would like to be able to Launch another method after the Export window is closed. Currently, my code opens the Export Form and then launches my other method, but I need the second method to process using information from the form. Is there a way to do this?
Answer: The standard Revit API approach to launch a command after the previous one has been completed is to use the Idling event. Explanations and many samples are provided in the topic group on Idling and external events for modeless access and driving Revit from outside.
However, there are other possibilities as well. For example, check out these other recent discussions on similar topics:
In both of those, simpler solutions seem to be possible. We always recommand keeping to the KISS principle.
At the time of writing, the discussion is not yet wrapped up on Can you chain Idling events?
Question: Is it possible to chain Idling events?
Say I have two functions, FuncA and FuncB.
I want to run FuncA the first time Revit idles, then run FuncB after FuncA is done running and Revit idles again.
Inside my FuncA handler, I am removing the handler to FuncA from UIApp.Idling, but I cannot assign a new handler because I don't have a valid API context.
Is there a way for me to achieve my intended behavior?
My goal is
to download a file from a server and then open that file.
Answer 1: This doesn't sound like a good idea in general.
When Revit idles you want to run FunctionA; when it idles again you want to run FunctionA but with different settings, i.e., subscribe to FunctionA and change what FunctionA does based on what it did last. Then, after a set number of things that FunctionA does, unsubscribe. In the end, you are waiting for the same event in-between doing tasks with the same function.
You can use static variable etc. to store stage of FunctionA.
Answer 2: Afaik, you cannot chain them directly, but you can easily achieve the same effect:
handlerAhandlerA, unsubscribe from the Idling event, then subscribe to the Idling event and attach handlerBDepending on other factors, Revit may or may not execute other actions in between the two event handler calls, but their relative order should be preserved.
You say, I cannot assign a new handler because I don't have a valid API context.
Why not? Within the Idling event handler, I thought you do have a valid Revit API context.
Question: why do the actions A and B have to be executed separately? Can't you just execute them both within the same Idling event handler?
Answer 3: You should create a queue service for that, subscribing and unsubscribing Revit events in your App as static.
Something like this IdlingQueueService.cs maybe helps.
You can register the service in your IExternalApplication and add some Action to run on the Idling event;
each one is gonna run in a different Idling Event.
Response: Thank you all for your responses. I have tried 3 different solutions all to no success...
If I step back from all the details of my implementation, my problem is really not too complicated.
I just wish I could run the Execute function of IExternalCommand like below.
public Result Execute(
ExternalCommandData commandData,
ref string message,
ElementSet elements)
{
Object1 obj1 = new Object1(commandData)
await obj1.func1;
await obj1.func2;
obj1.func3; // THIS IS THE ONLY REVIT INTERACTION
return Autodesk.Revit.UI.Result.Succeeded;
}
This doesn't work because I cannot make the Execute function async but this is the theory.
Not being able to await func1 and func2 is what is causing me to dive so deep into idling events.
Func1 and Func2 have nothing to do with Revit:
Thank you all for the guidance
Answer: You forgot to explain that you are using 'await' functions.
Revit does not like async stuff, and your code looks odd. How can you add an await without an async method...
To work with async and Revit use the Revit.Async package, so the package gonna manage the Idling stuff.
Response: Sorry, I just edited my reply for clarity. I am not actually running the functions with await as shown. That is how I would do it if the Execute function could be made async.
Func1 and Func2 are async functions which is why I am/was trying to run them in idling events.
Answer: One thing that is important is that when an IExternalCommand is running the Idling is not gonna trigger until the command ends. The Idling means the Revit is not busy doing something and is ready to receive some user interaction.
I guess the best approach in your case should be to use Revit.Async package with something like this.
public async Task Execute()
{
await func1;
await func2;
await RevitTask.RunAsync(func3); //THIS IS THE ONLY REVIT INTERACTION
}
Using the RevitTask you can run the func3 in Revit context.
Starting again from scratch:
One correct, reliable and effective approach to address the situation you describe is to implement an external event.
In the event handler, simply run the code to execute func3.
All the rest has nothing to do with Revit and does not require the Revit API.
Therefore, you can execute it independently, externally, and simply raise the external event after func1 and func2 have completed successfully.
Oh dear. I just noticed your statement:
Func1 and Func2 are async functions which is why I am/was trying to run them in idling events.
Well, that is just about the opposite of what you could or should do. Or at least it is not intended, afaict.
Revit and its API is single threaded.
The Idling event handler is single threaded.
So, as long as that event handler is busy executing, e.g., your func1 and func2, it will block Revit from doing anything else.
The purpose of the Idling event is to enable you to execute some action as soon as Revit has stopped being occupied with and therefore blocked by other tasks.
This confirms my preceding answer: it seems to me that an appropriate way to handle this would be to disconnect func1 and func2 from Revit and your add-in as much as possible, and let them trigger an external event when they are completed, to execute func3.
Response: So, what I ended up doing is below. It seems to work but would love some feedback if it's unsafe:
This still feels like the original idling action is unnecessary and I should be able to just dive right into the async func1, but other than that this works!
Question: How would you recommend disconnecting Func1 and Func2? The functions are async in that they use async functions in them but I don't need them to run truly asynchronously. Blocking Revit is fine for them. At all points in my code base, I am awaiting the results of the async functions so that everything runs essentially synchronously. All of my problems are due to the fact that the Revit execute function cannot be made "async" so I cannot "await" func1 and func2.
I can't imagine that this is the first time this problem has been encountered. It's a pretty standard workflow assuming that other plugins need some sort of authentication. First send an HTTP request to a server, then following a successful response, do all the Revit stuff.
Answer: Yes, this is a standard situation, and I described the standard solution above. No need for async anything, just create an external event X, raise the event when func1 and func2 have completed, and execute func3 in the external event X handler. No Idling needed, no async needed.
Response: Oh maybe I need to learn more about how async works in C# if it's different than JS development.
I would expect that if run func1 and func2 without the await flag, func2 will start before func1 has completed and the external event will be raised before func1 and func2 are completed. This would not work for my code since I would be trying to run code before the authentication step (func1) is completed.
Have I misunderstood? Thanks.
Answer: In the context of the Revit. API, I would recommend scrapping async completely. That will totally simplify things.
Response: haha I wish, but I still need to send requests to external servers. I can't think of a way to do that without async.
Answer: Well, I did myself, many times, connecting desktop and cloud.
Not very long ago, async did not exist.
Push and pull functionality was up and running for decades before async was invented in the form you know it,
cf. the history of C#.
That said, Kennan Chen, author of Revit.Async, underlines the suggestion above by Luiz Henrique @ricaun Cassettari:
This seems to be a highly matched case that Revit.Async is designed to solve.
I came up with the idea of Revit.Async for a cloud-based RFA management system. The main use case was to query the server about the information of an RFA file (your function 1), then download it (your function 2) and finally place it with Revit API (your function 3). I used a pattern similar to Revit.Async to chain them up and it worked like a charm.
I suggest you to take a look at Revit.Async and you will not be disappointed.
Let's wrap up for the time being with two jokes:
async function
Jordi Cabot via Pinterest