Bugzilla@Mozdev – Bug 26076
Listen to ContextMenu->MoveTo
Last modified: 2019-05-17 04:30:09
You need to
before you can comment on or make changes to this bug.
Test driving quickFilters...
First thing I do is enable the "Assistant"...
Then right-click a mail and Move-To -> Recent -> Whatever...
Assistant doesn't pop-up...
I never drag mails, it requires the folder you want to drag into to be visible,
or some annoying mouse wiggling to scroll the folder list until the target
folder is visible. I always right-click and Move-To. quickFilters should listen
to those events.
Accepted. As a workaround, you can install my Addon QuickFolders which allows
doing a "quickMove" by pressing SHIFT+M and then typing. Also it completely
eliminates scrolling the folder tree if you set you QF tabs cleverly, and
finally has a "recent folders" tab which you can use to do the same. (drag to
the tab and see a popup of recent folders) I will attach a screenshot.
I have hundreds of folders and literally _never_ drag email to the folder tree
as using QuickFolders is faster.
Having said this, I agree that the quickFilters folder listener definitely
needs to be expanded to react to the "move to recent" context menu.
Created an attachment (id=8101) [details]
QuickFolders recent folders tab
0. Install QuickFolders
1. Drag up to the first tab
2. drag down to a recent folder or a child folder of a recent folder
3. Never use the folder tree to go to or move mail to a folder anymore
4. save time!
Thanks, I'll have a look at quickFolders.
>Having said this, I agree that the quickFilters folder listener definitely
>needs to be expanded to react to the "move to recent" context menu.
It should also listen to Context->MoveTo->Account->Folder; not only RECENT. If
that's not too hard to do, of course; comes a time of diminishing returns for
the hours it takes to code. Btw, I'm done with my testDriving; I've added
quickFolders to my permanent TB profile; it's a good extension to have even tho
I don't create filters all that often and can handle the rules easily.
(In reply to comment #3)
> Thanks, I'll have a look at quickFolders.
> Regarding this:
> >Having said this, I agree that the quickFilters folder listener definitely
> >needs to be expanded to react to the "move to recent" context menu.
> It should also listen to Context->MoveTo->Account->Folder; not only RECENT. If
> that's not too hard to do, of course; comes a time of diminishing returns for
> the hours it takes to code. Btw, I'm done with my testDriving; I've added
> quickFolders to my permanent TB profile; it's a good extension to have even tho
> I don't create filters all that often and can handle the rules easily.
Well from a completionist standpoint I definitely agree: any message move /
copy operation should be monitored (regardless on how it is carried out) - it
shouldn't be impossible as (like in this case) a global function is used. Here
it is the global Thunderbird function MsgMoveMessage which needs to be
"wrapped" in something; I did a similar thing on the Postbox platform which has
its own quickmove function (move by typing a folder name); the difference is
that I was able to undo the wrapping before the calling function finished.
My first attempt at wrapping _Thunderbird's_ MsgMoveMessage yesterday ended in
an evil infinitive loop (one I was only able to break out of by switching off
the filter assistant). The problem with functions that can be called following
a (keyboard, mouse, something changed) event is that they can be called from
multiple places in unexpected ways. On top of this you will not see in a
debugger what causes the subsequent calls.
Anyway, I do expect to upload a test version here soon. (Once I break that
evil loop). The other thing to watch out for is that the MsgMoveMessage isn't
called when my other methods of invoking the FA (filter assistant) are - which
would lead to the FA coming up twice.
Created an attachment (id=8102) [details]
3.0 prerelease 23
First test version, beware of recursion! If it happens you have to CTRL+ALT+DEL
to kill Thunderbird. Hope it doesn't :)
Fixed in Version 3.0.1 Released Nov. 21, 2015