baffling API limitations

Question

The API doesn't officially support threading (see below) or a way to close an active document. That said, a work around to closing an active document is to call...

SendKeys.SendWait("^{F4}");

...from a separate thread. That works fine, except I need to loop through opening and closing several documents. If I put any code at all after thread, it will run it before closing the previous document. I have tried a number of standard threading callback methods including...

Task.Factory.StartNew(() =>

ThreadPool.QueueUserWorkItem(new WaitCallback

AutoResetEvent.WaitOne()

with no luck. And Thread.Sleep() just stalls the error/crash. Does anyone have any ideas.

"Revit's internals make use of multiprocessing in only a few select isolated locations. None of these locations currently encompass the code in the Revit API, or any part of it. Thus Autodesk does not recommend making any calls to the Revit API from within simultaneously executing parallel threads. It may be that some part of the Revit API is isolated enough to be able to execute successfully from within such threading code in a test environment; this should not be taken to be a guarantee that the same source code will function for any model or situation, or that a future change in Revit will not cause this code to cease to function."

    public void OpenFile()
    {
        for (int i = 0; i < 3; i++)
        {
            uiApp.OpenAndActivateDocument(TargetPath(i));

            ThreadPool.QueueUserWorkItem(CloseDocProc);

            //any code here at all opens the next doc without closing the last
        }            
    }

    public void CloseDocProc(object stateInfo)
    {
        SendKeys.SendWait("^{F4}");

        //can run code here
    }

@topofsteel, could you please explain what happened when you tried using `AutoResetEvent.WaitOne`? It's clear that you will need to wait until CloseDocProc completes before performing any other operations, and if, as you say, that close has to be invoked from a separate thread, an event wait handle sounds like a good option... It's not clear why you can't run synchronously, however. Is your code running within AutoCad & therefore blocking the main message loop? Could your entire body of code be run on a separate thread, with no internal threading? — Simon MᶜKenzie, Aug 21 '12 at 02:49

score 1 · Accepted Answer · answered Aug 21 '12 at 20:18

The problem was the threading, just like they said. Using any of the callback methods it would freeze right at that point. And you can only do a limited number of things in the thread, it would not let me open a document, no matter what!

The answer was to use a single-threaded timer.

System.Windows.Forms.Timer;

calling my Open() method every 10 seconds or so and stopping the timer and running the last bit of code when a counter reached a certain point.

score 1 · Answer 2 · answered Aug 23 '12 at 15:20

Not sure if it could do the trick, but you can perhaps use this technique: http://adndevblog.typepad.com/autocad/2012/06/use-thread-for-background-processing.html

It's for AutoCAD, but I think it could work with Revit. Revit API, like the AutoCAD one, do not support multithreading. You should only call the API functions from the main thread.

You need if fact to marshal the call to the main thread. The simplest way to achieve that is creating a System.Windows.Forms.Control object on the main thread and call its Invoke() from the separate thread where you're closing the document.

Or you can also use the Idle Event in a creative way...

score 0 · Answer 3 · answered Dec 24 '13 at 15:31

0

Create a state machine in your app idle event handler that interacts with your thread and which handles the revit calls.

answered Dec 24 '13 at 15:31

Randall

512
1
5
15

baffling API limitations

3 Answers3