WxWidgets, Mac and Acrobat 9 SDK

Question

We are having a lot of problems in the Mac using wxWidgets whch have now started using as a cross platform replacement to ADM.
On MacOS 10.4 (Tiger):
Having the sample 'wxPlugin' from the Acrobat 9 SDK samples-folder installed in either Acrobat 9 Pro or Acrobat 9 Reader leads to malfunction in some circumstances.
The two issues we experienced are:
1. You cannot open a PDF from the Finder - it just happens nothing (if Acrobat hasn't been running before, it will start though).
2. You cannot shut down MacOS (or restart it) while Acrobat is running (it doesn't matter if there is any document open) - you have to quit Acrobat manually or "Force Quit".
This is due to the wxInitialize call during the plug-in initialization (a reduced plug-in which does nothing works, but adding the single call to wxInitialize() (nothing more) would lead to the issues described above). The following information should help to reproduce the problem:
1. The 'wxPlugin' sample hasn't been touched apart from adjusting the path to the wxWidgets headers and libraries.
2. For wxWidgets, version 2.8.7 and 2.8.8 has been used, both without success.
3. Both wxWidgets libraries have been build with the following configuration: ../configure --disable-unicode --disable-shared --disable-monolithic --enable-universal_binary
There are several other issues with the wxWidgets sample that may or may not be related to the above problems:
1. The wxWidgets message loop is never called (would be part wxEntry function normally):
2. This has more effects (but only for modeless dialogs, since modal dialogs have their own event queue while active):
a) Messages about entering the window aren't processed -> that would result in e.g. the mouse pointer being not changed, not showing up tooltips etc.
b) Idle events are never called
c) Windows are never deleted - so basically all (including the window controls) remain as memory leaks
The last two (b & c) can be solved by registering an AVIdleProc and calling there wxTheApp->ProcessIdle() ,but some messages still aren't properly processed - so modeless dialogs won't work properly.
This can be easily verified by the Acrobat 9 SDK wxPlugin sample - the mouse cursor doesn't change if you have a document open and you see e.g. the Hand, and you move over the Modeless dialog of the sample. The same is true for tooltips (but they aren't applied in the sample code) - only in certain circumstances, when the window has been active - they will work.
In order to get those events working, a call to wxTheApp->MacDoOneEvent() in the idle procedure would help, but that would make other parts of Acrobat irresponsible, so that is no solution - but might be a hint.
Regards
Michael Peters
Mapsoft

Answer 1

I have a plug-in for Reader 10 written using wxWidgets 3.0 under Mac OS X 10.7 and I have all problems
described in OP post. Issue with sockets is added. (when releasing socket object it has deleted twice sometimes)
In this thread Adobe says that a new wxWidges sample will be coming shortly.
The wxPlugin from SDK 11 samples looks like this:
ACCB1 ASBool ACCB2 PluginInit(void)
#ifndef MAC_PLATFORM
/* The following code is not supported on Mac. */
          wxInitialize();
          mainFrame = new AcrobatFrame;
          wxTheApp->SetTopWindow(mainFrame);
          return MyPluginSetmenu();
#else
return true;
#endif
Is that true that wxWidgets officialy not supported in Acrobat SDK?
Is there some approved and tested technique for proper using of wxWidgets with Acrobat SDK for Mac?