Openoffice calc help failed code#

Wndclass.lpszClassName = TEXT('Problem Window Class') Wndclass.style = CS_HREDRAW | CS_VREDRAW Return DefWindowProc(hwnd, message, wParam, lParam) LRESULT CALLBACK WndProc(HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam) I really don't want to resort to putting all of the work in the same thread as the UI as this would make the UI unresponsive during lengthy operations. I can't find anything anywhere about this phenomenon or what the root cause is. Given that there are NOT multiple threads attempting to access OpenOffice at the same time, this doesn't seem like it should be a threading issue at all. If you uncomment it, you'll find the program now launches OpenOffice Calc perfectly. Within the WinMain(.) function, there is a call to TestOOCalc that is commented out. If you compile and run this on a machine with the newest version of OpenOffice, it will hang.

Openoffice calc help failed code#

However, if I do NOT set a break point, when the hang occurs I can break execution and I'll find that the call stack indicates that it is stuck somewhere within the process of RPC invocation awaiting a return from WaitForMultipleObjectsEx(.).Р”В«elow is a complete code example. If I set a breakpoint just prior to the invocation of 'loadComponentFromURL', the hang will NOT occur. If the integration is first carried out within the same thread as the UI, subsequent creation and execution of a separate thread runs without error.Р”Р„nd this is the weirdest observation: I'm using Visual Studio 2005 for debugging. If the integration code is launched from the same thread as the UI, no error occurs. If no UI window is made, the code in the separate thread executes flawlessly. Even if the custom window procedure does absolutely nothing but pass all messages to the default window procedure, the error occurs. However, if ANY custom procedure is involved it does occur. If the window class does NOT involve a custom procedure, no error occurs. It just happens to be a different thread from the one handling the UI. I should note that any given time, there is only ONE thread doing OpenOffice integration. I did quite a bit of research before figuring out that the failure required the following two events:Р”РЋ.) Creation of a simple UI window with a custom procedure (even if that procedure did not do anything more than pass everything on to the default procedure)Р”Сћ.) Creation of a separate thread in which the code to launch OpenOffice (via COM and ActiveX) is executed

I noticed with one of the newer versions of OpenOffice that my program would timeout and fail any time I tried doing the export. It is designed to do so using COM and ActiveX integration with Microsoft Excel and OpenOffice Calc. I have a C++ application that sometimes needs to export information to a spreadsheet.