After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 666468 - Lock mail folder structure
Lock mail folder structure
Status: RESOLVED DUPLICATE of bug 245025
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-12-18 22:21 UTC by Johann Glaser
Modified: 2012-04-06 13:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Johann Glaser 2011-12-18 22:21:56 UTC 
Every once in a while I accidentially keep the mouse button pressed in the tree view, which starts to drag mail folders around. Due to my large mail boxes, this consumes 100% CPU for 10-15 minutes, depending on what folders I accidentially moved.

Moving folders around is by far the most infrequent activity a normal Evolution user is doing. Although, it is reachable with extreme ease, even accidentially as described above.

Therefore I ask you to implement a way to lock the current folder structure, i.e., disable the drag and drop to move them around. Alternatively, a simple "Are you sure to move the mail folder xyz (containing 1.8 GB of data) to become a sub-folder of abc?" dialog would be good as well.

Thanks
  Hansi
Comment 1 Akhil Laddha 2011-12-19 04:15:14 UTC 
Is this about local folders (On this computer) or any server backend IMAP / Exchange / EWS / MAPI ?
Comment 2 Johann Glaser 2011-12-19 10:12:15 UTC 
Yes, I experienced the problem with local folders. On the other hand, what tremendous effort is necessary, to move folders on servers?
Comment 3 Milan Crha 2012-04-06 13:52:13 UTC 
I like the idea, especially if it'll be like "Yes/No/Always/Never" and only for drag&drop folder move within folder tree.
Comment 4 Milan Crha 2012-04-06 13:53:06 UTC 

*** This bug has been marked as a duplicate of bug 245025 ***