Issue 312462 In Chromium: Investigate Using Caremotelayer For Mac
Analysis Toolpak for Mac. This handy add-on replaces Microsoft Analysis Toolpak in Excel 2008-2019 for Mac. It features a detailed migration guide for users switching from Analysis Toolpak to StatPlus:mac and has the Excel interface you already know! StatPlus:mac allows Mac users to perform all forms of data analysis from the very basics to complex analysis, including as non-parametric and regression analysis. StatPlus:mac offers you an ability to perform heavy-duty data analysis on your Mac in a familiar and convenient Excel environment. Integrating tightly with. Integrating tightly with Microsoft Excel, StatPlus:mac empowers Microsoft Excel with a set of heavy-duty statistical analysis and data management tools, turning Microsoft Excel for Mac into a full-featured statistical analysis suite. Statplus download for mac.
I am currently using: 'chromium-args': '-data-path='./save/' Which works great in Windows/Linux 32/64-bit; however, under Mac OS X, this directory is never made and/or never saved to. This issue mentions that the path could be relative to somewhere inside the.app directory; however, I have not seen any 'save' folder being created anywhere.
I can confirm this as we can't load this data back in as we can in Windows/Linux, it simply is not created as far as I can tell. Want to back this issue? We accept bounties via. Just adding my 10p to this - -data-path still doesn't work (as of 0.11.5) on OSX (Mavericks) What's worse is that if you specify the parameter, nw fails to create ANYTHING (thus no localStorage/cookies/WebDB/cache or anything else) - even if it just ignored the parameter it would be better than nothing!?
Issue 312462 In Chromium: Investigate Using Caremotelayer For Mac Pro
A possible related issue is people using process.execPath to find 'the Node Executable' will get a nasty shock on OSX (as it's buried inside the Node WebKit Application folder structure) - process.cwd seems to return a more useful value tho? Don't think it's permissions - even if I pre-create the folder it just doesn't bother writing anything to it (and no errors are generated in the console that I can see, either) I notice you have a fully qualified path from root which MIGHT be why it works for you - but that isn't what most people would want (anyone working cross-platform would DEFINATELY not want to do that). I'm thinking that because of the weirdo way OSX Apps are distributed (and my comments on execPath vs cwd may apply to that in particular) Here- I've tried 'data' and './data' - likely what most people will want - neither works (I've not tried./././ to 'tunnel out' but that's obviously no use on other platforms) gui.App.dataPath reports the 'relative' value of 'data' or './data' too so if it's relative to execPath, that would explain the problem (I'm guessing OSX doesn't let you write inside the bundle?).