Jorg suggests that rather than saving a scheduled draft when a user starts editing it to prevent it from being sent while the user is editing, my background code should check before sending a draft to see whether there are any editing windows open for that draft. He points to this code as an example of how to do that.
I can't just change the add-on to behave that way, because users have come to expect that starting to edit a draft will cancel its scheduled send, so changing the behavior could cause scheduled messages to be sent that their users didn't intend, which would be very bad behavior.
However, I might be able to figure out a way to make Jorg's suggested behavior a configurable option.
If so, then I'd also have to figure out a new mechanism for removing a schedule from a draft, since editing the draft would no longer be the way to do that.
Jorg suggests that rather than saving a scheduled draft when a user starts editing it to prevent it from being sent while the user is editing, my background code should check before sending a draft to see whether there are any editing windows open for that draft. He points to this code as an example of how to do that.
I can't just change the add-on to behave that way, because users have come to expect that starting to edit a draft will cancel its scheduled send, so changing the behavior could cause scheduled messages to be sent that their users didn't intend, which would be very bad behavior.
However, I might be able to figure out a way to make Jorg's suggested behavior a configurable option.
If so, then I'd also have to figure out a new mechanism for removing a schedule from a draft, since editing the draft would no longer be the way to do that.