Closed
Bug 339848
Opened 19 years ago
Closed 15 years ago
Expand/Collapse trees by NumPad+/NumPad-
Categories
(Thunderbird :: Mail Window Front End, enhancement)
Thunderbird
Mail Window Front End
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 130388
People
(Reporter: arkady.belousov, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; ru) Opera 8.54
Build Identifier: http://mozilla.mirrors.tds.net/pub/mozilla.org/thunderbird/releases/1.5.0.2/win32/ru/Thunderbird%20Setup%201.5.0.2.exe
When I press NumPad+/NumPad- in tree currently ignored by TB, and I don't know other (standard) methods for this.
Reproducible: Always
Comment 1•19 years ago
|
||
left/right ?
Reporter | ||
Comment 2•19 years ago
|
||
> left/right ?
Well, Left/Right keys do expand/collapse, but +/- will be better.
Comment 3•19 years ago
|
||
Do you mean this should expand/collapse the tree with the currently-selected message, or all trees in the current pane? I presume the former, as that's how Windows Explorer does it. (Outlook too?) Explorer does not respond the '+'
and '-' on the main keyboard.
Somewhat OT: In the Thread pane, '*' and '\' expand and collapse all trees for that folder (and the setting is sticky for each folder). These keys *used* to be '*' and '/' which meant they could both be hit at the keypad, like the '+' and '-' convention suggested here -- however '/' was taken over (several versions of Seamonkey ago) by Find In Message, so the backslash was used instead.
Now, Ctrl+F is used (in TB, anyway) for Find In Message, and '/' does nothing
-- it would be good to restore the '/' shortcut to Collapse Threads.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
Hardware: PC → All
Version: unspecified → Trunk
Reporter | ||
Comment 4•19 years ago
|
||
> Do you mean this should expand/collapse the tree with the currently-selected
> message, or all trees in the current pane?
+ expand tree-node, on which cursor is stayed. If it stayed on account - should be expanded account tree. If cursor is on folder (branch inside account), should be expanded folder (if there is subbranches). If cursor is on/in thread root-letter or on/in some message inside thread, then should be expanded/collapsed all current thread. But, if you will support collapsing only for part of thread (like folder in account), may be, this also will be useful.
> I presume the former, as that's how
> Windows Explorer does it. (Outlook too?) Explorer does not respond the '+'
> and '-' on the main keyboard.
Win9x, Explorer: +/- works.
> Somewhat OT: In the Thread pane, '*' and '\' expand and collapse all trees for
> that folder (and the setting is sticky for each folder). These keys *used* to
Thank you for info.
> Now, Ctrl+F is used (in TB, anyway) for Find In Message, and '/' does nothing
BTW, is there possibility to search over all folder and/or over selected messages (no only inside current message)? If not, I will fill request to enhancement.
Comment 5•19 years ago
|
||
(In reply to comment #4)
> BTW, is there possibility to search over all folder and/or over selected
> messages (no only inside current message)? If not, I will fill request to
> enhancement.
Right-click on a folder or account, and select Search from the menu.
Reporter | ||
Comment 6•19 years ago
|
||
> > BTW, is there possibility to search over all folder and/or over selected
> > messages (no only inside current message)? If not, I will fill request to
> Right-click on a folder or account, and select Search from the menu.
This (filtering) is useful, but not equal to searching: with searching, I see context, then press "continue" and come to next context, etc. Unfortunately, currently, as I see, searching is stops at letter boundary.
Reporter | ||
Comment 7•19 years ago
|
||
> > BTW, is there possibility to search over all folder and/or over selected
> > messages (no only inside current message)? If not, I will fill request to
> Right-click on a folder or account, and select Search from the menu.
This (filtering) is useful, but not equal to searching: with searching, I see context, then press "continue" and come to next context, etc. Unfortunately, currently, as I see, searching is stops at letter boundary. So, should I create new enhancement request?
Updated•18 years ago
|
QA Contact: front-end
Updated•17 years ago
|
Assignee: mscott → nobody
Comment 8•15 years ago
|
||
We don't actually do the tree keyboard shortcuts, we get them for free from the core, which needs to distinguish between numpad+ and regular+ before it can do this.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•