Comment 12 for bug 668895

Revision history for this message
su_v (suv-lp) wrote :

Testing r10035 with bundled osxapp version (local build):

Extensions from the shared extension folder:
- if <check> points to an existing script file in the shared extensions folder (txt2svg.inx -> txt2svg.pl), the extension is not loaded and not listed in the 'File > Open…' dialog
- if <check> points to a non-existing script file in the shared extension folder (txt2foo.pl), the extension is loaded, listed, and the script referenced in the <command> directive is executed
- if the <check> directive is removed from the INX file, the extension is loaded, listed and the script referenced in the <command> directive is executed.

Extensions from the user extensions folder:
- if <check> points to an existing script file in the user extensions folder, the extension is loaded, listed in the 'File > Open…' dialog and the script referenced in the <command> directive is executed
- if <check> points to a non-existing script file in the shared extension folder (txt2foo.pl), the extension is loaded, listed, and the script referenced in the <command> directive is executed
- if the <check> directive is removed from the INX file, the extension is loaded, listed and the script referenced in the <command> directive is executed.

-> it seems that your last change does not work for current extensions using the 'check>' directive that are distributed and installed with Inkscape in the shared extension folder, if inkscape was configured, built and packaged as osxapp.

AFAICT '<check>' is still broken, but I'll wait to confirm the tests with an official development snapshot build for osx as soon as it is available from <http://inkscape.modevia.com/macosx-snap/?C=M;O=D>