Bug 83374 - [Viewers] Pending... node in CVS Repository view hard to use
Summary: [Viewers] Pending... node in CVS Repository view hard to use
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-01-21 03:39 EST by Dani Megert CLA
Modified: 2019-09-06 15:38 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2005-01-21 03:39:40 EST
I20050118

I don't need to use the repository view that often but every time I need expand
the nodes it strikes me: an artificial node called "Pending..." without an icon
is inserted and later removed making it hard to expand (exactly hit) another
node: I often hit the wrong note because the item gets removed just then when I
click.

Suggestion: Set the font of the node that gets expanded to italic similar to
views that do some work. Optional: change the label of that node to either "
(pending...)" or " (expanding...)". This would make the UI more stable.
Comment 1 Michael Valenta CLA 2005-01-26 10:43:52 EST
The pending node is provided by the UI (DeferredTreeContentManager) so I'm 
moving this there. I like the idea of decorating the parent but this requires 
a relationship between the label provider and the content provider which 
currently does not exist in the JFace architecture.
Comment 2 Boris Bokowski CLA 2009-11-26 09:55:38 EST
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:38:08 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.