Some thing to watch for ...

16 views

Skip to first unread message

Rick Grunwald

unread,

Dec 18, 2020, 3:34:56 PM12/18/20

to Jonathan Perry-Houts, Jonathan Kamens - Send Later SUPPORT, send-lat...@googlegroups.com

Since TB 75.6 I have noticed that some email when sent beyond the scheduled time, also stay in the drafts folder. They WERE sent so I just deleted them but it is something for testers to keep in mind

Also since one of the earlier versions to SL, the column sort does not "stick" I want it to sort by scheduled time ascending and that does not stay that way

When you clear the default time a little check mark appears. That is nifty! Could we get similar when we SET a default time? There is currently no visual cue to let you know it was successful

Thanks so much.

Jonathan Perry-Houts

unread,

Dec 19, 2020, 9:24:21 PM12/19/20

to Send Later Users

Could you explain what you mean by sent beyond the scheduled time? Do you mean messages for which Thunderbird was offline when the message was scheduled to send, but it was picked up correctly next time Thunderbird was opened, and not deleted from Drafts? I'll look into that. I suspect it has something to do with interacting with IMAP folders immediately after starting Thunderbird.

The column has been having all kinds of problems with sorting, persisting in the same location if you drag it around, and when messages are scheduled/rescheduled. I know this is annoying, but it's something that other add-ons have been experiencing as well. I know that Thunderbird Conversations implemented some complicated solution to partially solve the persistence problem, but a real fix requires that Thunderbird support a proper API to allow extensions to add columns. There is movement being made on the Thunderbird end to implement that, and I'm going to wait until that's finished before dealing with anything else column related. I don't want to do a lot of work on something that I know will change in the very near future anyway.

The checkbox was supposed to show up for the save button as well, but it looks like there was a bug in that function that was preventing that from happening. Thanks for catching that and letting me know! It'll be fixed in the next release.