Community
Participate
Working Groups
After versioning a project or file a different application window (e.g. an explorer window) gets in front of the eclipse window. How to reproduce this behavior: -open an arbitrary application window (e.g. an explorer window) -use "Team" > "Tag as Version..." from the context menu of a project -enter a version tag and press OK -after versioning, the application window comes to the front Note: This behavior also occurs with the "Team" > "Branch..." dialog (but not with all team dialogs, e.g. "Replace With" > "Another Branch or Version...")
I am unable to reproduce this behavior in 3.2 and I looked at the code and everything appears OK. Perhaps the issue was resolved at the Workbench or SWT levels. If you see the problem in 3.2, please reopen.
I've tested it with Eclipse 3.2 M6 and still have the behavior that the wrong window gets the focus after "Tag as Version...". It seems be to be a problem in conjunction with switching between eclipse perspectives. The problem occurs -NOT- when -Eclipse is opened with the "Resource perspective" -use "Tag as Version..." from the context menu in the Navigator view The problem occurs when -Eclipse is opened with the "CVS Repository exploring Perspective" -switch to the "Resource perspective" -use "Tag as Version..." from the context menu in the Navigator view The problem occurs also when -Eclipse is opened with the "Resource perspective" -switch to the "CVS Repository exploring Perspective" -switch back to the "Resource perspective" -use "Tag as Version..." from the context menu in the Navigator view Additional information which may have an influence - only the resource and the repository perspectives are open - CVSNT and Windows XP was used - the project that was tagged was small (short time for tagging) - the CVS password was stored (no password dialog when taging as version) - the behavior is reproducable on other computers (tested also with Win XP)
I'm still not able to reproduce although I do recall seeing it in the past. This is probably happening because we notify the repo view of the tag changes and the view refreshes. The repo view refresh story needs to be reworked but we won;'t hae time in 3.2 to do so. Moving to 3.3.
We didn't have time to investigate this in 3.3.
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.
