Hello Stephan, <div class="gmail_quote">2011/9/28 Stephan Bergmann <<a href="mailto:sbergman@redhat.com">sbergman@redhat.com</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">On 09/28/2011 10:46 AM, Michael Meeks wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Incidentally, while trying to get some StarBasic / VBA unit tests working with Moggi, it seemed that some of our hangs were down to dialogs showing up that were simply not visible, and spinning the mainloop waiting for a response. static void aBasicErrorFunc( const String&rErr, const String&rAction ) { rtl::OStringBuffer aErr( "Unexpected dialog: " ); aErr.append( rtl::OUStringToOString( rAction, RTL_TEXTENCODING_ASCII_US ) ); aErr.append( " Error: " ); aErr.append( rtl::OUStringToOString( rErr, RTL_TEXTENCODING_ASCII_US ) ); CPPUNIT_ASSERT_MESSAGE( aErr.getStr(), false); } void FiltersTest::setUp() { ErrorHandler::RegisterDisplay( aBasicErrorFunc ); } Solves that rather pleasantly, with the added bonus that it might help improve the accuracy / helpfulness our basic error reporting over time. I suspect we should do this for all unit-tests above tools, and the head-less smoketest too. </blockquote> </div> But isn't it the way that all dialogs are implicitly cancelled in headless mode, anyway? </blockquote></div>The Basic Error Dialog seems to be the only dialog at the moment that still tries to show up and results in a loop while waiting for user input. Micheal's patch fixed that problem for me and makes it possible to try to run basic code in unit tests. Markus