Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I encountered a similar issue but with Acrobat plugins. While adjusting our Acrobat plugins to Acrobat X (10) we had to remove code related to ADM (Acrobat Dialog Manager - Used to be a cross-platform GUI framework on Acrobat 7, 8 &amp; 9. Removed with Acrobat X) and use a different GUI framework. </p> <p>Acrobat SDK comes with samples of using wxWidgets as a cross-platform framework so we headed that way (we support MAC &amp; Windows). The plugin architecture of Acrobat is very similar to the one you described above: dlls (for Acrobat plugins the binary file extension is *.api) which are dynamically loaded by a main process (exe) and their functions are being called in a documented, pre-defined order.</p> <p>Because the Acrobat wxWidgets example was written with 2.8.12 and due to the fact that this is the stable version we decided to NOT use the 2.9.x ongoing version. </p> <p>So we statically linked our plugins (total of 3 different plugins) to the wx2.8.12 libs and found out that if 3 of them are installed, the two that were loaded last were not functioning. By that I mean - Our custom wxFrames, wxWindows &amp; wxDialogs belonging to these two plugins were all messed up (like someone tried to erase them, with rubber :-)).</p> <p>Digging deeply we narrowed it down to the fact that the first plugin being loaded, initializes wxWidgets and the latter do not, even though the explicit call to wxInitialize(). Something there went wrong....</p> <p>Here I forgot to mention - In an Acrobat plugin you cannot change the DllMain() function, so the initialization of wx is done in a "Plugin Init() function".</p> <p>Just to be clear - The wx libs are statically linked to the *.api files, so each should have a "copy" of its own and not influence on each other. </p> <p>Using Google for 2-3 FULL days I managed to find <a href="http://old.nabble.com/Adobe-Plugin-having-problems-with-wxPanel%27s-children-td22702458.html" rel="nofollow">this</a> post ,which suggested to apply <a href="http://trac.wxwidgets.org/ticket/10562" rel="nofollow">this</a> patch (for 2.8x ONLY!!!). I believe (or hope) that the 2.9.x version does not suffer from this issue (didn't have the chance to check it).</p> <p>BTW - The patch is only one file which is very clear, so reading the code to understand it and to be calm that it does no harm is pretty easy.</p> <p>I hope others using wx 2.8.x and suffering from the same issue will find this.</p> <p>Omri</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload