You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The release of nodes to CSV as an extension to Inkscape needs improvements to work with new parser.
Replace 'self.OptionParser.add_option' with 'self.arg_parser.add.argument' so that it works with Inkscape again. Will this be a new release and when? Thanks for your help, Kent Hardage
12/15/24 11:04am
Ok, I have made progress on this issue. I found the update nodes to csv on github for Inkscape 1.2 and the nodes_to_csv.py file had the changes to arg_parser.add.argument as needed to satisfy the #5 issue. I downloaded the zip then extracted files and copied the .inx and .py files into the extension folder in inkscape 1.2. Now the export nodes to csv works as expected.
Now inkscape 1.4 does not work with the 1.2 released .inx and .py files. When will there be a release of extension nodes to csv for inkscape version 1.4?? Thanks for your help. Kent Hardage
The text was updated successfully, but these errors were encountered:
The release of nodes to CSV as an extension to Inkscape needs improvements to work with new parser.
Replace 'self.OptionParser.add_option' with 'self.arg_parser.add.argument' so that it works with Inkscape again. Will this be a new release and when? Thanks for your help, Kent Hardage
12/15/24 11:04am
Ok, I have made progress on this issue. I found the update nodes to csv on github for Inkscape 1.2 and the nodes_to_csv.py file had the changes to arg_parser.add.argument as needed to satisfy the #5 issue. I downloaded the zip then extracted files and copied the .inx and .py files into the extension folder in inkscape 1.2. Now the export nodes to csv works as expected.
Now inkscape 1.4 does not work with the 1.2 released .inx and .py files. When will there be a release of extension nodes to csv for inkscape version 1.4?? Thanks for your help. Kent Hardage
The text was updated successfully, but these errors were encountered: