Closed: Exporter dialog not using saved folder

[Hayo Baan]

I just noticed that the exporter dialog no longer uses the folder as saved within the snapshot. This used to work fine before, so there must have been a change that broke this (not sure which version introduced this though).

Hopefully this can get fixed easily.

[Kirk Baker]

Is this happening with multiple Export templates, Hayo?

Thanks,

-Kirk

[Hayo Baan]

Hi Kirk,

Sorry for the delay, but yes, it seems to happen with all templates (at least the ones I tried).

[Kirk Baker]

Hayo,

Sorry for the delay, but yes, it seems to happen with all templates (at least the ones I tried).

I looked over the code (and some of the old snapshot files) and the path is not stored in the snapshots.  The Exporter dialog saves the last path used in any given exporter (for all exporters) and should restore the last saved folder but definitely not per snapshot.

-Kirk

[Hayo Baan]

Huh? It most certainly does The path was (and is) present in all my snapshots.
And this is definitely the way it has worked before! My workflow depends on it...

[Hayo Baan]

Hi Kirk,

I checked some older versions and it works as expected up to v16765 so the bug must have been introduced somewhere after that release.

Hope this helps,
Hayo

[Kirk Baker]

Hayo,

Huh? It most certainly does The path was (and is) present in all my snapshots.
And this is definitely the way it has worked before! My workflow depends on it...

I'd like to see one (or more) of your snapshots, please.

-Kirk

[Hayo Baan]

Hi Kirk,

Sure. Here are two freshly created ones with the latest version of PM. As you can see the export path is definitely set. From the main_dialog section of the snapshot:

Code: [Select]

  prefs:
    :export_path: /Volumes/Data-2/Temp/
(the two snapshots use a different path, corresponding to the path I had selected prior to saving the snapshot).

My guess is the export_path is not correctly restored any longer, or that you perhaps altered the code and now use a different variable name?

Cheers,
Hayo

[Hayo Baan]

Kirk et al.,

awesome: I can confirm that Version 5 Build 17338 fixed this issue

Thanks,
Hayo