simarilius-uk / inkscape_exportxy Goto Github PK

This is on Inkscape 1.0 (4035a4fb49, 2020-05-01) on Windows 10.

I downloaded the zip file from here this morning, unzipped it, and copied the Inkscape_Exportxy-master directory into my extensions directory. I then closed and restarted Inkscape, which I'd had open. The extension's option got added as Extensions > Export > Export XY, but was greyed out. Restarting Inkscape made no difference.

I tried changing the case of "X" and "Y" in the filenames to be consistent throughout, though since Windows ignores case in filenames, I didn't expect that to be a problem. It didn't help, anyway.

I don't know much about .inx files, but the extension's looks analogous to that of an extension I installed successfully, Apply Transforms. I can't see anything obviously wrong, given that similarity.

So I don't know what to do. Presumably Inkscape must "know" that some condition has failed, in order to grey out the menu option. Wouldn't it be helpful to report what that condition is, in English, in case it helps the user? E.g. "Manifest file not found", or "Python file locked against reading", or "Python can't find imported module".

I attach screenshots showing: the extension's directory in my extensions directory; the contents of the extension's directory; the .inx file, and the top of the Python file; the Edit > Preferences setting for my extensions directory, just to show that it matches where I put the extension; and the greyed-out menu option.

I could only get this extension to work after reading the following post: https://inkscape.org/forums/beyond/export-path-to-xy-coordinates-with/#c50671 I had to comment out lines 5 and 6 in the inx-file. This is with Inkscape 1.2.2,

Does the warn def just disable all the deprecation warnings from Inkscape 1.0?

I ask because this extension could be smaller and more capable if it was using the new API for 1.0 instead. See https://gitlab.com/inkscape/extensions/ for examples, especially the ones that output text.