broken data export window

[the-Arioch]

the "update" button in 3.4.23 was not very intuitive and was not very comfort - but it worked

the last vertion made something quite weird and outright counterintuitive - changing the hidden options without warning

[joyfullservice]

I agree that this isn't the most intuitive approach. I am open to suggestions on how to improve this from a usability standpoint.

For existing tables it is easy enough to find them in the list and set the export format, but sometimes you want to set up your options to always export a specific table name by default in your general options, without this table necessarily existing in the current database.

For example, I would expect that most users would definitely want custom ribbons exported by default, but the USysRibbons table may not exist in every database. If you are updating your global options, you probably want to have the add-in export this table data anytime it exists. The approach I took on this was to allow this entry in vcs-options.json to exist, even though no table by that name may exist in the current database.

The question is how do we intuitively manage these entries for tables that don't necessarily exist in the current database.

[the-Arioch]

some button to add special rows to the tables list, like "USysRibbons?" in the "nullable variable" fashion, meaning the table may or may not exist?

OTOH, do we really need it as a global preference?

I mean, the exact list of tables is clearly per-database thing, not per-computer.

Personally i consider that window to be an option to the particular export operation of a particular DB file. And i believe this kind of fine-grained settings is needed.

I think, hence, the "global defaults" (if it should be at all) should rather be a separate window. Which would address not specific tables (there are none, globally), but "kinds" of table (system, user-created, etc) and maybe name templates (filename-like or regex).

But whatever "global" settings are, when the database file is being opened they are recalculated into the local, per-table-name settings, when can be finely adjusted for the given export operation.