Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add options to store global default and per-workbook default export folder locations #10

Open
bskinn opened this issue Aug 8, 2017 · 4 comments
Milestone

Comments

@bskinn
Copy link
Owner

bskinn commented Aug 8, 2017

Can just add a couple of buttons to the form and store (a) the per-workbook default folder in that workbook, and (b) the global default folder in the .xlam.

Should implement a ~hidden helper function to easily clear the default folder from the .xlam.

Could also implement storage of all of the parameters on the form.

@bskinn bskinn added this to the Future milestone Aug 14, 2017
@bskinn bskinn modified the milestones: Future, Sooner Feb 7, 2020
@bskinn
Copy link
Owner Author

bskinn commented Feb 7, 2020

Form is getting complex enough that it's annoying to have to reconfigure everything every time.

@bskinn
Copy link
Owner Author

bskinn commented Feb 13, 2020

Storage of the save-to folder path will require addition of a validity check on that path. If the path isn't to an existing folder (maybe even check if it's writeable?), then disable export and change the font color to red.

@bskinn
Copy link
Owner Author

bskinn commented May 29, 2020

Probably implement ClassModule to hold settings info, translate to/from settings string. Probably makes the most sense to house the core defaults in this class, which are spit out if there's no settings Property on the .xlam or the active workbook, or if parsing of the options string fails.

Nonprintable character in settings string as separator?

@bskinn
Copy link
Owner Author

bskinn commented Jan 25, 2022

Add option to save multiple settings configurations? New modal dialog for settings save/load. Would want to stack all settings into a single document property, or else the number of properties would rapidly get out of hand.

OTOH, there's a character limit for document properties, but apparently no functional limit to the number of document properties that can be created.

Looks like the better way to go is to use Workbook.CustomXMLParts (see here and here, which does not have a size limit and which is intrinsically a structured datatype!

Maybe there's an XML parsing/writing library already available in the builtin References, too....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant