id
int64 1
6.5k
| bug_id
int64 2.03k
426k
| summary
stringlengths 9
251
| description
stringlengths 1
32.8k
⌀ | report_time
stringlengths 19
19
| report_timestamp
int64 1B
1.39B
| status
stringclasses 6
values | commit
stringlengths 7
9
| commit_timestamp
int64 1B
1.39B
| files
stringlengths 25
32.8k
| project_name
stringclasses 6
values |
|---|---|---|---|---|---|---|---|---|---|---|
3,830
| 138,378
|
Bug 138378 [Trim] can't drag a trim bar at all
|
N20060425 - I am able to drag views around and re-order the main coolbar but unable to start a drag with any trim items.
|
2006-04-25 10:43:10
| 1,145,980,000
|
verified fixed
|
5e9597d
| 1,146,060,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/layout/TrimCommonUIHandle.java
|
Eclipse_Platform_UI
|
3,831
| 137,384
|
Bug 137384 [Presentations] ClassCastException in org.eclipse.ui.internal.PartStack line 1305
|
Our RCP application has a IPerspectiveFactory that creates 2 IFolderLayout's for other plugins to add views to. This was working in eclipse 3.1.0, when we tried to migrate to eclipse 3.2RC1 we received a ClassCastException on startup, even with a clean workspace. Eclipse 3.2RC1 org.eclipse.ui.internal.PartStack line 1305 The offending line of code looks like this: PartPane pane = (PartPane)part; The part variable is actually an instance of org.eclipse.ui.internal.ViewStack. That stack at this point: Thread [main] (Suspended (exception java.lang.ClassCastException)) org.eclipse.ui.internal.ViewStack(org.eclipse.ui.internal.PartStack).showPart(org.eclipse.ui.internal.LayoutPart, java.lang.Object, boolean) line: 1305 org.eclipse.ui.internal.ViewStack(org.eclipse.ui.internal.PartStack).createControl(org.eclipse.swt.widgets.Composite, org.eclipse.ui.presentations.StackPresentation) line: 603 org.eclipse.ui.internal.ViewStack(org.eclipse.ui.internal.PartStack).createControl(org.eclipse.swt.widgets.Composite) line: 531 org.eclipse.ui.internal.ViewSashContainer(org.eclipse.ui.internal.PartSashContainer).createControl(org.eclipse.swt.widgets.Composite) line: 562 org.eclipse.ui.internal.PerspectiveHelper.activate(org.eclipse.swt.widgets.Composite) line: 244 org.eclipse.ui.internal.Perspective.onActivate() line: 832 org.eclipse.ui.internal.WorkbenchPage.onActivate() line: 2378 org.eclipse.ui.internal.WorkbenchWindow$6.run() line: 2612 org.eclipse.swt.custom.BusyIndicator.showWhile(org.eclipse.swt.widgets.Display, java.lang.Runnable) line: 69 org.eclipse.ui.internal.WorkbenchWindow.setActivePage(org.eclipse.ui.IWorkbenchPage) line: 2593 org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(java.lang.String, org.eclipse.core.runtime.IAdaptable) line: 657 org.eclipse.ui.internal.Workbench.busyOpenWorkbenchWindow(java.lang.String, org.eclipse.core.runtime.IAdaptable) line: 795 org.eclipse.ui.internal.Workbench.doOpenFirstTimeWindow() line: 1437
|
2006-04-18 17:40:59
| 1,145,400,000
|
resolved fixed
|
8d4070c
| 1,145,980,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PageLayout.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PartStack.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchMessages.java
|
Eclipse_Platform_UI
|
3,832
| 136,763
|
Bug 136763 Performance improvements to BindingManager
|
Build id: I20060413-0010 One of our performance tests that still shows significant regression is opening editors. With profiling I found that 0.8% of that time is in Collections.unmodifiableMap(...) called by three methods in BindingManager. Another 0.15% is from instantiating new TrigerSequence[0] in three locations in BindingManager. In the first case, the creation of an immutable map is completely unnecessary - the methods are private, the maps are never exposed across API boundaries, and there is never any risk that the maps will be modified. The creation of empty TriggerSequence arrays can also be avoided with a singleton. I will attach a patch that collectively saves about 1% of the total editor startup time (elapsed time as measured by sampling profiler). These are very simple and safe fixes that I recommend considering for RC2.
|
2006-04-13 17:44:31
| 1,144,960,000
|
verified fixed
|
4c0ed9b
| 1,145,980,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/bindings/BindingManager.java
|
Eclipse_Platform_UI
|
3,833
| 138,253
|
Bug 138253 [Trim] Extra space added by the Trim 'group' layout
|
Trim controls correctly designed to fit into the 'standard' status line height (22) don't fit because the Composite represetning the 'group' adds margin space.
|
2006-04-24 15:14:38
| 1,145,910,000
|
verified fixed
|
7e690d7
| 1,145,910,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/TrimBarManager.java
|
Eclipse_Platform_UI
|
3,834
| 131,105
|
Bug 131105 [EFS] CopyFilesAndFoldersOperation does not handle null locations
|
Stumbled on this problem when copying/moving resources between local and remote filesystems. Copying or moving a file from a project on a remote filesystem to a project on a local filesystem results in a source does not exist error; vice-versa produces a destination does not exist; nonlocal to nonlocal produces a destination does not exist. Partial stacktrace: MoveFilesAndFoldersOperation(CopyFilesAndFoldersOperation).validateDestinationLocation(IContainer) line: 1428 MoveFilesAndFoldersOperation(CopyFilesAndFoldersOperation).validateDestination(IContainer, IResource[]) line: 1357 MoveFilesAndFoldersOperation.validateDestination(IContainer, IResource[]) line: 217 ResourceNavigatorMoveAction(CopyResourceAction).isValid(Object) line: 166 ... Remark that all destination validation in these UI classes use IResource.getLocation() which is only usable for resources on the local filesystem. Because of this, it is impossible to seamlessly integrate local and nonlocal resources. I am using org.eclipse.ui.ide_3.2.0.I20060216-1200.jar but according to public CVS nothing has yet changed in the use of getLocation().
|
2006-03-09 10:38:30
| 1,141,920,000
|
verified fixed
|
8b63b30
| 1,145,900,000
|
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/actions/CopyFilesAndFoldersOperation.java
|
Eclipse_Platform_UI
|
3,835
| 137,527
|
Bug 137527 [PresentationAPI] (regression) Implementors of StackPresentation now must implement save/restore state methods
|
In previous releases it was okay not to implement the save/restore state methods for subclasses of StackPresentation. In recent builds, unexpected errors occur when restoring a perpsective from a previous run. Without code that looks like the following, no views are ever added to the StackPresentation on a restore event. public void restoreState(IPresentationSerializer serializer, IMemento savedState) { IMemento[] parts = savedState.getChildren(IWorkbenchConstants.TAG_PART); for (int idx = 0; idx < parts.length; idx++) { String id = parts[idx].getString(IWorkbenchConstants.TAG_ID); if (id != null) { IPresentablePart part = serializer.getPart(id); if (part != null) { addPart(part, null); } } } } public void saveState(IPresentationSerializer context, IMemento { TabItem[] items = tabFolder.getItems(); ArrayList parts = new ArrayList(3); for (int i=0; i<items.length; i++) { parts.add(getPartForTab(items[i])); } Iterator iter = parts.iterator(); while (iter.hasNext()) { IPresentablePart next = (IPresentablePart) iter.next(); IMemento childMem = memento .createChild(IWorkbenchConstants.TAG_PART); childMem.putString(IWorkbenchConstants.TAG_ID, context.getId(next)); } } We are fine with this change in behavior, we will update our presentation, however we should probably update the Javadoc.
|
2006-04-19 12:13:44
| 1,145,460,000
|
resolved fixed
|
cf82175
| 1,145,890,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PartStack.java
|
Eclipse_Platform_UI
|
3,836
| 109,361
|
Bug 109361 [Markers] Multiselection in problems view yields invalid status message
|
I20050906-1200 select multiple problems in the problems view -> the status message reads: "problem.statusSummarySelected"
|
2005-09-13 03:47:18
| 1,126,600,000
|
verified fixed
|
d2418e9
| 1,145,890,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/ProblemView.java
|
Eclipse_Platform_UI
|
3,837
| 137,977
|
Bug 137977 Missing view toolbars
|
Build: N20060421-0010 I am getting missing view toolbars in this build. It occurs when I first switch to a view in a view stack that was previously hidden. I have seen it with the breakpoints view and the synchronize view so far. Will attach a screenshot.
|
2006-04-21 12:02:14
| 1,145,640,000
|
resolved fixed
|
30ef50a
| 1,145,800,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/presentations/util/ProxyControl.java
|
Eclipse_Platform_UI
|
3,838
| 136,981
|
Bug 136981 [Trim] Failing trim gives multiple error dialogs
|
If a piece of contributed trim is failing during creation it will produce an error dialog during every subsequent call to 'fill'. Should 'wire off' bad trim once the failure has been detected once.
|
2006-04-17 09:36:50
| 1,145,280,000
|
verified fixed
|
e6ed186
| 1,145,650,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchMessages.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/TrimBarManager.java
|
Eclipse_Platform_UI
|
3,839
| 100,993
|
Bug 100993 [EditorMgmt][Presentations] Regression: Editor tabs do not remember order or active tab after restarting Eclipse
|
Editor tab order is not restored after closing and reopening Eclipse. 1. Open a few editors such that all tabs are completely visible. 2. Drag tabs to put in a specific order. 3. Close and reopen Eclipse. 4. Note that tabs are not in the order they were in when you closed Eclipse.
|
2005-06-20 20:25:36
| 1,119,310,000
|
resolved fixed
|
d3420d7
| 1,145,650,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/presentations/util/PresentablePartFolder.java
|
Eclipse_Platform_UI
|
3,840
| 137,767
|
Bug 137767 [Progress] UISynchronizer must clear Interrupt Status of the UI thread
| null |
2006-04-20 12:04:23
| 1,145,550,000
|
verified fixed
|
56b2f58
| 1,145,650,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/UILockListener.java
|
Eclipse_Platform_UI
|
3,841
| 130,297
|
Bug 130297 [Progress] dozens of "Scheduled refresh postponed due to conflicting operations" in Progress view
|
I20060301-0800 Eclipse suddenly got terribly slow, and tracing revealed that almost 100% of CPU time was burned in layouting the Progress view. Looking there, I found dozens of "Scheduled refresh postponed due to conflicting operations" jobs. I have scheduled a workspace sync every 1 hours.
|
2006-03-03 06:11:55
| 1,141,380,000
|
verified fixed
|
61a3852
| 1,145,640,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/FinishedJobs.java
|
Eclipse_Platform_UI
|
3,842
| 137,849
|
Bug 137849 Unable to set comparator in StructuredViewer
| null |
2006-04-20 18:04:42
| 1,145,570,000
|
verified fixed
|
9b1458c
| 1,145,630,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StructuredViewer.java
|
Eclipse_Platform_UI
|
3,843
| 137,341
|
Bug 137341 [WorkbenchParts] WorkbenchPage.closeEditors calls IWorkbenchPart.getSaveables after disposing the part
|
This violates the contract on IWorkbenchPart.dispose, which states that it will be the last method called on the part. One observable effect is that WorkbenchPage leaks Saveable reference counts for any editor that cleans up its saveable references on disposal and is not capable of handling getSaveables() after dispose(). This means that the "save as" dialog is often omitted. Also, the Saveables are only closed after the CHANGE_EDITOR_CLOSE event is fired from the window... this violates the contract on the CHANGE_EDITOR_CLOSE event, which is supposed to be fired after the part has been completely closed (for example, a CHANGE_EDITOR_CLOSE listener that tried to close an additional editor on the same saveable would not get the correct reference counts. POSSIBLE FIX: I believe the fix is as follows (in WorkbenchPage.closeEditors(IEditorReference[], boolean)) // Fire pre-removal changes for (int i = 0; i < editorRefs.length; i++) { IEditorReference ref = editorRefs[i]; // Notify interested listeners before the close window.firePerspectiveChanged(this, getPerspective(), ref, CHANGE_EDITOR_CLOSE); } deferUpdates(true); try { // ADD THIS BLOCK if(modelManager!=null) { modelManager.postClose(postCloseInfo); } // END OF ADDITION // Close all editors. for (int i = 0; i < editorRefs.length; i++) { IEditorReference ref = editorRefs[i]; // Remove editor from the presentation editorPresentation.closeEditor(ref); partRemoved((WorkbenchPartReference)ref); } } finally { deferUpdates(false); } // Notify interested listeners after the close window.firePerspectiveChanged(this, getPerspective(), CHANGE_EDITOR_CLOSE); // REMOVE THIS BLOCK: //if(modelManager!=null) { //modelManager.postClose(postCloseInfo); //} // END OF REMOVAL
|
2006-04-18 15:28:22
| 1,145,390,000
|
resolved fixed
|
8546938
| 1,145,630,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchPage.java
|
Eclipse_Platform_UI
|
3,844
| 136,475
|
Bug 136475 [Trim] Graphic is disposed error on shutdown
|
20060412 I got the following exception on shutdown - I am not sure what caused it !ENTRY org.eclipse.ui.workbench 4 2 2006-04-12 16:54:17.359 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". !STACK 0 org.eclipse.swt.SWTException: Graphic is disposed at org.eclipse.swt.SWT.error(SWT.java:3374) at org.eclipse.swt.SWT.error(SWT.java:3297) at org.eclipse.swt.SWT.error(SWT.java:3268) at org.eclipse.swt.graphics.Image.getBounds(Image.java:1105) at org.eclipse.swt.custom.CLabel.getTotalSize(CLabel.java:222) at org.eclipse.swt.custom.CLabel.computeSize(CLabel.java:154) at org.eclipse.jface.action.StatusLine$StatusLineLayout.computeSize(StatusLine.java:130) at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:219) at org.eclipse.swt.widgets.Control.computeSize(Control.java:418) at org.eclipse.ui.internal.layout.TrimLayout.arrange(TrimLayout.java:552) at org.eclipse.ui.internal.layout.TrimLayout.layout(TrimLayout.java:475) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:989) at org.eclipse.swt.widgets.Composite.layout(Composite.java:531) at org.eclipse.swt.widgets.Composite.layout(Composite.java:496) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:43) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:47) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:47) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:47) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:47) at org.eclipse.ui.internal.PerspectiveBarManager.relayout(PerspectiveBarManager.java:183) at org.eclipse.jface.action.ToolBarManager.update(ToolBarManager.java:348) at org.eclipse.ui.internal.PerspectiveSwitcher.removePerspectiveShortcut(PerspectiveSwitcher.java:295) at org.eclipse.ui.internal.PerspectiveSwitcher.access$2(PerspectiveSwitcher.java:282) at org.eclipse.ui.internal.PerspectiveSwitcher$ChangeListener.perspectiveClosed(PerspectiveSwitcher.java:156) at org.eclipse.ui.internal.PerspectiveListenerList$6.run(PerspectiveListenerList.java:172) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:816) at org.eclipse.ui.internal.PerspectiveListenerList.fireEvent(PerspectiveListenerList.java:58) at org.eclipse.ui.internal.PerspectiveListenerList.firePerspectiveClosed(PerspectiveListenerList.java:170) at org.eclipse.ui.internal.WorkbenchWindow.firePerspectiveClosed(WorkbenchWindow.java:1281) at org.eclipse.ui.internal.WorkbenchPage.dispose(WorkbenchPage.java:1555) at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(WorkbenchWindow.java:745) at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1482) at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:621) at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:597) at org.eclipse.ui.internal.WorkbenchWindow$2.run(WorkbenchWindow.java:710) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:708) at org.eclipse.jface.window.WindowManager.close(WindowManager.java:109) at org.eclipse.ui.internal.Workbench$12.run(Workbench.java:712) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:709) at org.eclipse.ui.internal.Workbench.access$8(Workbench.java:639) at org.eclipse.ui.internal.Workbench$14.run(Workbench.java:839) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.Workbench.close(Workbench.java:837) at org.eclipse.ui.internal.Workbench.close(Workbench.java:812) at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:618) at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:597) at org.eclipse.ui.internal.WorkbenchWindow$2.run(WorkbenchWindow.java:710) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:708) at org.eclipse.jface.window.Window.handleShellCloseEvent(Window.java:736) at org.eclipse.jface.window.Window$3.shellClosed(Window.java:682) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:159) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:925) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:949) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:934) at org.eclipse.swt.widgets.Decorations.closeWidget(Decorations.java:257) at org.eclipse.swt.widgets.Decorations.WM_CLOSE(Decorations.java:1606) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3248) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1539) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1634) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1915) at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:443) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1539) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1634) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1915) at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:443) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1539) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1634) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1920) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2964) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) !ENTRY org.eclipse.ui.workbench 4 2 2006-04-12 16:54:20.390 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". !STACK 0 org.eclipse.swt.SWTException: Graphic is disposed at org.eclipse.swt.SWT.error(SWT.java:3374) at org.eclipse.swt.SWT.error(SWT.java:3297) at org.eclipse.swt.SWT.error(SWT.java:3268) at org.eclipse.swt.graphics.Image.getBounds(Image.java:1105) at org.eclipse.swt.custom.CLabel.getTotalSize(CLabel.java:222) at org.eclipse.swt.custom.CLabel.computeSize(CLabel.java:154) at org.eclipse.jface.action.StatusLine$StatusLineLayout.computeSize(StatusLine.java:130) at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:219) at org.eclipse.swt.widgets.Control.computeSize(Control.java:418) at org.eclipse.ui.internal.layout.TrimLayout.arrange(TrimLayout.java:552) at org.eclipse.ui.internal.layout.TrimLayout.layout(TrimLayout.java:475) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:989) at org.eclipse.swt.widgets.Composite.layout(Composite.java:531) at org.eclipse.swt.widgets.Composite.layout(Composite.java:496) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:43) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:47) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:47) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:47) at org.eclipse.ui.internal.layout.LayoutUtil.resize(LayoutUtil.java:47) at org.eclipse.ui.internal.PerspectiveBarManager.relayout(PerspectiveBarManager.java:183) at org.eclipse.jface.action.ToolBarManager.update(ToolBarManager.java:348) at org.eclipse.ui.internal.PerspectiveSwitcher.removePerspectiveShortcut(PerspectiveSwitcher.java:295) at org.eclipse.ui.internal.PerspectiveSwitcher.access$2(PerspectiveSwitcher.java:282) at org.eclipse.ui.internal.PerspectiveSwitcher$ChangeListener.perspectiveClosed(PerspectiveSwitcher.java:156) at org.eclipse.ui.internal.PerspectiveListenerList$6.run(PerspectiveListenerList.java:172) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:816) at org.eclipse.ui.internal.PerspectiveListenerList.fireEvent(PerspectiveListenerList.java:58) at org.eclipse.ui.internal.PerspectiveListenerList.firePerspectiveClosed(PerspectiveListenerList.java:170) at org.eclipse.ui.internal.WorkbenchWindow.firePerspectiveClosed(WorkbenchWindow.java:1281) at org.eclipse.ui.internal.WorkbenchPage.dispose(WorkbenchPage.java:1555) at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(WorkbenchWindow.java:745) at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1482) at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:621) at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:597) at org.eclipse.ui.internal.WorkbenchWindow$2.run(WorkbenchWindow.java:710) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:708) at org.eclipse.jface.window.WindowManager.close(WindowManager.java:109) at org.eclipse.ui.internal.Workbench$12.run(Workbench.java:712) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:709) at org.eclipse.ui.internal.Workbench.access$8(Workbench.java:639) at org.eclipse.ui.internal.Workbench$14.run(Workbench.java:839) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.Workbench.close(Workbench.java:837) at org.eclipse.ui.internal.Workbench.close(Workbench.java:812) at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:618) at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:597) at org.eclipse.ui.internal.WorkbenchWindow$2.run(WorkbenchWindow.java:710) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:708) at org.eclipse.jface.window.Window.handleShellCloseEvent(Window.java:736) at org.eclipse.jface.window.Window$3.shellClosed(Window.java:682) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:159) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:925) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:949) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:934) at org.eclipse.swt.widgets.Decorations.closeWidget(Decorations.java:257) at org.eclipse.swt.widgets.Decorations.WM_CLOSE(Decorations.java:1606) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3248) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1539) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1634) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1915) at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:443) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1539) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1634) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1915) at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:443) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1539) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1634) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1920) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2964) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-04-12 17:05:42
| 1,144,880,000
|
verified fixed
|
c0b0403
| 1,145,630,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PerspectiveSwitcher.java
|
Eclipse_Platform_UI
|
3,845
| 137,640
|
Bug 137640 [CommonNavigator] New java elements not selected in project explorer
|
3.2 RC1 - show the Project Explorer view - create a Java project - select the project and create a package (e.g. using the toolbar button) - the package is created, but not selected (it does get selected in the Package Explorer) - select the package - create a new class - the class is created, but not selected (works in the PE) In both cases, the selection gets cleared. This results in subsequent package or class creations not knowing which source folder they should apply to. E.g. try creating two packages in a row.
|
2006-04-19 21:46:17
| 1,145,500,000
|
resolved fixed
|
c4c54e6
| 1,145,630,000
|
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentService.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentServiceContentProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentServiceLabelProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorPipelineService.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorContentDescriptorManager.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/SafeDelegateCommonLabelProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/INavigatorContentExtension.java
|
Eclipse_Platform_UI
|
3,846
| 137,784
|
Bug 137784 [Progress] progress colors not alternating correctly
|
20060420 When we refresh entries in the progress viewer we frequently do not get alternating colours (usually all grey). STEPS 1) Load the jobs example 2) Start a job 3) Start a second job Both are grey.
|
2006-04-20 12:57:49
| 1,145,550,000
|
verified fixed
|
d583225
| 1,145,580,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/DetailedProgressViewer.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressInfoItem.java
|
Eclipse_Platform_UI
|
3,847
| 132,821
|
Bug 132821 [Dialogs] Stored Dialog location and size invalid after changing font
| null |
2006-03-22 06:19:16
| 1,143,030,000
|
verified fixed
|
2e9f235
| 1,145,560,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/Dialog.java
|
Eclipse_Platform_UI
|
3,848
| 137,410
|
Bug 137410 [Presentations] ViewPane does not ask the ActionBarPresentation to create the toolbar control
|
The ViewPane class does ask the action bar presenation to create the toolbar manager but it does not ask it to create the toolbar control. Patch to follow.
|
2006-04-18 20:29:29
| 1,145,410,000
|
resolved fixed
|
c7b967b
| 1,145,560,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindowConfigurer.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/presentations/DefaultActionBarPresentationFactory.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/provisional/presentations/IActionBarPresentationFactory.java
|
Eclipse_Platform_UI
|
3,849
| 137,334
|
Bug 137334 [PerspectiveBar] Order of perspective bar items not maintained across sessions when coolbar not shown
| null |
2006-04-18 15:04:49
| 1,145,390,000
|
verified fixed
|
39deba3
| 1,145,550,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java
|
Eclipse_Platform_UI
|
3,850
| 137,375
|
Bug 137375 [Trim] too many resize calls
|
N20060418-0010 - In debugging some HeapStatus code I noticed that just on starting up the workbench I receive many computeSize calls. This must affect performance. Here are my results on starting up an inner workspace: 1) first computeSize from updateLayoutDataForContents as a result of restoring the workbench 2) second computeSize is a result of the Shell.setVisible() call which opens the workbench and causes the shell to layout 3) third is a result of an arrange call from the TrimLayout 4) the fourth is a result of another arrange call after a test for showRaggedTrim 5) the fifth looks like the fouth 6) TrimCommonUIHandle computesize calls compute size on the HeapStatus 7) the seventh looks like the fourth 8) the eigth looks like the sixth 9) looks like the fourth Computing the size 9 times can't be right.
|
2006-04-18 16:54:52
| 1,145,390,000
|
verified fixed
|
3aeec01
| 1,145,550,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/layout/TrimCommonUIHandle.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/layout/TrimLayout.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/presentations/PresentationUtil.java
|
Eclipse_Platform_UI
|
3,851
| 127,550
|
Bug 127550 [Progress] Little text centred in a big view
|
I20060213-0800, GTK+ 2.8.8, KDE 3.4.3, X.org 6.8.2, Linux 2.6.14 There is a little piece of text in the centre of the progress view if I open when nothing is running. This text looks a little out of place left horizontally aligned, and centre vertically aligned in a rather large sea of white space.
|
2006-02-13 16:04:32
| 1,139,860,000
|
verified fixed
|
f3ff35c
| 1,145,540,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/DetailedProgressViewer.java
|
Eclipse_Platform_UI
|
3,852
| 130,340
|
Bug 130340 [Decorators] lightweight decorator blinking problem
|
Mylar uses a lightweight to indicate interest level for any structured viewer (e.g. the most interesting java elements are bold in the Package Explorer). The problem is that when a refresh is requested (e.g. markers change), the elements become unbolded, then bolded again when they're decorated. This is additionally aggrevated by the fact that the pause while they blink can be well over a second because the decoration job priority is so low. A more severe version of this problem shows up when a downstream plug-in (Visual Source Safe is the only one we know of) calls overly frequent refresh/decoration on the Package Explorer. The bold/unbold blinking can be continuous during check-outs and background refreshes. This problem is not Mylar-specific, but should manifest for anyone who uses bold font in a lightweight decorator. Is there a way that the font, text, and image from the last decoration could be preserved until the decoration happens and not disappear when the refresh happens? It seems that this would give behavior that's consistent with a regular decorator and be safe to downstream plug-ins causing this sort of blinking.
|
2006-03-03 11:45:59
| 1,141,400,000
|
verified fixed
|
360ea32
| 1,145,480,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/DecoratingLabelProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerLabel.java
|
Eclipse_Platform_UI
|
3,853
| 137,315
|
Bug 137315 [Dialogs] Doubleclickable area to restore dialog size is often very small
| null |
2006-04-18 14:13:57
| 1,145,380,000
|
verified fixed
|
d997c57
| 1,145,480,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/Dialog.java
|
Eclipse_Platform_UI
|
3,854
| 137,564
|
Bug 137564 [JFace] - TitleAreaDialog test failures in N20060419-0840
|
testSetTitleImageDisposed Error Graphic is disposed org.eclipse.swt.SWTException: Graphic is disposed at org.eclipse.swt.SWT.error(SWT.java:3374) at org.eclipse.swt.SWT.error(SWT.java:3297) at org.eclipse.swt.SWT.error(SWT.java:3268) at org.eclipse.swt.graphics.Image.getImageData(Image.java:830) at org.eclipse.swt.widgets.Display.createPixbuf(Display.java:955) at org.eclipse.swt.widgets.ImageList.set(ImageList.java:115) at org.eclipse.swt.widgets.ImageList.add(ImageList.java:48) at org.eclipse.swt.widgets.Label.setImage(Label.java:485) at org.eclipse.jface.dialogs.TitleAreaDialog.setTitleImage(TitleAreaDialog.java:644) at org.eclipse.jface.tests.dialogs.TitleAreaDialogTest.testSetTitleImageDisposed(TitleAreaDialogTest.java:56) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:330) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:204) at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35) at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) 0.131 testSetTitleImageNull Success 0.083 testTexts Error Workbench has not been created yet. java.lang.IllegalStateException: Workbench has not been created yet. at org.eclipse.ui.PlatformUI.getWorkbench(PlatformUI.java:92) at org.eclipse.ui.internal.WorkbenchPlugin.getWorkbench(WorkbenchPlugin.java:563) at org.eclipse.ui.tests.harness.util.DialogCheck.getShell(DialogCheck.java:97) at org.eclipse.jface.tests.dialogs.TitleAreaDialogTest.testTexts(TitleAreaDialogTest.java:73) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:330) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:204) at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35) at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-04-19 14:26:36
| 1,145,470,000
|
verified fixed
|
085bda2
| 1,145,470,000
|
tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/dialogs/TitleAreaDialogTest.java
|
Eclipse_Platform_UI
|
3,855
| 136,292
|
Bug 136292 [Markers] problems view: NPE after delete
|
20060412-0010 Not sure if this is reproducable, but when I deleted a project, I got the following exception. The problem view was grouped by 'Type' at that moment. !ENTRY org.eclipse.ui.ide 4 4 2006-04-12 10:13:35.483 !MESSAGE Marker id: 4684521 not found. !STACK 1 org.eclipse.core.internal.resources.ResourceException: Marker id: 4684521 not found. at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:56) at org.eclipse.core.internal.resources.Marker.getType(Marker.java:194) at org.eclipse.ui.views.markers.internal.Util.getMarkerTypeName(Util.java:380) at org.eclipse.ui.views.markers.internal.FieldCategory.getValue(FieldCategory.java:61) at org.eclipse.ui.views.markers.internal.FieldCategory.compare(FieldCategory.java:88) at org.eclipse.ui.views.markers.internal.CategorySorter.compare(CategorySorter.java:58) at org.eclipse.ui.views.markers.internal.CategorySorter.compare(CategorySorter.java:72) at org.eclipse.jface.viewers.ViewerComparator$1.compare(ViewerComparator.java:184) at java.util.Arrays.mergeSort(Arrays.java:1284) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.sort(Arrays.java:1223) at org.eclipse.jface.viewers.ViewerComparator.sort(ViewerComparator.java:182) at org.eclipse.ui.views.markers.internal.MarkerAdapter.buildAllMarkers(MarkerAdapter.java:251) at org.eclipse.ui.views.markers.internal.MarkerView.updateForContentsRefresh(MarkerView.java:544) at org.eclipse.ui.views.markers.internal.MarkerView$MarkerProcessJob.run(MarkerView.java:148) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) !SUBENTRY 1 org.eclipse.core.resources 4 376 2006-04-12 10:13:35.483 !MESSAGE Marker id: 4684521 not found. !ENTRY org.eclipse.core.jobs 4 2 2006-04-12 10:13:35.573 !MESSAGE An internal error occurred during: "Process resource updates". !STACK 0 java.lang.NullPointerException at java.lang.String.compareTo(String.java) at org.eclipse.ui.views.markers.internal.FieldCategory.compare(FieldCategory.java:88) at org.eclipse.ui.views.markers.internal.CategorySorter.compare(CategorySorter.java:58) at org.eclipse.ui.views.markers.internal.CategorySorter.compare(CategorySorter.java:72) at org.eclipse.jface.viewers.ViewerComparator$1.compare(ViewerComparator.java:184) at java.util.Arrays.mergeSort(Arrays.java:1284) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.sort(Arrays.java:1223) at org.eclipse.jface.viewers.ViewerComparator.sort(ViewerComparator.java:182) at org.eclipse.ui.views.markers.internal.MarkerAdapter.buildAllMarkers(MarkerAdapter.java:251) at org.eclipse.ui.views.markers.internal.MarkerView.updateForContentsRefresh(MarkerView.java:544) at org.eclipse.ui.views.markers.internal.MarkerView$MarkerProcessJob.run(MarkerView.java:148) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
|
2006-04-12 04:25:25
| 1,144,830,000
|
verified fixed
|
d96aacc
| 1,145,470,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/FieldCategory.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/FieldMarkerType.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/Util.java
|
Eclipse_Platform_UI
|
3,856
| 137,356
|
Bug 137356 [Markers] marker grouping not working as expected via markerSupport
|
N20060418-0010 The Java tooling now warns when a buildpath references an execution environment for which there is no exact match in the workspace (warning support is in HEAD as of today - org.eclipse.jdt.launching and org.eclipse.jdt.debug.ui plugins). The marker created should be categorized as a buildpath problem with other JDT build path problems. To do this, I create a marker support extension as follows (in jdt.debug.ui). <extension point="org.eclipse.ui.ide.markerSupport"> <markerAttributeGrouping defaultGroupingEntry="org.eclipse.jdt.ui.category.buildpath" markerType="org.eclipse.jdt.launching.jreContainerMarker"/> </extension> My understanding is that this should group all markers of type "org.eclipse.jdt.launching.jreContainerMarker" as buildpath problems. JUI has a corresponding grouping entry: <markerGroupingEntry id="org.eclipse.jdt.ui.category.buildpath" markerGrouping="org.eclipse.jdt.ui.java_marker_category" label="%MarkerCategory.buildpath" priority="100"/> I get the following error in the log: Reference to invalid markerGroupingEntry org.eclipse.jdt.ui.category.buildpath
|
2006-04-18 15:48:30
| 1,145,390,000
|
verified fixed
|
40c10ec
| 1,145,470,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerSupportRegistry.java
|
Eclipse_Platform_UI
|
3,857
| 136,830
|
Bug 136830 Close Unrelated Projects closes needed projects
|
As I did not find a description in the help about the "Close Unrelated" menu item my guess is, that it would close all projects which are not needed for the selected one - at least this is what would make most sense for me. Under this assumption I file this bug, as in 3.2M6 "Close Unrelated" closes Projects which are needed to build the current project. How to reproduce: I start eclipse with a as unencumbered environment as possible $ mkdir /tmp/freshDirectory $ cd /tmp/freshDirectory $ HOME=/tmp/freshDirectory /usr/local/java/eclipse/eclipse -data /tmp/freshDirectory Then in eclipse enter the Workbench. Create three Java Projects named "A", "B" and "C". Select project "C" and enter Project->Properties. Select "Java Build Path" and there the "Projects" Tab. Add project "A" to the required projects list. Press "OK" to terminate the dialog. Select project "C" press the right mouse button and in the popup menu select "Close Unrelated Projects". Result: Both Projects "A" and "B" are closed. The "Problems" view shows two errors informing that the project "C" cannot be built anymore because project "A" is missed. Expected Result: Only project B, on which A does not depend, is closed. PS: If you had intended to just implement a simple "Close All Others" item like for the editor tabs, which does not care about any dependencies, then you should call it "Close All Other Projects" and not "Close Unrelated Projects". But please, don't use this as a quick fix. Implement something that is really useful.
|
2006-04-14 07:50:50
| 1,145,020,000
|
verified fixed
|
90f5ce7
| 1,145,460,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/actions/CloseUnrelatedProjectsAction.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/navigator/MainActionGroup.java
|
Eclipse_Platform_UI
|
3,858
| 137,227
|
Bug 137227 [Trim] occasionally last moved trim is moved instead of current
|
- dragged progress trim around (also moved using menu) - docked it on the left - dragged heap status - dropped head status and progress bar moved down next to it in the bottom
|
2006-04-18 11:00:36
| 1,145,370,000
|
verified fixed
|
0cd0227
| 1,145,460,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java
|
Eclipse_Platform_UI
|
3,859
| 110,169
|
Bug 110169 [Navigator] ResourceNavigator.initWorkingSetFilter should be protected visibility.
|
The above mentioned method seems mistakingly have an incorrect visibility. E.g. the method initResourceSorter is protected. I don't see why initResourceSorter is not protected.
|
2005-09-21 09:19:09
| 1,127,310,000
|
resolved fixed
|
483064e
| 1,145,390,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/navigator/ResourceNavigator.java
|
Eclipse_Platform_UI
|
3,860
| 129,841
|
Bug 129841 [DynamicUI] Calling reg.removeExtension, then reg.addContribution not showing actionSet in UI
|
I'm using the new dynamic registry APIs in 3.2 M5 (thanks!). The problem is that I'm adding a dynamic extension (reg.addContribution), then removing it using reg.removeExtension, and then not seeing it in the UI when I try to re-add the same one again. There are no exception being thrown, and the registry is indeed allowing me to re-add (reg.addContribution), but in my case, I'm adding actionSets and they never appear in the UI. I added a registry listener and it is fired when I do the re-add, but the UI does not get refreshed. Interesting, is that if open a new workbench window and I do see the updated UI! here is my addContribution code: void addExtension() { IExtensionRegistry reg = RegistryFactory.getRegistry(); IContributor contributor = ContributorFactorySimple.createContributor("test.dynamic.extensions"); String xmlsrc = "<?xml version=\"1.0\" encoding=\"UTF-8\"?><plugin><extension id=\"extensionId1\" point=\"org.eclipse.ui.actionSets\"><actionSet label=\"Sample Action Set\" visible=\"true\" id=\"test.dynamic.extensions.SampleactionSet\"><menu label=\"Dynamic Extension\" id=\"sampleMenu\"><separator name=\"sampleGroup\"></separator></menu><action label=\"Sample Extension\" icon=\"icons/blue.gif\" class=\"test.dynamic.extensions.actions.SampleAction\" tooltip=\"Sample Extension\" menubarPath=\"sampleMenu/sampleGroup\" toolbarPath=\"sampleGroup\" id=\"test.dynamic.extensions.actions.SampleAction\"></action></actionSet></extension></plugin>"; ByteArrayInputStream is = new ByteArrayInputStream(xmlsrc.getBytes()); reg.addContribution(is, contributor, false, null, null, null); } And here is my removeExtension code: void removeExtension() { IExtensionRegistry reg = RegistryFactory.getRegistry(); IExtension extension = reg.getExtension("org.eclipse.ui.actionSets", "test.dynamic.extensions.extensionId1"); reg.removeExtension(extension,null); }
|
2006-02-28 14:49:36
| 1,141,160,000
|
verified fixed
|
779af04
| 1,145,390,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/dynamicplugins/ActionSetTests.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/dynamicplugins/DynamicPluginsTestSuite.java
|
Eclipse_Platform_UI
|
3,861
| 137,148
|
Bug 137148 [Markers] Contributions to IMarker no longer show up on elements in the Problems View
| null |
2006-04-18 02:44:51
| 1,145,340,000
|
closed fixed
|
715e532
| 1,145,390,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerSelectionProviderAdapter.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/TableView.java
|
Eclipse_Platform_UI
|
3,862
| 66,292
|
Bug 66292 [Dialogs] InputDialog NPE when invoking setErrorMessage(...) too early
|
06081200 build Setting the error message this early is probably not anticipated, but it shouldn't throw an exception... public class Main { public static void main(String[] args) { Display display = new Display(); Shell shell = new Shell(display); InputDialog dialog = new InputDialog (shell, "TEST", "value", "test", null); dialog.setErrorMessage("error"); dialog.open(); shell.open(); } }
|
2004-06-09 10:02:59
| 1,086,790,000
|
verified fixed
|
b7c99aa
| 1,145,390,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/InputDialog.java
|
Eclipse_Platform_UI
|
3,863
| 137,310
|
Bug 137310 [CommonNavigator] NewActionProvider should use a different name than the group.new marker
|
The NewActionProvider should use a name like "group.new.menu" instead of "group.new" as the name of its submenu to avoid conflics with the Menu.findByPath() API.
|
2006-04-18 13:57:28
| 1,145,380,000
|
resolved fixed
|
005cb53
| 1,145,380,000
|
bundles/org.eclipse.ui.navigator.resources/src/org/eclipse/ui/internal/navigator/resources/actions/NewActionProvider.java
|
Eclipse_Platform_UI
|
3,864
| 137,199
|
Bug 137199 Generate Identifiers Test has very unstable Elapsed process
|
20060417 GenerateIdentifiersTest is all over the place on Elapsed Process but quite stable on CPU time on the slow Red Hat machine (it is fine on the others). As this does not give an accurate indication of performance currently I am going to switch it to CPU time for now until we can discover the cause of the inconsistency.
|
2006-04-18 08:38:42
| 1,145,360,000
|
resolved wontfix
|
8503cf3
| 1,145,360,000
|
tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/GenerateIdentifiersTest.java
|
Eclipse_Platform_UI
|
3,865
| 42,056
|
Bug 42056 [Dialogs] New Path Variable Dialog; lable alignment
|
The "Name" and "Location" labels should be bottom aligned with their corresponding text fields.
|
2003-08-26 20:01:07
| 1,061,940,000
|
verified fixed
|
7d44a8a
| 1,145,310,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/PathVariableDialog.java
|
Eclipse_Platform_UI
|
3,866
| 90,273
|
Bug 90273 [Dialogs] ListSelectionDialog dialog alignment
|
Deselect All should be right aligned with Cancel. Reached through pref page Java Build Path/Projects/Add
|
2005-04-05 07:28:17
| 1,112,700,000
|
verified fixed
|
32036a3
| 1,145,310,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/ListSelectionDialog.java
|
Eclipse_Platform_UI
|
3,867
| 113,370
|
Bug 113370 [Dialogs] The window title SafeRunnable displays is always English in non-English language
|
The window title SafeRunnable displays is not resourced out correctly. So the error dialog always displays the English "Error" even in non-English language. In plugins\org.eclipse.jface\src\org\eclipse\jface\util\SafeRunnable.java, In SafeRunnable#handleException(Throwable e): MessageDialog.openError(null, JFaceResources.getString ("Error"), message); //$NON-NLS-1$ It should specify "error" instead of "Error".
|
2005-10-21 12:31:18
| 1,129,910,000
|
verified fixed
|
1e57d6f
| 1,145,310,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/util/SafeRunnable.java
|
Eclipse_Platform_UI
|
3,868
| 133,416
|
Bug 133416 Open with references should only prompt if necessary
|
Build: I20060327-1200 While watching a demo at EclipseCon I noticed a user selecting "open project" on a workspace with only one project. It then prompted to ask if referenced projects should also be opened. This drew some laughter from the crowd - clearly it doesn't need to prompt if there is nothing to open. This is an easy polish item
|
2006-03-27 14:44:57
| 1,143,490,000
|
verified fixed
|
d38eb6f
| 1,145,310,000
|
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/actions/OpenResourceAction.java
|
Eclipse_Platform_UI
|
3,869
| 136,921
|
Bug 136921 [IDE] New File dialog locks for 20 seconds
|
I have fairly large workspace (many thousands files in 150+ projects). Whenever I try to create a new file, "New File" dialog stays locked for 15-20 seconds before I can start typing file name. CPU utilization is 100% during this time. Eclipse 3.2 I20060331-2000, WinXP SP2, tried with both IBM Java 1.5.0 SR1 and SUN 1.5.0_05.
|
2006-04-15 23:18:40
| 1,145,160,000
|
verified fixed
|
8e7c72c
| 1,145,310,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/ContainerSelectionGroup.java
|
Eclipse_Platform_UI
|
3,870
| 136,855
|
Bug 136855 [IDE] Deadlock caused by IDEIdleHelper and HeapStatus calls to runFinalization from UI thread
|
Plugins that have multi-threaded access to a COM server dll whose ThreadingModel=Apartment are broken in Eclipse 3.2. COM implements cross-apartment COM calls using Windows messages. Thus the IUnknown::Release() calls from a thread in the multi-threaded-apartment (MTA) to an object owned by the single-threaded-apartment (STA) actually post a message to the main thread's dispatch loop and then block waiting for a response. The IUnknown::Release() calls typically happen during finalization of the Java objects that are accessing the COM server via JNI. The IDEIdleHelper and HeapStatus calls to System.runFinalization() from the UI thread cause it to block, thus its dispatch loop (i.e. Workbench.runEventLoop) is no longer functioning when objects are finalized. Result: deadlock. The System.runFinalization() method, unlike the System.gc() method, causes the calling thread to block on a Thread.join() call: Thread [main] (Suspended) Object.wait(long) line: not available [native method] Thread.join(long) line: 1038 Thread.join() line: 1091 Finalizer$1.run() line: 164 AccessController.doPrivileged1(PrivilegedAction) line: not available [native method] AccessController.doPrivileged(PrivilegedAction) line: 287 Finalizer.forkSecondaryFinalizer(Runnable) line: 170 Finalizer.runFinalization() line: 175 Runtime.runFinalization0() line: not available [native method] Runtime.runFinalization() line: 692 System.runFinalization() line: 833 IDEIdleHelper.performGC() line: 154 IDEIdleHelper$1.run() line: 125 Display.runTimer(int) line: 3409 Display.messageProc(int, int, int, int) line: 2691 OS.DispatchMessageW(MSG) line: not available [native method] OS.DispatchMessage(MSG) line: 1879 Display.readAndDispatch() line: 2964 Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 1914 Workbench.runUI() line: 1878 Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 419 PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 143 IDEApplication.run(Object) line: 95 PlatformActivator$1.run(Object) line: 78 EclipseAppLauncher.runApplication(Object) line: 92 EclipseAppLauncher.start(Object) line: 68 EclipseStarter.run(Object) line: 376 EclipseStarter.run(String[], Runnable) line: 169 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 85 NativeMethodAccessorImpl.invoke(Method, Object, Object[]) line: 58 DelegatingMethodAccessorImpl.invoke(Method, Object, Object[]) line: 60 Method.invoke(Object, Object[]) line: 391 Main.invokeFramework(String[], URL[]) line: 336 Main.basicRun(String[]) line: 280 Main.run(String[]) line: 977 Main.main(String[]) line: 952 Here's the relevent code from the Finalizer class: private static void forkSecondaryFinalizer(final Runnable proc) { PrivilegedAction pa = new PrivilegedAction() { public Object run() { ThreadGroup tg = Thread.currentThread().getThreadGroup(); for (ThreadGroup tgn = tg; tgn != null; tg = tgn, tgn = tg.getParent()); Thread sft = new Thread(tg, proc, "Secondary finalizer"); sft.start(); try { sft.join(); } catch (InterruptedException x) { /* Ignore */ } return null; }}; AccessController.doPrivileged(pa); } The "Secondary Finalizer" thread calls the Java objects' finalize() method, which calls IUnknown::Release(), which then deadlocks. Besides this deadlock behaviour, in principle, it's a bad idea to block the UI thread while doing finalizations. Especially since there's no compelling reason to do so. Either the calls to System.runFinalization() should be removed or they should be run from a background thread. This call is entirely optional anyways. The objects will eventually be finalized (though there may be compelling reasons to force the finalizations). Probably the best solution is to make both the call to gc() and to runFinalization() in a background thread. I have confirmed this behaviour using IBM VM versions 1.4.2 and Sun VM versions 1.4.2 and 1.5.0. I am unable to reproduce this using the IBM 1.5 vm. I have written a small Java-only testcase that demonstrates the deadlock. It emulates the scenario by doing a Display.syncExec() from a Java object's finalize() method so there's no need for the Eclipse team to actually use a Java/COM bridge to see the behaviour. I'll attach the testcase to the report shortly.
|
2006-04-14 11:58:06
| 1,145,030,000
|
verified fixed
|
3e07bce
| 1,145,310,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEIdleHelper.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchMessages.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/HeapStatus.java
|
Eclipse_Platform_UI
|
3,871
| 136,870
|
Bug 136870 Progress bar in progress dialog too long
|
Progress bar in progress dialog too long (see attached image). I'm using dual head video adapter.
|
2006-04-14 13:39:07
| 1,145,040,000
|
verified fixed
|
0f2744c
| 1,145,300,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressInfoItem.java
|
Eclipse_Platform_UI
|
3,872
| 136,450
|
Bug 136450 [Progress] Widget disposed at end of update
|
[I20060412-0847] I installed EMF using the update manager. At the end, I got an error dialog, and the log contained this: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:3374) at org.eclipse.swt.SWT.error(SWT.java:3297) at org.eclipse.swt.SWT.error(SWT.java:3268) at org.eclipse.swt.widgets.Widget.error(Widget.java:432) at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:542) at org.eclipse.ui.internal.progress.ProgressMonitorFocusJobDialog$4.runAsync(ProgressMonitorFocusJobDialog.java:260) at org.eclipse.ui.internal.progress.ProgressMonitorFocusJobDialog$4.done(ProgressMonitorFocusJobDialog.java:204) at org.eclipse.ui.internal.progress.ProgressManager$JobMonitor.done(ProgressManager.java:222) at org.eclipse.update.internal.operations.BatchInstallOperation.execute(BatchInstallOperation.java:107) at org.eclipse.update.internal.ui.wizards.InstallWizard2.install(InstallWizard2.java:370) at org.eclipse.update.internal.ui.wizards.InstallWizard2.access$1(InstallWizard2.java:367) at org.eclipse.update.internal.ui.wizards.InstallWizard2$1.run(InstallWizard2.java:461) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
|
2006-04-12 16:12:55
| 1,144,870,000
|
verified fixed
|
4102116
| 1,144,880,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressMonitorFocusJobDialog.java
|
Eclipse_Platform_UI
|
3,873
| 124,655
|
Bug 124655 [Markers] can't easily sort Problems view by severity
|
I20060119-0800 In 3.1, I could easily sort the Problems view by severity by clicking on the title of the first column (which held the icons and made the severity accessible for screen readers) With recent builds, this is not possible any more, since the severity column has been integrated into the description column also when not in hierarchical mode. I'd like to have the severities column back at least in flat mode.
|
2006-01-20 10:32:12
| 1,137,770,000
|
verified fixed
|
0d709da
| 1,144,870,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/FieldMessage.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/FieldSeverity.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/FieldSeverityAndMessage.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/ProblemView.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/TableView.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/TaskView.java
|
Eclipse_Platform_UI
|
3,874
| 134,648
|
Bug 134648 [Intro] IDEWorkbenchWindowAdvisor should not call Bundle#start
|
IDEWorkbenchWindowAdvisor#openWelcomeEditors calls Bundle#start explicitly. This causes the bundle to be started eagerly the next time Eclipse comes up. We should change it so that this does not happen. Tom, what is the recommended way of dealing with this? The reason for starting the bundle at that time (before showing the welcome editor) is to give it a chance to perform first-time initialization tasks. Should we use deprecated methods from core.compatibility? Just for context: Welcome editors are deprecated and have been replaced by the "intro" support for some time now. (I believe intro was introduced in 3.0).
|
2006-04-03 23:00:48
| 1,144,120,000
|
verified fixed
|
4a35a41
| 1,144,870,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchWindowAdvisor.java
|
Eclipse_Platform_UI
|
3,875
| 135,058
|
Bug 135058 new error message popup in wizards is too "distracting"
|
Eclipse 3.2M6 Although it might look cool, the new error popup in wizards is very distracting. Here's the use case: Create a new Java package based on an existing package name. For example, create a new package called "org.eclipse.ui.editors.text.test". Assuming "org.eclipse.ui.editors.text" already exists. As you type, for each "." or package segment that already exists, the popup will go up and down, up and down. It is just too distracting.
|
2006-04-05 11:47:13
| 1,144,250,000
|
resolved fixed
|
6df122c
| 1,144,860,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/TitleAreaDialog.java bundles/org.eclipse.jface/src/org/eclipse/jface/preference/PreferenceMessageArea.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchControlAnimator.java
|
Eclipse_Platform_UI
|
3,876
| 136,373
|
Bug 136373 [EFS] Can't browse for files when creating linked resources
|
Build id: I20060412-0847 File > New > File Click Advanced Click Browse. Nothing happens, and an error appears in the log. Same for the new folder dialog. java.lang.NullPointerException at org.eclipse.ui.internal.ide.dialogs.CreateLinkedResourceGroup.handleLinkTargetBrowseButtonPressed(CreateLinkedResourceGroup.java:376) at org.eclipse.ui.internal.ide.dialogs.CreateLinkedResourceGroup.access$13(CreateLinkedResourceGroup.java:372) at org.eclipse.ui.internal.ide.dialogs.CreateLinkedResourceGroup$3.widgetSelected(CreateLinkedResourceGroup.java:260) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
|
2006-04-12 12:35:11
| 1,144,860,000
|
verified fixed
|
59093ab
| 1,144,860,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/CreateLinkedResourceGroup.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ProjectContentsLocationArea.java
|
Eclipse_Platform_UI
|
3,877
| 134,328
|
Bug 134328 [Wizards] Two error messages interact in two different wizards
|
There is a required field in wizard A, so there is an error message shown in this wizard A like "*** can't be empty"; to enter this field, there is a "New" button next to this field, so click New button to pop up another wizard B, enter an invalid value in wizard B, it will display an error message in wizard B, then the error message can be disappeared after the correct valued entered, click Finish button in wizard B. Now it goes back to wizard A, the value which entered in wizard B is displayed in wizard A, so the error message "*** can't be empty" should be disapperared from wizard A, but the error message is still there. The problem may caused by org.eclipse.jface.util.Policy.java, there is a static field animator, which shares by others.
|
2006-03-31 16:44:12
| 1,143,840,000
|
resolved fixed
|
7128f13
| 1,144,860,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/AnimatorFactory.java bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/ControlAnimator.java bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/ImageAndMessageArea.java bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/TitleAreaDialog.java bundles/org.eclipse.jface/src/org/eclipse/jface/preference/PreferenceMessageArea.java bundles/org.eclipse.jface/src/org/eclipse/jface/util/Policy.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/JFaceUtil.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchAnimatorFactory.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchControlAnimator.java
|
Eclipse_Platform_UI
|
3,878
| 98,265
|
Bug 98265 Strings in Combo drop down list are truncated
|
Long strings writtenn in Japanese/Chinese are truncated in a dropdown list of a ComboBox. The list is not wide enough. The combo box's parent has GridLayout and the combobox has GridData with HORIZONTAL_FILL.
|
2005-06-03 08:41:15
| 1,117,800,000
|
resolved fixed
|
599b687
| 1,144,860,000
|
tests/org.eclipse.ui.tests.performance/src/org/eclipse/jface/tests/performance/ComboViewerRefreshTest.java
|
Eclipse_Platform_UI
|
3,879
| 136,178
|
Bug 136178 [Markers] Quick filter selection is not updating the view
|
20050411 Selecting and deselecting filters from the drop down is not changing the filters until you open the dialog
|
2006-04-11 15:40:03
| 1,144,780,000
|
verified fixed
|
a777413
| 1,144,850,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/FilterEnablementAction.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java
|
Eclipse_Platform_UI
|
3,880
| 133,536
|
Bug 133536 [Field Assist] - PageUp and PageDown in ContentAssistFields change combo contents
|
I20060328-0010 To reproduce: - open Find/Replace dialog - find some text, such that the MRU combo for the Find field contains something - enable regex - invoke content assist in Find field => pressing PageUp or PageDown changes the Find field text as welll => pressing Home or End moves the caret in the Find field as well All these keys should only move the selection in the popup list.
|
2006-03-28 10:04:13
| 1,143,560,000
|
verified fixed
|
1a96db3
| 1,144,820,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
3,881
| 133,599
|
Bug 133599 [FieldAssist] Left and right arrow keys should work with open proposals list
|
I20060328-0010, worked in M5 In the Find/Replace dialog, enable regex, then type something into the Find field and invoke content assist. Pressing the left or right arrow key now closes the proposals popup. The list should not be closed, but the caret should be moved and the proposals should be recalculated for the new caret position.
|
2006-03-28 11:53:36
| 1,143,560,000
|
verified fixed
|
7ccc2aa
| 1,144,820,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
3,882
| 132,798
|
Bug 132798 [Field Assist] - Pressing Backspace at offset 0 should not reload field assist popup
|
N20060322-0010. After migrating the Find/Replace dialog to the new field assist support I found the following blooper: pressing the Backspace key at offset 0 reloads the field assist popup. Test Case: 1. in a text editor press Ctrl+F 2. enable regex search 3. in the Find filed press Ctrl+Space 4. continuously press Backspace ==> each time the proposal list is reloaded.
|
2006-03-22 03:20:06
| 1,143,020,000
|
verified fixed
|
7b2fb7c
| 1,144,810,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
3,883
| 133,620
|
Bug 133620 [FieldAssist] auto activation of proposal popup should be canceled on keystroke
|
I20060328-0010 Auto activation of the proposal popup should be canceled on keystroke. Steps: - open Find/Replace dialog, activate regex - type "\rrrrrrr" as fast as possible => after a few "r"s, the proposal popup appears at the last "r" inserted This is not the intent of the "auto activation with delay" feature. Auto activation is intended to help the user if he stops typing and starts to think about possible completions. It should be triggered when the user types "\" and then waits a while, but the popup should not appear when the user continues typing after the trigger character.
|
2006-03-28 12:43:28
| 1,143,570,000
|
verified fixed
|
e89dcbf
| 1,144,810,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
3,884
| 133,615
|
Bug 133615 [FieldAssist] ContentAssistField: proposal popup and additional info should have different bg color
|
I20060328-0010 ContentAssistField's proposal popup and additional info should have different background colors. They currently have the same yellow background (I guess the system info bg color, but the info color is not really suitable for the list). The Java editor already lets the user configure the proposal list colors (Preferences > Java > Editor). I think the colors should be the same in the Java editor and in the editor's Find/Replace dialog. 2 solutions: a) use the system default color for the proposals list (white on WinXP) b) Platform/UI adds the colors for the proposal popup to the Colors and Fonts preferences page and offers API to retrieve the default colors
|
2006-03-28 12:23:41
| 1,143,570,000
|
verified fixed
|
09f1e5b
| 1,144,810,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
3,885
| 135,641
|
Bug 135641 [CommonNavigator] NPE when closing common navigator
|
java.lang.NullPointerException at org.eclipse.ui.navigator.CommonNavigator.getSaveables(CommonNavigator.java:552) at org.eclipse.ui.internal.SaveablesList.getSaveables(SaveablesList.java:504) at org.eclipse.ui.internal.SaveablesList.postClose(SaveablesList.java:477) at org.eclipse.ui.internal.WorkbenchPage.hideView(WorkbenchPage.java:2152) at org.eclipse.ui.internal.ViewPane.doHide(ViewPane.java:213) at org.eclipse.ui.internal.PartStack.close(PartStack.java:498) at org.eclipse.ui.internal.PartStack.close(PartStack.java:481) at org.eclipse.ui.internal.PartStack$1.close(PartStack.java:105) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:81) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:267) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:276) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.access$1(DefaultTabFolder.java:1) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder$1.closeButtonPressed(DefaultTabFolder.java:67) at org.eclipse.ui.internal.presentations.PaneFolder.notifyCloseListeners(PaneFolder.java:580) at org.eclipse.ui.internal.presentations.PaneFolder$3.close(PaneFolder.java:187) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2107) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:292) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:925) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3346) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2966) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-04-07 15:35:53
| 1,144,440,000
|
verified fixed
|
16e06a1
| 1,144,790,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/ISaveablesLifecycleListener.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/SaveablesList.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchPage.java
|
Eclipse_Platform_UI
|
3,886
| 127,519
|
Bug 127519 [Markers] Disabling all filters gives empty list
|
If you disable (uncheck) the 'Default' filter then the result seems to be that -everything- gets filtered. This seems most unintuitive...I'd think that if I don't have any filters enabled then I should see an 'unfiltered' list.
|
2006-02-13 14:33:19
| 1,139,860,000
|
verified fixed
|
5dd6e45
| 1,144,780,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerAdapter.java
|
Eclipse_Platform_UI
|
3,887
| 132,427
|
Bug 132427 [Markers] TaskPropertiesDialog problems
| null |
2006-03-17 21:02:11
| 1,142,650,000
|
verified fixed
|
c080872
| 1,144,780,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/tasklist/TaskPropertiesDialog.java
|
Eclipse_Platform_UI
|
3,888
| 73,612
|
Bug 73612 [Markers] "Open All" does not work with multi-select in the bookmarks view
| null |
2004-09-09 16:27:03
| 1,094,760,000
|
verified fixed
|
15d34be
| 1,144,780,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/ActionOpenMarker.java
|
Eclipse_Platform_UI
|
3,889
| 136,101
|
Bug 136101 [Markers] ProblemsView constantly busy when empty
|
20060412 The problems view is constantly busy when there are no entries - the tab goes italic all of the time.
|
2006-04-11 09:12:57
| 1,144,760,000
|
verified fixed
|
58c7b43
| 1,144,760,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerAdapter.java
|
Eclipse_Platform_UI
|
3,890
| 134,238
|
Bug 134238 [Undo] TriggeredOperations should close open operation on RuntimeExceptions
| null |
2006-03-31 04:35:42
| 1,143,800,000
|
verified fixed
|
7ccff0b
| 1,144,700,000
|
bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/operations/TriggeredOperations.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/operations/OperationsAPITest.java
|
Eclipse_Platform_UI
|
3,891
| 26,823
|
Bug 26823 [Markers] cannot reorder columns in task list
|
-cannot reorder columns in task list -should allow for custom columns content (line number only, line in method, in file) -should allow to wrap text in a higher row for long error message: we keep adjusting the columns width all the time...
|
2002-11-20 18:29:29
| 1,037,830,000
|
verified fixed
|
bcb4656
| 1,144,700,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/TableView.java
|
Eclipse_Platform_UI
|
3,892
| 135,586
|
Bug 135586 [Markers] ClassCastException invoking help from ProblemsView
|
M6 If you have help open and then hit F1 in the problems view you get the following exception !ENTRY org.eclipse.ui.workbench 4 2 2006-04-07 11:42:25.500 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". !STACK 0 java.lang.ClassCastException at org.eclipse.ui.views.markers.internal.MarkerView$ContextProvider.getContext(MarkerView.java:404) at org.eclipse.help.ui.internal.views.ContextHelpPart.handleActivation(ContextHelpPart.java:247) at org.eclipse.help.ui.internal.views.ContextHelpPart.setFormInput(ContextHelpPart.java:522) at org.eclipse.ui.forms.ManagedForm.setInput(ManagedForm.java:236) at org.eclipse.help.ui.internal.views.RelatedTopicsPart.setFormInput(RelatedTopicsPart.java:165) at org.eclipse.ui.forms.ManagedForm.setInput(ManagedForm.java:236) at org.eclipse.help.ui.internal.views.ReusableHelpPart.update(ReusableHelpPart.java:1060) at org.eclipse.help.ui.internal.views.HelpView.handlePartActivation(HelpView.java:129) at org.eclipse.help.ui.internal.views.HelpView.partActivated(HelpView.java:216) at org.eclipse.ui.internal.PartListenerList2$1.run(PartListenerList2.java:68) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:816) at org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:53) at org.eclipse.ui.internal.PartListenerList2.firePartActivated(PartListenerList2.java:66) at org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:77) at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:171) at org.eclipse.ui.internal.WWinPartService.updateActivePart(WWinPartService.java:124) at org.eclipse.ui.internal.WWinPartService.access$0(WWinPartService.java:115) at org.eclipse.ui.internal.WWinPartService$1.partDeactivated(WWinPartService.java:48) at org.eclipse.ui.internal.PartListenerList2$4.run(PartListenerList2.java:113) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:816) at org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:53) at org.eclipse.ui.internal.PartListenerList2.firePartDeactivated(PartListenerList2.java:111) at org.eclipse.ui.internal.PartService.firePartDeactivated(PartService.java:116) at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:165) at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:56) at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:126) at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3139) at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:2692) at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:256) at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:220) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:925) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:949) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:930) at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1199) at org.eclipse.swt.widgets.Shell.WM_MOUSEACTIVATE(Shell.java:1878) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3287) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1539) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1634) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1915) at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1915) at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1915) at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1915) at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1915) at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1163) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:4589) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:1839) at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1252) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:4591) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4023) at org.eclipse.swt.internal.win32.OS.PeekMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.PeekMessage(OS.java:2384) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2961) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-04-07 11:55:21
| 1,144,430,000
|
verified fixed
|
e829887
| 1,144,700,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java
|
Eclipse_Platform_UI
|
3,893
| 129,215
|
Bug 129215 performance tests that run too fast (< 100 ms)
|
The test org.eclipse.ui.tests.performance.EditorSwitchTest#testEditorSwitch:perf_basic,perf_outline() is running in less than 100 ms on most of the test machines. That's too fast. Need to increase the length of time for which this test runs. We may want to call BasicPerformanceTest.exercise(Runnable, int, int, int) instead of BasicPerformanceTest.exercise(Runnable) from the EditorSwitchTest instead.
|
2006-02-23 14:53:43
| 1,140,720,000
|
resolved fixed
|
741d52f
| 1,144,700,000
|
tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/OpenCloseViewTest.java
|
Eclipse_Platform_UI
|
3,894
| 135,284
|
Bug 135284 [Viewers] API: need to add methods to StructuredViewer to support ViewerComparator
| null |
2006-04-06 10:56:58
| 1,144,340,000
|
verified fixed
|
0208d56
| 1,144,690,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StructuredViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerSorter.java
|
Eclipse_Platform_UI
|
3,895
| 135,173
|
Bug 135173 [Markers] ArrayIndexOutOfBoundsException from Problems view
|
Eclipse 3.2 M6 The following exception occurred while the Problems view was updating during a build. This build was started by selecting "Clean..." on a group of projects. org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ArrayIndexOutOfBoundsException: 277) at org.eclipse.swt.SWT.error(SWT.java:3374) at org.eclipse.swt.SWT.error(SWT.java:3297) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3323) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2969) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) Caused by: java.lang.ArrayIndexOutOfBoundsException: 277 at org.eclipse.ui.views.markers.internal.MarkerList.getMarker(MarkerList.java:322) at org.eclipse.ui.views.markers.internal.MarkerAdapter$MarkerCategory.getConcreteRepresentative(MarkerAdapter.java:162) at org.eclipse.ui.views.markers.internal.FieldMarkerGroup.compare(FieldMarkerGroup.java:259) at org.eclipse.ui.views.markers.internal.CategorySorter.compare(CategorySorter.java:58) at org.eclipse.ui.views.markers.internal.CategorySorter.compare(CategorySorter.java:72) at org.eclipse.jface.viewers.ViewerComparator$1.compare(ViewerComparator.java:184) at java.util.Arrays.mergeSort(Arrays.java:1284) at java.util.Arrays.sort(Arrays.java:1223) at org.eclipse.jface.viewers.ViewerComparator.sort(ViewerComparator.java:182) at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:549) at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2278) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1602) at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:932) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1578) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1533) at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1386) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1294) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1384) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1341) at org.eclipse.ui.views.markers.internal.MarkerView$UpdateJob.runInUIThread(MarkerView.java:184) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) ... 20 more
|
2006-04-05 18:48:59
| 1,144,280,000
|
verified fixed
|
463fb04
| 1,144,690,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerAdapter.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java
|
Eclipse_Platform_UI
|
3,896
| 135,648
|
Bug 135648 [Trim] Need API to lock all trim
|
One of the standard RCP scenarios identified by Nick was the ability for an RCP app to 'lock' the trim. For now he thinks that simply having the capability to have -all- the trim locked or not would suffice. The proposed change would add a new preference in IWorkbenchWindowConstants (LOCK_TRIM="Lock Trim"), 'false' by default. This does -not- need to be a dynamic preference; there would be no GUI to change it so it wouldn't require pref change listeners... Then I'd modify the TrimLayout to respect the value by querying it on construction.
|
2006-04-07 16:16:18
| 1,144,440,000
|
verified fixed
|
40b5e9c
| 1,144,680,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IWorkbenchPreferenceConstants.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/layout/TrimLayout.java
|
Eclipse_Platform_UI
|
3,897
| 134,044
|
Bug 134044 Required field inconsistency on New File wizard
|
I20060330-0010. See attached picture: there's an error on top saying the link location field is required but in contrast to the other fields it is not indicated as such.
|
2006-03-30 04:59:19
| 1,143,710,000
|
verified fixed
|
2504ad7
| 1,144,520,000
|
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/dialogs/NewFolderDialog.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/CreateLinkedResourceGroup.java
|
Eclipse_Platform_UI
|
3,898
| 77,336
|
Bug 77336 [Markers] [Dialogs] TableSortDialog does not use dialog font
|
Problems view toolbar; Sorting...
|
2004-10-29 20:30:57
| 1,099,100,000
|
verified fixed
|
6f61a67
| 1,144,440,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/TableSortDialog.java
|
Eclipse_Platform_UI
|
3,899
| 133,214
|
Bug 133214 [Field Assist] - required field color hard to see
| null |
2006-03-24 17:21:54
| 1,143,240,000
|
verified fixed
|
b988fe0
| 1,144,440,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/FieldAssistColors.java
|
Eclipse_Platform_UI
|
3,900
| 104,496
|
Bug 104496 [BIDI] Need to support Hebrew language code change to "he" from "iw"
| null |
2005-07-20 10:36:25
| 1,121,870,000
|
verified fixed
|
d704c4d
| 1,144,440,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchPlugin.java
|
Eclipse_Platform_UI
|
3,901
| 43,523
|
Bug 43523 [MPE] getAdapter(IEditorStatusLine.class) not working for MultipageEditor
|
I20030923 As an example: use FindReplace dialog on Source page of PDE's plug-in editor and observe: status is written in dialog but not in the workbench window's status line.
|
2003-09-23 13:32:03
| 1,064,340,000
|
verified fixed
|
77f776e
| 1,144,410,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/part/MultiPageEditorPart.java
|
Eclipse_Platform_UI
|
3,902
| 134,750
|
Bug 134750 [DataBinding] TextObservableValue throws NPE on change if the intial model value is null
|
When binding a Text to a model attribute that has an intial value of null ObservableTextValue throws a NPE when updating the view. In "updateListener" it assumes that oldValue != null. I'll attach a JUnit that throws the Exception.
|
2006-04-04 10:07:29
| 1,144,160,000
|
resolved fixed
|
883495e
| 1,144,360,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/internal/swt/TextObservableValue.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/scenarios/BindingScenariosTestSuite.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/scenarios/NPETestScenario.java
|
Eclipse_Platform_UI
|
3,903
| 127,629
|
Bug 127629 [Markers] problems view: keep selection stable
|
I20050214-0010 1. Select a grouping (e.g. Java problem type) and select a marker inside 2. Switch to another grouping Selection is gone. Same when - changing filter - a build adds new marker (in a different file)
|
2006-02-14 04:33:27
| 1,139,910,000
|
verified fixed
|
36090a3
| 1,144,360,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/ProblemView.java
|
Eclipse_Platform_UI
|
3,904
| 134,879
|
Bug 134879 [DataBinding] Provide toString implementations for implementations of IDiff
|
It can be beneficial for a developer when attempting to debug or learn Data Binding to see what the diffs are that are being sent back and forth through the pipeline. I'm attaching implementations of toString() for: * ValueDiff * SetDiff * ListDiff * ListDiffEntry I didn't create an implementation for MappingDiff because I'm not positive of its usage and what would be an appropriate toString implementation. When I figure that out I'll attach it as well. I'm also attaching a TestCase that asserts that NPEs aren't thrown when any of the properties of these classes are null.
|
2006-04-04 17:12:04
| 1,144,190,000
|
resolved fixed
|
ff44d89
| 1,144,360,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/list/ListDiff.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/list/ListDiffEntry.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/set/SetDiff.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/value/ValueDiff.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/BindingTestSuite.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/IDiffsTest.java
|
Eclipse_Platform_UI
|
3,905
| 135,023
|
Bug 135023 [Trim] Contributed trim 'fill' failures can prevent Workbench from opening
|
I just changed some code for a piece of contributed trim (accidentally intriducing a CCE). A subseqeuent to bring up the WB resulted 'silent' failure with no error display or log but also no workbench...
|
2006-04-05 10:18:46
| 1,144,250,000
|
verified fixed
|
3d100ab
| 1,144,350,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchMessages.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/TrimBarManager.java
|
Eclipse_Platform_UI
|
3,906
| 133,867
|
Bug 133867 [EFS] Project wizard browse button not connected to file system contributor
|
Build: I20060328-0010 1) Install org.eclipse.ui.examples.filesystem 2) Open the new project wizard 3) Uncheck the default location checkbox 4) Select "In Memory" file system 5) Click "Browse" I would expect FileSystemContributor.browseFileSystem(String,Shell) to be called, but it isn't. Not matter what file system I select, clicking browse just opens a standard local file system dialog. This makes it impossible for another file system to plugin in a different file system browse dialog.
|
2006-03-29 11:00:41
| 1,143,650,000
|
verified fixed
|
e816513
| 1,144,340,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/CreateLinkedResourceGroup.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ProjectContentsLocationArea.java
|
Eclipse_Platform_UI
|
3,907
| 123,409
|
Bug 123409 [FastViews][DnD] Fastview bar is vertically oriented in status bar after switch from 3.1.2 to 3.2
|
- start M20060109-1200 (3.1.2 candidate) with a new workspace - move the Javadoc and Declaration views to the fast view bar - move the fast view bar to the left - shut down and start I20060110-1026 with the same workspace => The fast view bar is now vertically oriented, but not on the left of the workbench window as expected, but instead in the status bar, making it very high. I found no way to move the fast view bar around or change its orientation.
|
2006-01-11 06:39:45
| 1,136,980,000
|
verified fixed
|
ba4a25a
| 1,144,340,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java
|
Eclipse_Platform_UI
|
3,908
| 135,088
|
Bug 135088 [JFace] AbstractResourceManager.find() returns a RefCount instead of the created resource
|
M6 If you attempt to call find on an AbstractResourceManager subclass you will get back a RefCount object instead of the resource bound to the desired descriptor. RefCount is a private class that is unusable to clients of this API. This should be addressed for 3.2 to address the intention of the method description.
|
2006-04-05 13:31:16
| 1,144,260,000
|
verified fixed
|
bb04ff7
| 1,144,290,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/resource/AbstractResourceManager.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/images/ResourceManagerTest.java
|
Eclipse_Platform_UI
|
3,909
| 108,102
|
Bug 108102 [Viewers] Project expands in wrong working set
|
I am using "Show->Working Sets" in the package explorer. Some of the working sets contain the same project: Working Set-1: - Project-A - Project-B - Project-C Working Set-2: - Project-B - Project-C - Project-D If I now double-click "Working Set-1.Project-B" "Project-B" in working set "Working Set-2" will be expanded. If the working set "Working Set-2" itself is not expanded it will seem as if nothing happens, but after expanding "Working Set-2" one can see the changed state of the project. Double-clicking "Working Set-2.Project-B" works as expected.
|
2005-08-26 07:43:21
| 1,125,060,000
|
resolved fixed
|
607cfd9
| 1,144,260,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractTreeViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StructuredViewer.java
|
Eclipse_Platform_UI
|
3,910
| 43,581
|
Bug 43581 [MPE] MultiPageEditorPart has class cast error in pageChange
|
I have attached a GEF GraphicalEditor to a tab in a MultipageEditor (as generated by EMF). import org.eclipse.gef.ui.parts.GraphicalEditor; protected GraphicalEditor gefEditor; ... addPage(gefEditor, gefEditor.getEditorInput()); ... When I select the tab with the GraphicalEditor I get the a class cast exception in the following line in MultiPageEditorPart. ((MultiPageSelectionProvider) getSite().getSelectionProvider()).fireSelectionChanged(event); getSelectionProvider is expected to return an ISelectionProvider, so the cast ought to be subject to an instanceof first IMO. Or there should be some way of preventing non-proficient eclipse programmers attaching something that is not an MultiPageSelectionProvider. Perhaps I am just missing out on something, configuring the right selection provider for the gef editor, perhaps, but I cannot see any setSelectionProvider() method on the GraphicalEditor. The stacktrace is here: !ENTRY org.eclipse.ui 4 4 sep 24, 2003 16:28:52.703 !MESSAGE Unhandled exception caught in event loop. !ENTRY org.eclipse.ui 4 0 sep 24, 2003 16:28:52.718 !MESSAGE java.lang.ClassCastException !STACK 0 java.lang.ClassCastException at org.eclipse.ui.part.MultiPageEditorPart.pageChange(MultiPageEditorPart.java:414) at com.nds.core.epg.designer.model.presentation.ModelEditor.pageChange(ModelEditor.java:1005) at org.eclipse.ui.part.MultiPageEditorPart$2.widgetSelected(MultiPageEditorPart.java:133) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:848) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:872) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:857) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:665) at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:1742) at org.eclipse.swt.custom.CTabFolder.onMouseDown(CTabFolder.java:1930) at org.eclipse.swt.custom.CTabFolder.access$4(CTabFolder.java:1922) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:201) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:848) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2188) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1878) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1680) at org.eclipse.ui.internal.Workbench.run(Workbench.java:1663) at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.basicRun(Main.java:291) at org.eclipse.core.launcher.Main.run(Main.java:747) at org.eclipse.core.launcher.Main.main(Main.java:583)
|
2003-09-24 11:20:49
| 1,064,420,000
|
verified fixed
|
41fa525
| 1,144,250,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/part/MultiPageEditorPart.java
|
Eclipse_Platform_UI
|
3,911
| 134,266
|
Bug 134266 [Wizard] Page description not set if page message already set
|
Since page messages such as errors and warnings used to be displayed in the same widget as the page description, code was put in place in WizardDialog#updateDescriptionMessage() to avoid setting the page description if there was already a message. As of 3.2 M6 there is a separate widget for displaying error and warning messages and so the page description should always be set.
|
2006-03-31 10:23:55
| 1,143,820,000
|
verified fixed
|
afee238
| 1,144,250,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/wizard/WizardDialog.java
|
Eclipse_Platform_UI
|
3,912
| 130,338
|
Bug 130338 Eclipse Core Expressions Property Testers not loaded on demand
|
The Eclipse Core Expressions framework provides a nice way to declare an enablement clause for arbitrary extension points. However, the property testers used by this framework are not loaded when referenced in an expression. Instead, clients that take advantage of the core expressions mechanism must either (1) wait for the property tester plugin to load by chance or (2) insert a hack to force the plugin that declares a necessary property tester to load, or worse yet (3) make the plugin that declares the property tester an early start up plugin (I hope you shuddered when you read that like I did when I typed it). So, I submit that the framwork, while trying to be performance-friendly has sacrificed the usability and consumeability of this highly useful framework by not declaring some quality, efficient mechanism to force the property tester to be available when needed. I'm open to suggestions on how this issue should be fixed, but I would suggest at a minimum that the propertyTester extension point declare a "forceLoad" attribute (which I'm happy to let default to false) so that property testers can decide when they are really important or optional. Granted, many people will probably want to set this flag to true; but better they do it this way rather than make their property tester plugins early startup plugins because they could find no other solution.
|
2006-03-03 11:28:29
| 1,141,400,000
|
resolved fixed
|
704d7cb
| 1,144,250,000
|
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/actions/CommonActionProviderDescriptor.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/dnd/CommonDropAdapterDescriptor.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/LinkHelperDescriptor.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorContentDescriptor.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/sorters/CommonSorterDescriptor.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/wizards/CommonWizardDescriptor.java
|
Eclipse_Platform_UI
|
3,913
| 122,819
|
Bug 122819 [Metadata] Some UI classes use CPL
|
Several UI classes have CPL rather than EPL in their copyright notices. These should be fixed to indicate the proper license. I will attach a file because it is easier to read. CC Nick: the JAOO RCP adventure builder example in platform-ui-home is also all copyright with CPL - I don't know if that was intentional or not. If not, you probably need to update your template preferences to use EPL.
|
2006-01-05 17:18:55
| 1,136,500,000
|
verified fixed
|
b517de2
| 1,144,170,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/resource/DerivedImageDescriptor.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/ResourceUtil.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorReference.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ErrorEditorPart.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ErrorViewPart.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PartList.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PartService.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PartTester.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ViewReference.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchPagePartList.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/AdaptableForwarder.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/CustomizePerspectiveDialog.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/misc/UIListenerLogging.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/util/Descriptors.java
|
Eclipse_Platform_UI
|
3,914
| 134,588
|
Bug 134588 [Markers] Problems view not indicating pending update after deletion
|
3.2 M6 The problems view updates itself in the background. During the last weeks I was confused quite a few times due to a log delay till the problems view responded to changes in the workspace. However, I was never able to track this down. Today I made another observation, which I believe is worthwhile to report here. I had a Java source file in my workspace with 3 compile errors (fatal problems, grouping is on). I simply deleted the file and then was confused again because the problems view still showed the problems. I remembered that I saw this behavior in the past. Thus I decided to simply wait and watch this time. In the past I often tried a "clean" to force a rebuild. I waited approximately 20 seconds till the problems were removed from the view. The interesting thing is that the view title did not indicate any ongoing activity. Usually it's cursive to indicate ongoing update work. There was no activity on my laptop during the 20 seconds. Thus, I don't know what caused the delay. I also noted, the no build was caused by the deletion of the compilation unit (at least the progress monitor didn't show an ongoing build and there was no hard disk activity). I think it's hard to track this down but it does cause quite a bit confusion to an end user.
|
2006-04-03 15:32:36
| 1,144,090,000
|
verified fixed
|
e687a35
| 1,144,160,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/ProblemView.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/TableView.java
|
Eclipse_Platform_UI
|
3,915
| 134,401
|
Bug 134401 Bug in JFace Window JavaDoc
|
Eclipse: 3.2 M5 Class: org.eclipse.jface.window.Window In text below "getContents()" should be used instead of "getControl()". /** * Creates and returns this window's contents. Subclasses may attach any * number of children to the parent. As a convenience, the return value of * this method will be remembered and returned by subsequent calls to * getControl(). Subclasses may modify the parent's layout if they overload * getLayout() to return null. * * <p> * It is common practise to create and return a single composite that * contains the entire window contents. * </p> * * <p> * The default implementation of this framework method creates an instance * of <code>Composite</code>. Subclasses may override. * </p> * * @param parent * the parent composite for the controls in this window. The type * of layout used is determined by getLayout() * * @return the control that will be returned by subsequent calls to * getControl() */ protected Control createContents(Composite parent) { // by default, just create a composite return new Composite(parent, SWT.NONE); }
|
2006-04-02 01:25:05
| 1,143,960,000
|
resolved fixed
|
c95b731
| 1,144,080,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/window/Window.java
|
Eclipse_Platform_UI
|
3,916
| 126,155
|
Bug 126155 [Markers] Issues of multi quick fix dialog
|
I20060131-1200 Here are a few things to improve in the multi quickfix dialog (problems view -> Quick fix on a missing SUID problem) - Description of the dialog ("Select the fix for...") should put the problem message in quotes to make it more readable. - What about an icon in the title area? We have not other dialogs like this which do not show an icon in the title area. - Either use "resolution" or "fix" as term for the offered proposal. I'd suggest to use fix (e.g. in "Select a resolution:") - Perhaps "Add Matching Problems" is not that clear. It is more something like searching for similar problems which can be fixed the same way, e.g. "Find similar problems" - The progress message which appears when clicking on "Add Matching Problems" ("Calculating Possible Resolutions working on...") should better rephrased to "Searching for similar problems..." - After having clicked on "Add Matching Problems", this button gets disabled. As soon as the selection is changed, it is reenabled again. I suggest to enable this button once for a specific fix to let the user find similar problems, and cache the results.
|
2006-02-02 04:37:41
| 1,138,870,000
|
verified fixed
|
a48c0e3
| 1,144,080,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerResolutionDialog.java
|
Eclipse_Platform_UI
|
3,917
| 115,061
|
Bug 115061 [Progress] Progress entries should have a smaller minimum size
|
M3 Currently the minimum size for progress entries is quite large - we should determine which constraint is causing this and reduce the size.
|
2005-11-04 07:45:21
| 1,131,110,000
|
verified fixed
|
202c74e
| 1,144,070,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressInfoItem.java
|
Eclipse_Platform_UI
|
3,918
| 133,896
|
Bug 133896 [DataBinding] TableModelDescription Needs Enhancement
|
In moving to latest JFace data binding code on HEAD, I found two issues with the refactored table and collection binding support. 1. TableModelDescription does not support binding to an existing IObservableList. The attached patch address this by adding an alterative contructor taking an IObservableList and a Array of Strings for columns. The patch also includes changes to the ViewersBindingFactory to use this supplied IObservableList instead of attempting to create one from the Property value on the TableModelDescription. 2. Binding a viewer to a collection of objects used to default to using each object's toString() method to determine the row label. The implementation on HEAD wants to bind a IObservableCollectionWithLabels (the observable for viewers) to a IObservableMultiMappingWithDomain. Attempting to bind to a IObservableList generates an exception. One solution is to wrap the IObservableList in a TableModelDescription which will then generate a IObservableMultiMappingWithDomain when createObservable() is called. This is more verbose than I think the solution should be. Attached is a patch which defaultly creates a JavaBeanObservableMultiMapping from the IObservableList and specifies one column based on the toString() method of its objects. This reimplements the previous behavior when binding collections to viewers with one column.
|
2006-03-29 12:48:58
| 1,143,650,000
|
resolved fixed
|
c0419f2
| 1,143,670,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/beans/BeanObservableFactory.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/description/TableModelDescription.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/viewers/ViewersBindingFactory.java
|
Eclipse_Platform_UI
|
3,919
| 133,935
|
Bug 133935 [CommonNavigator] Export menu creation issue
|
In the PortingActionProvider there is a typo. It checks to see the size of the importwizardactiongroup list rather than the export list. This blocks export menus from showing unless import menus exist. See below: private void addExportMenu(IMenuManager aMenu) { exportWizardActionGroup.setContext(getContext()); if (importWizardActionGroup.getWizardActionIds().length == 0) { aMenu.appendToGroup(ICommonMenuConstants.GROUP_PORT, exportAction); return; } IMenuManager submenu = new MenuManager( WorkbenchNavigatorMessages.PortingActionProvider_ExportResourcesMenu_label, COMMON_NAVIGATOR_EXPORT_MENU); exportWizardActionGroup.fillContextMenu(submenu); submenu.add(new Separator(ICommonMenuConstants.GROUP_ADDITIONS)); submenu.add(new Separator()); submenu.add(exportAction); aMenu.appendToGroup(ICommonMenuConstants.GROUP_PORT, submenu); }
|
2006-03-29 16:55:27
| 1,143,670,000
|
closed fixed
|
b494e18
| 1,143,670,000
|
bundles/org.eclipse.ui.navigator.resources/src/org/eclipse/ui/internal/navigator/resources/actions/PortingActionProvider.java
|
Eclipse_Platform_UI
|
3,920
| 133,533
|
Bug 133533 [JFace] Animated warning in new class wizard moves away but never reveals message text
|
I20060328-0010, worked fine in 3.2M5 - import a plugin as binary - open a class file and make sure the name of the type declaration is selected - open New Java Class wizard => The (valid) warning message moves through the message area from bottom to top and then leaves the area blank as long as no error is shown (e.g. add a character to the name -> still no warning).
|
2006-03-28 09:46:32
| 1,143,560,000
|
verified fixed
|
7870d39
| 1,143,660,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchControlAnimator.java
|
Eclipse_Platform_UI
|
3,921
| 133,847
|
Bug 133847 Javadoc bug in StackPresentation.setState(int)
|
StackPresentation.setState(int) references "IPresentationSite.STATE_*" and "IPresentationSite") a number of times. The reference should be to "IStackPresentationSite".
|
2006-03-29 09:55:20
| 1,143,640,000
|
resolved fixed
|
f2e114e
| 1,143,650,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/presentations/StackPresentation.java
|
Eclipse_Platform_UI
|
3,922
| 133,058
|
Bug 133058 [CommonNavigator] @value tag reports unknown reference if javadoc 1.5 is used
|
Inside the ui.navigator plugin, some @value tag work fine with javadoc 1.4, but not with javadoc 1.5. In case Eclipse is switching to javadoc 1.5, we should patch the doc with the attached patch.
|
2006-03-23 14:48:07
| 1,143,140,000
|
resolved fixed
|
b0c19d6
| 1,143,580,000
|
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/INavigatorViewerDescriptor.java
|
Eclipse_Platform_UI
|
3,923
| 129,061
|
Bug 129061 [Common Navigator] Request to support programmatic binding of drag adapter
|
We have a problem in the Team use of the Common Navigator is that each repository provider may define one or more viewers. It is not practical for each of the viewer definitions to define the complete set of drag assistants, especially considering that each model may have their own elements that can be dragged. It would simplify things if we could just programmatically bind drag assistants to a viewer. Then we could bind he resource drag assistant to all Team viewers for free. Currently, each provider with a viewer must add a dependency to the org.eclipse.ui.navigator.resources plugin and then add the dragAssistant binding to each viewer.
|
2006-02-22 16:35:20
| 1,140,640,000
|
resolved fixed
|
af24ae1
| 1,143,580,000
|
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/dnd/NavigatorDnDService.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/INavigatorDnDService.java
|
Eclipse_Platform_UI
|
3,924
| 133,375
|
Bug 133375 [Viewers] Need access to the element comparer of a tree selection
| null |
2006-03-27 10:46:03
| 1,143,470,000
|
verified fixed
|
0598494
| 1,143,560,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/CustomHashtable.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeSelection.java
|
Eclipse_Platform_UI
|
3,925
| 133,531
|
Bug 133531 Tests - OutOfMemoryError
|
There have been OOM errors since I20060327-1600 in the UI tests. One was caused by a leak in the WorkbenchMenuManager (dispose menu authority). Investigation is continuing. PW
|
2006-03-28 09:40:35
| 1,143,560,000
|
verified fixed
|
05670af
| 1,143,560,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/TrimBarManager.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/WorkbenchMenuService.java
|
Eclipse_Platform_UI
|
3,926
| 131,771
|
Bug 131771 Match animated message behaviour in Preferences
|
An enhancement should be made to Preferences so that warnings and errors show up in a sliding message area like it they do in TitleAreaDialog.
|
2006-03-14 13:52:40
| 1,142,360,000
|
resolved fixed
|
9f2ec8f
| 1,143,490,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/ImageAndMessageArea.java bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/MessageArea.java bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/TitleAreaDialog.java bundles/org.eclipse.jface/src/org/eclipse/jface/preference/MessageArea.java bundles/org.eclipse.jface/src/org/eclipse/jface/preference/PreferenceMessageArea.java
|
Eclipse_Platform_UI
|
3,927
| 133,342
|
Bug 133342 [Commands] handlers: Global keybindings don't work (Open Type, Search, ...)
|
I20060327-0010 Several important keybindings don't work in this build, although their menu items are enabled and show a shortcut: - Open Type (Ctrl+SHift+T) - Open Type Hierarchy - Search (Ctrl+H) - Organize Imports (in Package Explorer)
|
2006-03-27 07:14:49
| 1,143,460,000
|
verified fixed
|
3681535
| 1,143,490,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java
|
Eclipse_Platform_UI
|
3,928
| 133,059
|
Bug 133059 [Markers] CCE when switching Problems view grouping
|
I20060322-1335 I switched Problems view grouping from Java Problem Type to Type while a background build was going on. !ENTRY org.eclipse.core.jobs 4 2 2006-03-23 20:36:24.465 !MESSAGE An internal error occurred during: "Process resource updates". !STACK 0 java.lang.ClassCastException: org.eclipse.ui.views.markers.internal.MarkerGroupingEntry at org.eclipse.ui.views.markers.internal.FieldCategory.getValue(FieldCategory.java:66) at org.eclipse.ui.views.markers.internal.FieldCategory.compare(FieldCategory.java:88) at org.eclipse.ui.views.markers.internal.CategorySorter.compare(CategorySorter.java:59) at org.eclipse.ui.views.markers.internal.CategorySorter.compare(CategorySorter.java:73) at org.eclipse.jface.viewers.ViewerComparator$1.compare(ViewerComparator.java:184) at java.util.Arrays.mergeSort(Arrays.java:1284) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1295) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.mergeSort(Arrays.java:1296) at java.util.Arrays.sort(Arrays.java:1223) at org.eclipse.jface.viewers.ViewerComparator.sort(ViewerComparator.java:182) at org.eclipse.ui.views.markers.internal.MarkerAdapter.buildAllMarkers(MarkerAdapter.java:240) at org.eclipse.ui.views.markers.internal.MarkerView.updateForContentsRefresh(MarkerView.java:412) at org.eclipse.ui.views.markers.internal.MarkerView$MarkerProcessJob.run(MarkerView.java:146) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
|
2006-03-23 15:02:02
| 1,143,140,000
|
verified fixed
|
8f67349
| 1,143,480,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerMessages.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/ProblemView.java
|
Eclipse_Platform_UI
|
3,929
| 111,144
|
Bug 111144 WorkingCopyPreferences tries to flush removed pref nodes
| null |
2005-09-29 16:57:57
| 1,128,030,000
|
verified fixed
|
d6a6c3f
| 1,143,460,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/preferences/WorkingCopyManager.java
|
Eclipse_Platform_UI
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.