Bug 25498 - Missing summary after switching to another view
Summary: Missing summary after switching to another view
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 minor (vote)
Target Milestone: 2.1 RC1   Edit
Assignee: Boris Shingarov CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2002-10-29 12:05 EST by John Arthorne CLA
Modified: 2003-02-20 18:41 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2002-10-29 12:05:53 EST
Build 20021018

- Select a project and choose "Synchronize with repository"
- Notice that after the progress dialog disappears, it shows a 
summary of changes in the status linke
- Click on a resource in the resource navigator
- Now click back in the synchronize view
- The summary information is now missing

I don't know if this is a platform UI or CVS UI issue. The status line should
continue to be there whenever the current selection is in the sync view.
Comment 1 Eric Nickell CLA 2003-02-07 20:58:25 EST
eclipse 2.1 I200302061700 linux-gtk, j2sdk 1.4.1_01

Furthermore, if there is an existing non-visible fastview of Synchronize (e.g.,
because you did a synchronize earlier and iconized the window rather than
deleting it), and you synchronize a project, the fastview pops back out, but the
status bar *never* shows the summary information.

Since this is happening on linux box, and the original reporter was Win2000, I
don't think this is platform-related.  If I had been so empowered, I would have
changed OS to "All", but apparently only the original reporter and assignee can
do that.
Comment 2 Kevin McGuire CLA 2003-02-11 18:45:35 EST
I just realized that this affects accessibility since screen readers rely on 
this information.

We should try to fix for 2.1.
Comment 3 Kevin McGuire CLA 2003-02-20 18:41:42 EST
This appears fixed now.  I assume it was a UI bug that was fixed.

Pls reopen if you notice it again.