0 Members and 1 Guest are viewing this topic.
Yeah, I'm actually more versed in the Revit API than I am Fab API. The spool tool was my first foray into C# at all. It worked. It was also.. some of the ugliest code you'll ever see. I have since rewritten it twice and have a nice one of my own.What kind of walls are you hitting?Couple of things:Are you reading articles about it on The Building Coder?I also know that there were SDK samples that involved making and tweaking assemblies (revit assemblies). I suggest you toy with assemblies to facilitate spooling in normal Revit, by the way. Just use the normal UI to get familiar with how they work. I think the key is simply making an interface for that process because what you need is mostly there. It's just full of too many ridiculous prompts when you want it to batch, essentially.You first will need to automate the selection (or attainment of current selection) being turned into an assembly. Then you will need to generate assembly views that are both the views and the schedules (revit schedules are subclasses of views).You'll eventually have to automate the formatting of both of these, which is tough at first but I learned a lot from it.Or as Alina said, try out Victaulic's digs. But man.. there's a stupid amount of untapped potential in Revit for spooling and it's fun to finally get it wrestled down and see what that can do.
I may have to pick your brain later down the road with this.
When you say external event do you mean your command logic has to call the dockable window logic in order to work?
Vic creates spools by creating assemeblies while Sysque creates spools by creating sheets and schedules per spool.