FAYT configuration changed with upgrade to 12.8 - backups don't reset functionality

Help & Support
1

Hopefully a minor issue. The FAYT options have changed in an incompatible way between 12.7 and 12.8

After the upgrade, my FAYT settings were unclear, and typing in a lister would invoke the "command" toolbar.

I restored a backup from before the upgrade, and the functionality wasn't reset.

Looking at the config page, I see

fL3C1U4
fL3C1U4.png782×704 29.9 KB

There is no 'detault' FAYT action, and all choices show a hot key.

Resetting to my choice of default action (Filter Bar) works fine, but restoring the 12.7 backup
resets it to the unknown state.

Thanks for all the great work otherwise. A fabulous update overall

2

Could you send us the config backup you're restoring so we can work out why it isn't setting the drop-down properly?

Please send it via private message or an email to crashdumps@gpsoft.com.au in case the config contains anything private.

3

On its way.

4

If it helps at all, I also lost this setting (had to reset to filter bar) but I lost it when upgrading from 12.6 to 12.7 (haven't upgraded to 12.8 yet).

5

Many thanks for sending the config to us. We've fixed that so it won't happen again. If you chose Filter Bar now it will stick for future versions.

(As a side-effect of fixing this, anyone choosing WSL Command as the default mode in 12.8 will need to chose it again in 12.8.1/12.9. But anyone choosing that as the default is unlikely. Note that you can't currently see the WSL Command option unless Windows Subsystem for Linux is installed, which is why you were getting a blank value in the drop-down.)

6

Was it definitely 12.6 to 12.7, and not to 12.7.1 or another beta later than 12.7?

As far as I can tell, 12.7.1 was the first version where it might have happened. If that's not true, please let me know, as I may have missed a situation and I'd like to make sure the fix covers everything.

7

Thank again! Awesome job!

8

You're probably right, maybe it wasn't 12.6. I did have problems with 12.7.2 and I went back to 12.7 so maybe that was the time it happened. Sorry, I just don't remember to well anymore.

1 Like
9

Understandable! No reason to remember these things most of the time. :slight_smile: I only know the exact versions things changed after checking the code history.

I think the change I've done should fix everything, in that case.

10

Just FYI, the point of the public beta program is so problems like this can be found and fixed before the general release, not after. Please report problems you find when you find them - don’t just rollback and wait for the next version.