Open marcg1 opened 10 months ago
the rules should work, as well as the save location of other messages in the thread.
The history might still be affected by the TB 115 changers.
Killing and restarting TB seems to have fixed the problem for now. I did not restart after earlier 4.0.4>4.0.5 upgrade.
Will report back if the problem recurs.
The restart of Thunderbird following the upgrade to 4.0.5 has almost entirely fixed the issue. The suggested folder for save appears consistently with the following single exception.
When I click on a link in an email message, the suggestion disappears until I re-select the message in the message list pane or move to another message.
I am also having trouble with the "+shift" window disappearing. I have tried to identify when it disappears. Here are a couple things that I have found:
Sorry I don't have more to go on. I've been tying all sort of things to reproduce this consistently.
Windows 10 TB 115.3.3 32-bit Nostalgy 4.0.5
@mewalter I can reliably reproduce your first example (and maybe that's what was happening when I clicked on a link in an email and was taken to a browser window). For the second example, I can get the suggested folder to reappear by picking a different message in the original folder after returning.
thanks for testing all this
thanks for testing all this
Thanks for developing it!
I do not get an onFocusChanged when switching back to TB, so I probably cannot do a lot. Workaround is to click an unwanted message, the the wanted
Windows 11 TB 115.3.3 Nostalgy 4.0.5
After Save to a folder ("s"), the suggestion for SaveAsSuggested appears in the bottom-right Nostalgy notification area only ~half the time. When the notification is present, SaveAsSuggested ("S") works. When the notification is not present, SaveAsSuggested does not work. Tested the latter with the thought that this might be purely a display issue and that SaveAsSuggested in that case might do a save to the last folder used for a save ... but it didn't.
Didn't see anything relevant in the error console. Haven't found a sequence of actions that reliably trigger the issue.