Moini wrote:Would your additional variable be a good idea to port to the current branches? I see you've even taken care of it for Windows, even though your version was intended for OS X.
- The current build system is legacy - personally, I'd not recommend to spend a lot of time changing minor (and not user-relevant) bits of it. If spending time, there'd certainly be other changes I'd push for first (e.g. improving relocation support for osx app bundles, without the relative path hack).
- The change for the other platforms was required, otherwise I would have had to add ifdef's in the prefs dialog (which I did not want to - the whole section of the prefs dialog probably needs another rework, either with a more pruned list of paths, or one that is platform- and build-specific. I definitely did not want to nor could go there at the time).
Moini wrote:(and while you're here, I'd like to grasp the opportunity: do you maybe have an idea why putting the extension into the user extensions directory didn't work for Lynn? I've covered all the options I could think of with looking into error log, permissions, broken inx file and wrong folder, ran out of ideas...)
I do not know why it failed to work for Lynn. Extensions installed (as copies, or symbolic links) into the Inkscape user profile folder (~/.config/inkscape/extensions) always worked for my, using local builds and any of (earlier and current) Inkscape packages for Mac OS X (created by myself or by other contributors like LiamW and tghs).
The provided Finder screenshot (link
) lacks context and details ... I'd check for the actual location (full path), comparing file modification dates e.g. of preferences.xml, extension-errors.log (to make sure this is the correct and currently used folder). I'd also check again the content of the two extension files installed there (many users save HTML pages from GitHub instead of downloading the actual raw files (or a ZIP of the repo). A broken INX file (e.g. a HTML page) does generate warnings to the console - on OS X, those warnings can be seen in Console.app.