4.157 / 4.159 File save dialog box choice no longer "sticky"

[Gibsonm]

I have a relatively complex "My scenarios" folder structure:

 

 

One of these is "aPlan files" where I try and save / store plan files.

 

In 4.023 and prior I'd follow the following steps to save the Plan file in the "right" place:

 

1. Select Save Plan and be presented with this dialogue box:

 

 

2. Select the "aPlan files" sub folder:

 

 

Because I didn't want to either write over the default choice, or retype the scenario name, I'd hit cancel.

 

3. I'd then choose "Save Plan" again and be presented with both the right location and the correct name:

 

 

Note: I've re-confirmed this today (the source of the screen shots with 4.159 installed beside 4.023).

 

In 4.157 and 4.159 the behaviour is:

 

1. Select Save Plan and be presented with this dialogue box:

 

 

2. Select the "aPlan files" sub folder:

 

 

However, hitting "Cancel" and then selecting "Save Plan" again now brings me back to:

 

 

That is the sub folder choice that was remembered in 4.023 (and prior) is no longer remembered in 4.157 or 4.159.

 

The end result is I now save the Plan file into the root "My Scenario"s folder and then post mission need to manually move it to the correct location.

 

The same behaviour is exhibited when attempting to save scenario files as well.

 

Edited August 11, 2019 by Gibsonm

[Ssnake]

Interesting.

I didn't even know that the old method worked, let alone that it was a conscious design decision. To that extent I don't feel us to be obliged to preserve it. But of course I can see the utility value of this or "something like this", so I'll see what we can do to make your life a bit easier here, maybe by dropping the annoying habit to replace the file name with the first file it finds in the target folder rather than preserving the original name until the user actually clicks of a different file.

[Ssnake]

This is now bug 7829.

[Gibsonm]

6 minutes ago, Ssnake said:

Interesting.

I didn't even know that the old method worked, let alone that it was a conscious design decision. To that extent I don't feel us to be obliged to preserve it. But of course I can see the utility value of this or "something like this", so I'll see what we can do to make your life a bit easier here, maybe by dropping the annoying habit to replace the file name with the first file it finds in the target folder rather than preserving the original name until the user actually clicks of a different file.

 

Yes I didn't know if it was an unintended feature in 4.023 and prior, or a concious decision, which was changed in 4.156 / 4.157 / 4.159.

Edited August 11, 2019 by Gibsonm