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 |
|---|---|---|---|---|---|---|---|---|---|---|
1,930 | 273,330 |
Bug 273330 [JFace] Add API to MessageDialog to enable clients to use SWT.SHEET
|
A new style constant SWT.SHEET was added recently. Without adding new API in JFace, clients who are currently using the convenience methods MessageDialog.openWarning/Error/Information/Question/Confirmation would not be able to open these dialogs as sheets.
|
2009-04-22 15:12:05
| 1,240,430,000 |
verified fixed
|
18de306
| 1,240,500,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/MessageDialog.java bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/MessageDialogWithToggle.java
|
Eclipse_Platform_UI
|
1,931 | 255,422 |
Bug 255422 [Contributions] Toolbar painting issues when a command is contributed to the menu
| null |
2008-11-14 18:32:27
| 1,226,710,000 |
verified fixed
|
0f9db3d
| 1,240,500,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ViewPane.java
|
Eclipse_Platform_UI
|
1,932 | 272,583 |
Bug 272583 [Dialogs] OK button is in the wrong position if dialog explicitly calls layout() before initializeBounds()
|
Select a project in the Package Explorer and hit delete. When the Delete Resources dialog pops up for confirmation, the 3 buttons are displayed in the following order: Preview, OK, Cancel. On the Mac this should be: Preview, Cancel, OK. Appears to be a problem on both Cocoa and Carbon on Eclipse 3.5 Version: 3.5.0 Build id: I20090414-0800
|
2009-04-16 17:10:34
| 1,239,920,000 |
verified fixed
|
050b72e
| 1,240,490,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/Dialog.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/dialogs/AllTests.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/dialogs/DialogTest.java
|
Eclipse_Platform_UI
|
1,933 | 190,838 |
Bug 190838 [Presentation] Can't drag a non-instantiated view out of a minimized stack
|
Found in RC3: Fresh WS, minimize the bottom stack Try to drag the 'Declaration' view no drop area are supported If the view has been visible then it works correctly. The problem is that the DnD dropTarget handlers all use a check of the form to prevent dragging between WBW's: draggedPart.getWorkbenchWindow() != getWorkbenchWindow() However, if the 'draggedPart' is a ViewPane whose view has never been displayed then it hasn't had its 'control' defined yet leading to 'draggedPart.getWorkbenchWindow()' always returning 'null' and failing the test. This was impossible in the 3.0 presentation because clicking on a view to drag it in the presentation would activate it; causing the control to be created.
|
2007-06-04 12:16:44
| 1,180,970,000 |
verified fixed
|
cb83ec5
| 1,240,420,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/FastViewDnDHandler.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PartSashContainer.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PerspectiveHelper.java
|
Eclipse_Platform_UI
|
1,934 | 267,934 |
Bug 267934 [Perspectives] Space doesn't check/unckeck focused list item
|
This might be an SWT issue. I submitted here because there might be some missing code in platform ui code. Reproduce: Switch to a perspective, like "Team Sync". Ctrl+Shift+T is missing by default. Right click on toolbar, and press "Customize Perspective...". "From Tool Bar Visibility" (which might be better to be spelled as Toolbar Visibility), open "Search" tree item, and check "Open Type (Ctrl+Shift+T)". You will prompted by a yes/no question. Press Yes. Now the form switches to "Command Groups Availabililty". Focus seems to be on "Java Navigation" checkbox, but pressing "Space" does check/unckeck the first item of "Available command groups", in my case Annotation Navigation.
|
2009-03-10 14:16:00
| 1,236,710,000 |
verified fixed
|
645e483
| 1,240,420,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/CustomizePerspectiveDialog.java
|
Eclipse_Platform_UI
|
1,935 | 267,834 |
Bug 267834 [Perspectives] Customize Perspective dialog: Warning for invisible items needs polish
| null |
2009-03-10 08:10:43
| 1,236,690,000 |
verified fixed
|
29203db
| 1,240,410,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/dialogs/CustomizePerspectiveDialog.java
|
Eclipse_Platform_UI
|
1,936 | 273,163 |
Bug 273163 [CSS] Remove dependency on org.apache.commons.logging, xerces, xml.resolver
|
We shouldn't require this.
|
2009-04-21 21:08:46
| 1,240,360,000 |
resolved fixed
|
e4c737a
| 1,240,360,000 |
bundles/org.eclipse.e4.ui.css.core/src/org/eclipse/e4/ui/css/core/dom/properties/providers/CSSPropertyHandlerLazyProviderImpl.java bundles/org.eclipse.e4.ui.css.core/src/org/eclipse/e4/ui/css/core/impl/sac/CSSDocumentHandlerImpl.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/CSSPropertyBackgroundSWTHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/CSSPropertyClassificationSWTHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/resources/SWTResourcesRegistry.java
|
Eclipse_Platform_UI
|
1,937 | 194,917 |
Bug 194917 stack overflow error from working set management
|
stack overflow error on saving newly created bugzilla task. Error dialog said something strange about adding entry to the working set. -- Error Log -- Date: Fri Jun 29 10:05:52 EDT 2007 Message: task activity listener failed: org.eclipse.mylyn.internal.tasks.ui.workingsets.TaskWorkingSetUpdater@1d8c046 Severity: Error Plugin ID: org.eclipse.mylyn Stack Trace: java.lang.StackOverflowError at com.sun.org.apache.xerces.internal.dom.ParentNode.getLength(ParentNode.java:720) at org.eclipse.ui.XMLMemento.getChildren(XMLMemento.java:224) at org.eclipse.ui.internal.AggregateWorkingSet.restoreWorkingSet(AggregateWorkingSet.java:199) at org.eclipse.ui.internal.AbstractWorkingSet.getElementsArray(AbstractWorkingSet.java:151) at org.eclipse.ui.internal.AbstractWorkingSet.getElements(AbstractWorkingSet.java:139) at org.eclipse.ui.internal.AggregateWorkingSet.constructElements(AggregateWorkingSet.java:83) at org.eclipse.ui.internal.AggregateWorkingSet.restoreWorkingSet(AggregateWorkingSet.java:212) at org.eclipse.ui.internal.AbstractWorkingSet.getElementsArray(AbstractWorkingSet.java:151) at org.eclipse.ui.internal.AbstractWorkingSet.getElements(AbstractWorkingSet.java:139) at org.eclipse.ui.internal.AggregateWorkingSet.constructElements(AggregateWorkingSet.java:83) at org.eclipse.ui.internal.AggregateWorkingSet.restoreWorkingSet(AggregateWorkingSet.java:212) at org.eclipse.ui.internal.AbstractWorkingSet.getElementsArray(AbstractWorkingSet.java:151) at org.eclipse.ui.internal.AbstractWorkingSet.getElements(AbstractWorkingSet.java:139) ....
|
2007-06-29 10:10:30
| 1,183,130,000 |
verified fixed
|
5880f61
| 1,240,340,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IWorkingSet.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/AggregateWorkingSet.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchMessages.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/api/IAggregateWorkingSetTest.java
|
Eclipse_Platform_UI
|
1,938 | 273,012 |
Bug 273012 [Forms] NPE in FormPage.setActive(...)
| null |
2009-04-21 00:21:03
| 1,240,290,000 |
resolved fixed
|
7d103d6
| 1,240,330,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/forms/editor/FormPage.java
|
Eclipse_Platform_UI
|
1,939 | 89,256 |
Bug 89256 [Themes] Poor layout in colors and fonts preference page
| null |
2005-03-28 13:29:34
| 1,112,030,000 |
verified fixed
|
1632edc
| 1,240,250,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/themes/ColorsAndFontsPreferencePage.java
|
Eclipse_Platform_UI
|
1,940 | 266,097 |
Bug 266097 [Commands] NPE in SubActionBars.clearGlobalActionHandlers(..) when view could not be created
| null |
2009-02-25 05:49:43
| 1,235,560,000 |
verified fixed
|
3194f4a
| 1,240,250,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/SubActionBars.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ViewReference.java
|
Eclipse_Platform_UI
|
1,941 | 272,913 |
Bug 272913 [ActivityMgmt] Dynamically contributed activity extensions are not registering
| null |
2009-04-20 11:04:35
| 1,240,240,000 |
verified fixed
|
d40975f
| 1,240,250,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/activities/ExtensionActivityRegistry.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/activities/DynamicTest.java
|
Eclipse_Platform_UI
|
1,942 | 268,816 |
Bug 268816 [WorkbenchLauncher] 'Workspaces' preference page does not inherit dialog font
| null |
2009-03-16 11:38:00
| 1,237,220,000 |
verified fixed
|
d11b126
| 1,240,060,000 |
bundles/org.eclipse.ui.ide.application/src/org/eclipse/ui/internal/ide/application/dialogs/RecentWorkspacesPreferencePage.java
|
Eclipse_Platform_UI
|
1,943 | 270,174 |
Bug 270174 [Wizards] Wizard's 'Finish' button is misaligned if there are multiple pages and it cannot be finished early
|
Build id: I20090325-1135 1. File > New > Other... 2. See that the 'Finish' button is at the end of the button bar. 3. Window > Preferences > Java > Installed JREs 4. Click the 'Add...' button. 5. See that the 'Finish' button is not the last button. 6. Close the dialog. 7. Select an existing JRE. 8. Click 'Edit...'. 9. See that the 'Finish' button is at the end of the button bar. I snooped around the code but couldn't quite figure out what was wrong. :o
|
2009-03-26 15:56:14
| 1,238,100,000 |
verified fixed
|
5bed844
| 1,239,970,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/wizard/WizardDialog.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/wizards/ButtonAlignmentTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/wizards/WizardTestSuite.java
|
Eclipse_Platform_UI
|
1,944 | 265,422 |
Bug 265422 [FieldAssist] Field assist hint popup border is black
| null |
2009-02-19 03:54:33
| 1,235,030,000 |
verified fixed
|
b9e8efb
| 1,239,910,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ControlDecoration.java bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/DecoratedField.java
|
Eclipse_Platform_UI
|
1,945 | 218,302 |
Bug 218302 [Help] WorkbenchHelpSystem.desiredHelpSystemId fails
|
Build ID: I20071213-1700 Eclipse 3.4 M4 The following method findElement(...) from the Runnable in method WorkbenchHelpSystem#initializePluggableHelpUI doesn't work as expected; it always returns the first element instead of the desired element. private IConfigurationElement findElement( String desiredHelpSystemId, IExtension[] extensions) { for (int i = 0; i < extensions.length; i++) { IExtension extension = extensions[i]; if (desiredHelpSystemId.equals(extension.getUniqueIdentifier())) { IConfigurationElement[] elements = extensions[0] .getConfigurationElements(); if (elements.length == 0) { // help UI present but mangled - act like there was // no help // UI return null; } return elements[0]; } } return null; } The "extensions[0]" should be replaced by "extension".
|
2008-02-08 09:05:05
| 1,202,480,000 |
verified fixed
|
13a77d3
| 1,239,910,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/help/WorkbenchHelpSystem.java
|
Eclipse_Platform_UI
|
1,946 | 250,125 |
Bug 250125 createExistentResourceFromHandle forgets to create children resources
|
Problem: The method FolderDescription#createExistentResourceFromHandle(IResource,IProgressMonitor) checks if the folder already exists and returns immediately if so. In cases where the FolderDescription has members which are not existing at that moment, that members will not be created. Use case: Assume you want to create a folder and a file in that folder and use two operations for this. I know it is not necessary to use two operations but my configuration is more complex than this example code. IFolder folder = ... // must not exist CreateFolderOperation op1 = new CreateFolderOperation(folder,...); IFile file = folder.getFile(...); // must not exist CreateFileOperation op1 = new CreateFileOperation(file,...); op1.execute(...); op2.execute(...); The execution of the op2 does not create the file because as stated above createExistentResourceFromHandle returns immediately because the parent folder of the file was created by op1. IMHO createExistentResourceFromHandle must check if members of a FolderDescription should be created.
|
2008-10-08 12:51:25
| 1,223,480,000 |
verified fixed
|
ce3bf42
| 1,239,910,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/undo/AbstractResourcesOperation.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/undo/CreateFileOperation.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/undo/CreateFolderOperation.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/operations/WorkspaceOperationsTests.java
|
Eclipse_Platform_UI
|
1,947 | 252,887 |
Bug 252887 [PropertiesView] REGRESSION: Pressing F1 causes loss of editor properties
|
Build ID: IES 3.4.1 used in RAD 7.5.1 Steps To Reproduce: Our product (WebSphere Integration Developer 6.2) makes extensive use of the property sheet view to show/edit the properties of items selected in our editors. When focus is in the property sheet, pressing F1 is causing the Help View to become the active workbench part (this was not the behavior in 3.4.0 and earlier). When the Help View becomes the active part the contents of the property sheet view contributed by the editor are lost. The user is forced to re-select the item in the editor in order to continue to work on the properties they are editing. We make extensive use of F1 help to assist the user in editing properties. This regression in usability is a stop ship defect for WID 6.2 I have confirmed that this is also happening when using a RAD editor (web diagram). The attached screen shots show the effect of pressing F1 in the property sheet Note in the Before picture the help view is not the active part and the content of the properties view are maintained In the After picture the help view is the active part and the contents of the properties
|
2008-10-30 16:02:02
| 1,225,400,000 |
resolved fixed
|
4b60fd8
| 1,239,890,000 |
bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/PropertySheet.java
|
Eclipse_Platform_UI
|
1,948 | 266,970 |
Bug 266970 [CSS] Widget.setData keys should be qualified
|
There are many cases where we use Widget.setData(keyString, value) to remember some CSS value. See SWTElement for many examples. These key strings are often of the form "active", "hover", etc. They should be fully qualified to reduce conflicts since others may be using the widget's setData. So should instead be: "active" -> "org.eclipse.e4.ui.css.swt.active" "hover" -> "org.eclipse.e4.ui.css.swt.hover" Also, we should have final static fields to hold keys with these as values, eg. in DynamicPseudoClassesSWTActiveHandler we would have final static String WIDGET_ACTIVE_KEY = "org.eclipse.e4.ui.css.swt.activeLost"
|
2009-03-03 23:11:23
| 1,236,140,000 |
resolved fixed
|
08cadab
| 1,239,820,000 |
bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/CSSSWTConstants.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/dom/SWTElement.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/selectors/DynamicPseudoClassesSWTActiveHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/selectors/DynamicPseudoClassesSWTFocusHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/selectors/DynamicPseudoClassesSWTHoverHandler.java
|
Eclipse_Platform_UI
|
1,949 | 262,173 |
Bug 262173 [Workbench] [About] ISharedImages.IMG_OBJ_ADD has no Image
|
Build ID: M20080911-1700 PlatformUI.getWorkbench().getSharedImages() .getImage(ISharedImages.IMG_OBJ_ADD) returns null, although the Javadoc on ISharedImages states that "This class provides Image and ImageDescriptors for each named image in the interface." I tried all other IMG_OBJ_* images -- for each of those an image is returned. I have not tried all the other images defined in ISharedImages.
|
2009-01-23 09:30:13
| 1,232,720,000 |
verified fixed
|
63b2517
| 1,239,820,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchImages.java
|
Eclipse_Platform_UI
|
1,950 | 263,090 |
Bug 263090 [legacy] Load the model with commands and handlers
|
The legacy fragment should be able to load the commands model with commands and the handlers model with handlers. PW
|
2009-01-30 14:47:51
| 1,233,340,000 |
resolved fixed
|
ff86353
| 1,239,820,000 |
bundles/org.eclipse.e4.ui.services/src/org/eclipse/e4/ui/internal/services/ContextCommandService.java bundles/org.eclipse.e4.ui.services/src/org/eclipse/e4/ui/internal/services/ContextHandlerService.java bundles/org.eclipse.e4.ui.services/src/org/eclipse/e4/ui/internal/services/HandlerContextFunction.java bundles/org.eclipse.e4.ui.services/src/org/eclipse/e4/ui/services/ECommandService.java bundles/org.eclipse.e4.ui.services/src/org/eclipse/e4/ui/services/EHandlerService.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/ContributedPartFactory.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/SWTPartFactory.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/WBPartFactory.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/IHandlerService.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Workbench.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/renderers/PartHandlerService.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/renderers/PartRenderer.java tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/UIAllTests.java tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/workbench/HandlerTest.java tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/workbench/MWindowTest.java
|
Eclipse_Platform_UI
|
1,951 | 272,165 |
Bug 272165 [Viewers] Potential NPE in FilteredItemsSelectionDialog.ContentProvider.getFilteredItems
|
Build ID: I20090313-0100 Steps To Reproduce: More information: getFilteredItems is very careful about ensuring that the IProgressMonitor is not null. Yet you have this snippet of code: if (filteredElements == null || monitor.isCancelled()) { if (monitor != null) monitor.done(); return new Object[0]; } So why not start the method with if (monitor == null) { monitor = new NullProgressMonitor(); } Anyway, as it is, you can get an NPE there.
|
2009-04-14 11:29:44
| 1,239,720,000 |
verified fixed
|
e59e2f1
| 1,239,820,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/FilteredItemsSelectionDialog.java
|
Eclipse_Platform_UI
|
1,952 | 112,337 |
Bug 112337 [Forms] ColumnLayoutData javadoc for CENTER and RIGHT constants are interchanged
|
Very simple "bug". The javadoc for CENTER and RIGHT constants of the org.eclipse.ui.forms.widgets.ColumnLayoutData class are exchanged. Change this: /** * Horizontal alignment constant - control will be aligned to the right. */ public static final int CENTER = 2; /** * Horizontal alignment constant - control will be centered. */ public static final int RIGHT = 3; to this: /** * Horizontal alignment constant - control will be centered. */ public static final int CENTER = 2; /** * Horizontal alignment constant - control will be aligned to the right. */ public static final int RIGHT = 3; and all is fine :-)
|
2005-10-12 10:00:12
| 1,129,130,000 |
resolved fixed
|
e17c6d9
| 1,239,810,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/forms/widgets/ColumnLayoutData.java
|
Eclipse_Platform_UI
|
1,953 | 272,065 |
Bug 272065 [Trim] Restore detached view over maximized view part throws NullPointerException
|
Build ID: I20070621-1340 Steps To Reproduce: 1.On a RCP application with 3 viewparts, detach one of them, then close the view. 2.Maximize one of the remaining views. 3.Re-open the closed view. An exception is thrown: java.lang.NullPointerException at org.eclipse.ui.internal.Perspective.showView(Perspective.java:2160) More information: Somehow the Perspective showView method is trying to show the detached view on a trim stack
|
2009-04-13 14:55:44
| 1,239,650,000 |
verified fixed
|
d511905
| 1,239,730,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Perspective.java
|
Eclipse_Platform_UI
|
1,954 | 199,499 |
Bug 199499 Switching tabs by Ctrl+PageUp/PageDown must not be caught on the inner tab set
| null |
2007-08-09 18:33:46
| 1,186,700,000 |
verified fixed
|
b7e7588
| 1,239,660,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/part/MultiPageEditorPart.java
|
Eclipse_Platform_UI
|
1,955 | 271,834 |
Bug 271834 Remove e4 workbench dependency on org.eclipse.core.runtime
|
org.eclipse.core.runtime, and the Platform class in particular, are the root of all singleton evil in platform core. We should avoid this bundle and Platform like the plague in e4. Everything of value in core.runtime has a non-singleton equivalent in other core/equinox bundles.
|
2009-04-09 14:49:45
| 1,239,300,000 |
resolved fixed
|
6fde2d4
| 1,239,300,000 |
bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Workbench.java
|
Eclipse_Platform_UI
|
1,956 | 271,830 |
Bug 271830 Use injection for WorkbenchLogger
|
WorkbenchLogger "reaches out" to get a log and a trace instance. It should instead use injection to make it a more reusable piece (and to eat our own e4 programming model dog food).
|
2009-04-09 14:32:56
| 1,239,300,000 |
resolved fixed
|
269d958
| 1,239,300,000 |
bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/WorkbenchLogger.java
|
Eclipse_Platform_UI
|
1,957 | 271,823 |
Bug 271823 Define common injection annotations
|
We currently have three copies of the various annotations for injection (@Inject, @In, @Out, etc). We should have a single set of annotations in a common place rather than copying them everywhere. This is inhibiting wider use of annotations within the e4 workbench because currently each bundle needs to redefine them. I propose creating a new bundle org.eclipse.e4.core.services.annotations that contains these common annotations (and possibly others in the future).
|
2009-04-09 13:56:53
| 1,239,300,000 |
resolved fixed
|
f8e2a40
| 1,239,300,000 |
examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/ExifTable.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Location.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Preview.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Thumbnails.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/annotations/In.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/annotations/Inject.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/annotations/Out.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/annotations/PostConstruct.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/annotations/PreDestroy.java
|
Eclipse_Platform_UI
|
1,958 | 271,799 |
Bug 271799 Replace IBackgroundRunner/IRunnableWithProgress with equinox.concurrent APIs
|
These basic abstractions of "something I want to run", and "someone who can run things" tend to get reinvented in various components. We should consolidate on the simple low level Equinox APIs for consistency.
|
2009-04-09 11:31:56
| 1,239,290,000 |
resolved fixed
|
0eb0caa
| 1,239,290,000 |
bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/BackgroundRunnerFunction.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Activator.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/JobExecutor.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Thumbnails.java
|
Eclipse_Platform_UI
|
1,959 | 271,683 |
Bug 271683 [Compatibility] hook into the popup menus, somehow
|
It would be nice if we were filling in context menus with either object contributions or menu contributions (or both). PW
|
2009-04-08 15:09:35
| 1,239,220,000 |
resolved fixed
|
41f8996
| 1,239,290,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PopupMenuExtender.java
|
Eclipse_Platform_UI
|
1,960 | 199,364 |
Bug 199364 [Browser] Internal Web Browser get pop up with the address bar empty
|
The internal web browser poped up when triggered with this code IWorkbenchBrowserSupport browserSupport = MyPlugin.getDefault() .getWorkbench().getBrowserSupport(); browser = browserSupport.createBrowser(IWorkbenchBrowserSupport.LOCATION_BAR, null, null, null); URL url = new URL(inURL); browser.openURL(url); The browser works fine, but the address bar is empty at the initial stage and need to drop down it to view the URL and set it.
|
2007-08-09 02:10:39
| 1,186,640,000 |
resolved fixed
|
d3af066
| 1,239,140,000 |
bundles/org.eclipse.ui.browser/src/org/eclipse/ui/internal/browser/BrowserViewer.java
|
Eclipse_Platform_UI
|
1,961 | 139,528 |
Bug 139528 [Browser] Error message should be improved
|
I got the following error in my log. The message is probably allright except for the trailing null. eclipse.buildId=I20060428-1315 java.fullversion=J2RE 1.4.2 IBM build cxia32142-20050609 (JIT enabled: jitc) BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 -debug -consolelog Warning Mon May 01 12:39:50 EDT 2006 Internal browser is not available: null
|
2006-05-01 11:41:25
| 1,146,500,000 |
resolved fixed
|
9ae574d
| 1,239,130,000 |
bundles/org.eclipse.ui.browser/src/org/eclipse/ui/internal/browser/WebBrowserUtil.java
|
Eclipse_Platform_UI
|
1,962 | 270,989 |
Bug 270989 Context refactoring
|
Based on discussions over the past weeks, I'm doing a refactoring of the context API. Major changes: - Renamed IComputedValue to IContextFunction - Renamed *Value to *Function - Renamed UIContextScheduler to UISchedulerStrategy - Added concept of ILookupStrategy to delegate lookup of keys that are not yet defined in a given context - Re-implemented OSGi service support using lookup strategy I also fixed a couple of NPE's I found while testing with the e4 photo demo (null realms, etc)
|
2009-04-02 11:47:44
| 1,238,690,000 |
resolved fixed
|
9309f5d
| 1,238,690,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/ContributedPartFactory.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/StackModelFactory.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/WBPartFactory.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/BackgroundRunnerFunction.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/BackgroundRunnerValue.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/ProgressMonitorFunction.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/ProgressMonitorValue.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/ActiveChildOutputFunction.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/ActiveChildOutputValue.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/ReflectionContributionFactory.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/UIContextScheduler.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/UISchedulerStrategy.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Workbench.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Library.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/RealmFunction.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/RealmValue.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/WorkspaceValue.java
|
Eclipse_Platform_UI
|
1,963 | 68,684 |
Bug 68684 [EditorMgmt] tabs: Remove the MRU tab reordering code from the default presentation
|
DefaultPartPresentation recently added code to arrange the editor tabs in left-to-right order until the tab list is full, in which case it inserts at the end of the visible list. There is also code to rearrange tabs when an invisible editor is selected from the dropdown. This behavior is quite complicated, which makes it hard to keep track of where editors are. It also makes it impossible for the user to arrange the tabs themselves, since Eclipse may subsequently move an editor if it is selected through the dropdown. It would be much simpler if the following changes were made: 1. The tabs always opened in left-to-right order. The window of visible tabs would scroll to show the newly opened editor if it isn't already visible. 2. The editor dropdown always showed editors in the same order that they are shown in the tabs rather than in alphabetical order (although highlighting the currently visible tabs makes sense) 3. In addition to the dropdown, left and right arrows could be shown on either end of the tabs, to indicate to the user that they are looking at a sliding window of tabs.
|
2004-06-25 18:30:07
| 1,088,200,000 |
resolved fixed
|
6704c85
| 1,238,620,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/presentations/BasicPartList.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/tweaklets/TabBehaviour.java
|
Eclipse_Platform_UI
|
1,964 | 270,774 |
Bug 270774 [Mac] ui.tests.rcp did not finish because CocoaUIEnhancer crashes
| null |
2009-04-01 09:51:39
| 1,238,590,000 |
verified fixed
|
ec8daa5
| 1,238,620,000 |
bundles/org.eclipse.ui.cocoa/src/org/eclipse/ui/internal/cocoa/CocoaUIEnhancer.java
|
Eclipse_Platform_UI
|
1,965 | 260,417 |
Bug 260417 [Commands] Handler expressions ignored in multi page editors.
| null |
2009-01-08 11:43:26
| 1,231,430,000 |
verified fixed
|
04d9c85
| 1,238,600,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/contexts/SlaveContextService.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/handlers/NestableHandlerService.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/handlers/SlaveHandlerService.java
|
Eclipse_Platform_UI
|
1,966 | 270,146 |
Bug 270146 [Mac] NSToolbar leak in CocoaUIEnhancer
| null |
2009-03-26 12:42:17
| 1,238,090,000 |
verified fixed
|
912fbac
| 1,238,440,000 |
bundles/org.eclipse.ui.cocoa/src/org/eclipse/ui/internal/cocoa/CocoaUIEnhancer.java
|
Eclipse_Platform_UI
|
1,967 | 267,359 |
Bug 267359 [Commands] The platform hangs upon shutdown when an Action Handler dispose method throws an exception
|
Steps to reproduce: 1. Write a simple plugin with a button in the toolbar and an action handler associated. 2. In the action handler, in the dispose method throw a runtime exception, e.g. NullPointerException 3. Start the Eclipse IDE with the plugin 4. Quit Eclipse. Expected behavior - Eclipse quits and the process is terminated. Actual behavior - Eclipse process just hangs indefinitely until being killed. It seems that there is no proper handling for exceptions during dispose, thus, the whole shutdown sequence just aborts after destroying most of the resources. This is not a good behavior. At least it should be clearly documented in the dispose method Javadoc. Seeking out my bug almost drove me crazy.
|
2009-03-06 08:45:53
| 1,236,350,000 |
verified fixed
|
23126be
| 1,238,410,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/handlers/HandlerPersistence.java
|
Eclipse_Platform_UI
|
1,968 | 268,955 |
Bug 268955 [Commands] IWorkbenchCommandConstants is missing API restrictions
|
3.5 M6 IWorkbenchCommandConstants is missing API restrictions which makes it impossible in the future to add new constants. Please add: * @noimplement This interface is not intended to be implemented by clients. * @noextend This interface is not intended to be extended by clients.
|
2009-03-17 07:51:49
| 1,237,290,000 |
verified fixed
|
c7bbfad
| 1,238,410,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IWorkbenchCommandConstants.java
|
Eclipse_Platform_UI
|
1,969 | 230,360 |
Bug 230360 [JFace] FontRegistry does not play nicely with non-UI threads
|
This method does: ... Display current = Display.getCurrent(); if (current == null) { Shell shell = new Shell(); } This code will _always_ fail because Shell will execute if (!display.isValidThread ()) Which is always TRUE because "current" was null.
|
2008-05-06 06:19:47
| 1,210,070,000 |
verified fixed
|
e93a667
| 1,238,080,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/resource/FontRegistry.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/preferences/FontPreferenceTestCase.java
|
Eclipse_Platform_UI
|
1,970 | 263,690 |
Bug 263690 [Commands] Command that can throw a CoreException during execution is considered successfully run
|
Using M5, I have a case where I try to start a command handler that will fail (I removed some required bundles on purpose). I was checking an error handling code. The problem is that the first time the command is run it looks like it is successful when it failed to terminate normally. Here is the stack trace I have: org.eclipse.core.runtime.CoreException: Plug-in org.eclipse.equinox.p2.ui.sdk was unable to load class org.eclipse.equinox.internal.p2.ui.sdk.InstallNewSoftwareHandler. at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:180) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:162) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:874) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51) at org.eclipse.ui.internal.handlers.HandlerProxy.loadHandler(HandlerProxy.java:335) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:274) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.pde.api.tools.ui.internal.preferences.ApiErrorsWarningsConfigurationBlock$4.mouseDown(ApiErrorsWarningsConfigurationBlock.java:1299) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3877) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3470) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) I think the problem comes from: public final Object execute(final ExecutionEvent event) throws ExecutionException { if (loadHandler()) { if (!isEnabled()) { MessageDialog.openInformation(Util.getShellToParentOn(), WorkbenchMessages.Information, WorkbenchMessages.PluginAction_disabledMessage); return null; } return handler.execute(event); } return null; } where null is returned is the loading of the handler failed. loadHandler is swallowing the core exception. So the best thing to do is to replace the: return null; statement with a throw new ExecutionException(..); This will make sure that the user code can properly detect an execution failure. Steps to reproduce: 1) Define a new command handler that throws a CoreException 2) Run the corresponding command with a try/catch for all potential exceptions thrown by Command.executeWithChecks(..). 3) You won't hit any of the catch blocks on the first run.
|
2009-02-04 15:22:00
| 1,233,780,000 |
verified fixed
|
69f6043
| 1,238,080,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/handlers/HandlerProxy.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/commands/ExceptionThrowingHandler.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/commands/HandlerActivationTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/dynamicplugins/CommandsExtensionDynamicTest.java
|
Eclipse_Platform_UI
|
1,971 | 270,120 |
Bug 270120 [CommonNavigator] tracing .options file *not* put in kit
|
And also adding some more tracing to help debug bindings
|
2009-03-26 09:45:39
| 1,238,080,000 |
verified fixed
|
a3c2577
| 1,238,080,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/Binding.java
|
Eclipse_Platform_UI
|
1,972 | 267,408 |
Bug 267408 [Contributions] RadioState should work like RegistryToggleState
|
It should honour the same 2 IExecutableExtension parameters, default and persist PW
|
2009-03-06 12:41:53
| 1,236,360,000 |
verified fixed
|
94a4a7b
| 1,237,920,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/handlers/RadioState.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/handlers/RegistryToggleState.java
|
Eclipse_Platform_UI
|
1,973 | 269,711 |
Bug 269711 [jface] org.eclipse.jface.viewers.StructuredViewerInternals.AssociateListener contains an invalid api tooling tag
|
@noinstantiate is not valid for interfaces.
|
2009-03-23 12:19:21
| 1,237,830,000 |
resolved fixed
|
1e13700
| 1,237,840,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StructuredViewerInternals.java
|
Eclipse_Platform_UI
|
1,974 | 269,466 |
Bug 269466 [Progress] CCE caused by ProgressManager's 3.x workbench assumptions
| null |
2009-03-19 23:51:49
| 1,237,520,000 |
resolved fixed
|
b1ec74d
| 1,237,840,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressManager.java
|
Eclipse_Platform_UI
|
1,975 | 266,367 |
Bug 266367 [About] Error when closing the new About dialog
|
build I20090224-0800 I opened the new About dialog and was clicking around in the tabs of the Installation Details. When I closed the dialog, I got an error dialog saying: 'org.eclipse.ui.internal.about.AboutPluginsPage' has encountered a problem. An internal error has occurred. Pressing the details showed me: Widget is disposed. There is nothing in my .log file so I don't have a stack trace for you. Note this happened 2 out of 3 times. (during the same Eclipse session) Not sure what the trigger is but I clicked on all tabs.
|
2009-02-26 14:40:47
| 1,235,680,000 |
verified fixed
|
3298c79
| 1,237,830,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/AboutPluginsPage.java
|
Eclipse_Platform_UI
|
1,976 | 269,312 |
Bug 269312 Support @Out annotations
|
Instead of the ugly "outputContext" idea. Using JavaBeans style change notification.
|
2009-03-19 01:06:08
| 1,237,440,000 |
resolved fixed
|
bf6cb15
| 1,237,440,000 |
bundles/org.eclipse.e4.ui.services/src/org/eclipse/e4/ui/services/IServiceConstants.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/ReflectionContributionFactory.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/ExifTable.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Location.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Preview.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Thumbnails.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/annotations/In.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/annotations/Out.java
|
Eclipse_Platform_UI
|
1,977 | 212,696 |
Bug 212696 [ErrorHandling] [Dialogs] Error dialogs: Ctrl-C doesn't copy errors, eventhough there are a "Copy" popup menu
|
Build ID: I20070621-1340 Steps To Reproduce: 1. Run some job that's return a multiple-errors status (a MultiStatus containing Status with exceptions) 2. The error dialog shown up with details buttons to show the error details as a selectable list. 3. In the details panel, select an error and press Ctrl-C. The selected error is not copied. Right-Click and select copy, then all of the errors are copied More information: * Because we already provided the copy function, it would be better if we also tie Ctrl-C to that function * As user can select individual error, copy should only copy that error
|
2007-12-11 20:54:22
| 1,197,420,000 |
resolved fixed
|
3b1f5bf
| 1,237,360,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/statushandlers/DefaultDetailsArea.java
|
Eclipse_Platform_UI
|
1,978 | 269,027 |
Bug 269027 Create and example that modifies the model
|
An example of walking the model and modifying it in the running eclipse. PW
|
2009-03-17 12:43:17
| 1,237,310,000 |
resolved fixed
|
3775888
| 1,237,340,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/SWTPartFactory.java
|
Eclipse_Platform_UI
|
1,979 | 269,058 |
Bug 269058 [UI] Remove product specific code
|
The current implementation of org.eclipse.e4.workbench.ui.internal.Workbench currently contains code (based on the availability of the LegacyHook) that is specific to running either the compatibility layer (LH == true) or the photo demo (PH == false). We should make the base Workbench logic work whichever of the two 'applications' are running (i.e. based -only- on the difference in their 'default' model XMI).
|
2009-03-17 15:22:07
| 1,237,320,000 |
resolved fixed
|
dac9b23
| 1,237,320,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/SWTPartFactory.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/WBPartFactory.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Workbench.java
|
Eclipse_Platform_UI
|
1,980 | 269,025 |
Bug 269025 contributed part name should change when the model changes
|
Currently, the name will not be updated until the part is instantiated. PW
|
2009-03-17 12:38:00
| 1,237,310,000 |
resolved fixed
|
10f2a74
| 1,237,310,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/StackModelFactory.java
|
Eclipse_Platform_UI
|
1,981 | 268,829 |
Bug 268829 [UI] Thumbnails do not appear immediately in photo demo
|
3.5 M6 Latest of CSS/UI psfs as of March 16/11am EST. 1. Run the photo demo 2. Click on an album that has pictures 3. No thumbnails appear. Note if you expand the album, the pictures are there. 4. Click on the thumbnail area itself, the thumbnails will now appear.
|
2009-03-16 12:21:31
| 1,237,220,000 |
resolved fixed
|
95d9ff7
| 1,237,230,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/StackModelFactory.java
|
Eclipse_Platform_UI
|
1,982 | 267,977 |
Bug 267977 [About] Should clicking on uninstall cause the initial about dialog to be closed
|
I20090310 When I hit the uninstall or update button, the dialog from which I initiated the action closes. Should the initial about dialog be closed to at that time?
|
2009-03-10 16:28:27
| 1,236,720,000 |
resolved fixed
|
0b1bc87
| 1,236,720,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/about/IInstallationPageContainer.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/about/InstallationPage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/InstallationDialog.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/AboutDialog.java
|
Eclipse_Platform_UI
|
1,983 | 257,919 |
Bug 257919 [Viewers] OwnerDraw: Open type doesn't display the selected type
| null |
2008-12-08 08:44:02
| 1,228,740,000 |
resolved fixed
|
14177ce
| 1,236,720,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StyledCellLabelProvider.java
|
Eclipse_Platform_UI
|
1,984 | 267,748 |
Bug 267748 UI Test Failure in org.eclipse.ui.tests.leaks.LeakTests.testBug265449PropertiesLeak
|
HEAD (It's failing on Fedora 10 Linux when running with Xvfb/metacity) The test runs fine when only the Leak tests are run by themselves UI Test Suite org.eclipse.ui.tests.UiTestSuite org.eclipse.ui.tests.leaks.LeakTests testBug265449PropertiesLeak(org.eclipse.ui.tests.leaks.LeakTests) junit.framework.AssertionFailedError: Reference not enqueued at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.eclipse.ui.tests.leaks.LeakTests.checkRef(LeakTests.java:77) at org.eclipse.ui.tests.leaks.LeakTests.testBug265449PropertiesLeak(LeakTests.java:239) 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 junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:114) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3452) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3099) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2393) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2357) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2209) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:499) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:492) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:46) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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.equinox.launcher.Main.invokeFramework(Main.java:556) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511) at org.eclipse.equinox.launcher.Main.run(Main.java:1284) at org.eclipse.equinox.launcher.Main.main(Main.java:1260)
|
2009-03-09 18:54:27
| 1,236,640,000 |
resolved fixed
|
9a5673e
| 1,236,720,000 |
tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/AbstractPropertySheetTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/MultiInstancePropertySheetTest.java
|
Eclipse_Platform_UI
|
1,985 | 267,722 |
Bug 267722 [CommonNavigator] ClassCastException when synchronizing
|
I20090309-1300 When I hit the synchronize button and then hit next on CVS,I get the following exception java.lang.ClassCastException: org.eclipse.ui.dialogs.ContainerCheckedTreeViewer at org.eclipse.ui.internal.navigator.NavigatorContentService.getSourceOfContribution(NavigatorContentService.java:732) at org.eclipse.ui.internal.navigator.NavigatorContentService.findDescriptorsByTriggerPoint(NavigatorContentService.java:768) at org.eclipse.ui.internal.navigator.NavigatorContentService.findContentExtensionsByTriggerPoint(NavigatorContentService.java:624) at org.eclipse.ui.internal.navigator.NavigatorContentService.findContentExtensionsByTriggerPoint(NavigatorContentService.java:605) at org.eclipse.ui.internal.navigator.NavigatorContentService.findRootContentExtensions(NavigatorContentService.java:509) at org.eclipse.ui.internal.navigator.NavigatorContentService.findRootContentExtensions(NavigatorContentService.java:467) at org.eclipse.ui.internal.navigator.NavigatorContentService.updateService(NavigatorContentService.java:375) at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.inputChanged(NavigatorContentServiceContentProvider.java:591) at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:270) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1617) at org.eclipse.team.internal.ui.mapping.ModelElementSelectionPage.setVisible(ModelElementSelectionPage.java:221) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1161) at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1139) at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.java:1128) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1126) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:820) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1204) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1228) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1213) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1031) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3208) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2881) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.team.internal.ui.synchronize.actions.SynchronizePageDropDownAction$1.run(SynchronizePageDropDownAction.java:40) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1204) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1228) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1213) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1031) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3208) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2881) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2393) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2357) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2209) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:499) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:492) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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.equinox.launcher.Main.invokeFramework(Main.java:556) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511) at org.eclipse.equinox.launcher.Main.run(Main.java:1284)
|
2009-03-09 16:04:27
| 1,236,630,000 |
verified fixed
|
9bf3d9e
| 1,236,660,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StructuredViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StructuredViewerInternals.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentService.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/SafeDelegateTreeContentProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/StructuredViewerManager.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/CommonViewer.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/INavigatorContentServiceTests.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/NavigatorTestBase.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/NonCommonViewerView.java
|
Eclipse_Platform_UI
|
1,986 | 218,884 |
Bug 218884 [DataBinding] Add API: WorkbenchObservables
|
... for things like listening to ISelectionService
|
2008-02-13 16:57:05
| 1,202,940,000 |
resolved fixed
|
0fcabda
| 1,236,630,000 |
bundles/org.eclipse.core.databinding.observable/src/org/eclipse/core/databinding/observable/Observables.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/databinding/WorkbenchObservables.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/databinding/WorkbenchProperties.java
|
Eclipse_Platform_UI
|
1,987 | 260,664 |
Bug 260664 [JFace] "Clear" works incorrectly in filtered preference dialog
|
Build ID: Eclipse3.4.0 Steps To Reproduce: 1.In SampleAction run method, add below codes to filter preference dialog, only want to see "Plug-in Development" node in preference dialog. String [] displayIDs = {"org.eclipse.pde.ui.MainPreferencePage"}; PreferenceDialog dialog = PreferencesUtil.createPreferenceDialogOn(null, null, displayIDs, null); dialog.open(); 2.Click Sample Menu action. The filtered preference dialog is opened. 3.Input "aa" to input filter text, no node appears in the tree. It's correct. 4.Click "Clear" button. All notes appear in the tree, which is incorrect. Only the filtered node "Plug-in Development" should appear in the tree. We need to filter preference dialog in some conditions in the product, so needs the filtered dialog can not display hide notes by every UI entry. More information:
|
2009-01-12 00:48:19
| 1,231,740,000 |
verified fixed
|
b8dde80
| 1,236,630,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/PreferencesUtil.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/FilteredPreferenceDialog.java
|
Eclipse_Platform_UI
|
1,988 | 248,103 |
Bug 248103 [PropertiesView] Multi-instance Properties View
| null |
2008-09-22 03:53:14
| 1,222,070,000 |
resolved fixed
|
748cbf4
| 1,236,630,000 |
bundles/org.eclipse.ui.views/src/org/eclipse/ui/internal/views/properties/PropertiesMessages.java bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/IPropertiesHelpContextIds.java bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/NewPropertySheetHandler.java bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/PinPropertySheetAction.java bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/PropertySheet.java bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/PropertyShowInContext.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/ui/tests/session/NonRestorableView.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/AbstractPropertySheetTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/MultiInstancePropertySheetTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/NewPropertySheetHandlerTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/PropertySheetAuto.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/PropertySheetTestSuite.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/PropertyShowInContextTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/ShowInPropertySheetTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/TestNewPropertySheetHandler.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/TestPropertySheetPage.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/session/NonRestorablePropertySheetTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/session/SessionTests.java
|
Eclipse_Platform_UI
|
1,989 | 262,666 |
Bug 262666 [EditorMgmt] EditorErrorPart fails on create
|
Found in I20090127-0100. If you have an open editor whose implementation bundle is unavailable we no longer get an 'error' part but the tab does -nothing- when clicked except activate. The contents are whatever was left over from the previously active editor. Setup: Create a fresh workspace and check the org.eclipse.ui.examples.propertysheet project (gets you a '.usr' editor) Run an inner, create a new plugin project (gets us a manifest editor) add a 'foo.usr' file to it (gets us a .usr editor) Close the inner Now, close the examples project and re-run the inner. When we closed the 'foo' editor was active but now the manifest editor is up...but when you click on it the editor contents stay as they were (showing the manifest form). Close the manifest editor (leaving only the bogus one). Now, double click on the editor area (as if to maximize)...views start disappearing!! trace coming...
|
2009-01-27 16:28:51
| 1,233,090,000 |
resolved fixed
|
4db94f3
| 1,236,620,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorReference.java
|
Eclipse_Platform_UI
|
1,990 | 267,469 |
Bug 267469 [Help] WorkbenchHelpSystem.setHelp() should strip mnemonics
|
org.eclipse.ui.internal.help.WorkbenchHelpSystem.setHelp(IAction, String) creates a Context object for an action. It uses the name of the action as the title of the context, however it is not stripping any '&' characters from the title, resulting in a title like "Open &Type"
|
2009-03-06 18:51:00
| 1,236,380,000 |
verified fixed
|
17a7b44
| 1,236,600,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/help/WorkbenchHelpSystem.java
|
Eclipse_Platform_UI
|
1,991 | 267,495 |
Bug 267495 javadoc warning in N20090306-2000
|
javadoc: warning - Multiple sources of package comments found for package "org.eclipse.core.databinding.util"
|
2009-03-07 09:19:22
| 1,236,440,000 |
resolved fixed
|
1698530
| 1,236,570,000 |
bundles/org.eclipse.core.databinding/src/org/eclipse/core/databinding/util/ILogger.java bundles/org.eclipse.core.databinding/src/org/eclipse/core/databinding/util/Policy.java
|
Eclipse_Platform_UI
|
1,992 | 213,645 |
Bug 213645 [RCP] Requesting programmatic hook to create view folders that remain visible after their last child is closed
| null |
2007-12-20 16:45:02
| 1,198,190,000 |
resolved fixed
|
52d281a
| 1,236,570,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/application/WorkbenchWindowAdvisor.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/FastViewManager.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PageLayout.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PerspectiveHelper.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ViewStack.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java
|
Eclipse_Platform_UI
|
1,993 | 267,560 |
Bug 267560 [EditorMgmt] Javadoc inconsistent for EditorManager#findEditors
|
The Javadoc comments for the two org.eclipse.ui.internal.EditorManager#findEditors methods are inconsistent/wrong. The description of findEditors(IEditorInput, String, int) says (correct): If none match, returns an empty array. Whereas the @return tag says (incorrect): the matching editor, or <code>null</code> if no match fond The description of findEditors(List, IEditorInput, String, int, List) has a @return tag although the method is void. Also note the typo ('fond') in all the @return tags of the findEditor[s] methods.
|
2009-03-08 19:32:15
| 1,236,560,000 |
resolved fixed
|
8b75605
| 1,236,560,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorManager.java
|
Eclipse_Platform_UI
|
1,994 | 198,971 |
Bug 198971 [CommonNavigator] Provide extension schema for setting help ID
|
I haven't been able to find a way to set the help ID for a view using the common resource navigator. It seems that having schema support for this would be the best way to handle this.
|
2007-08-06 14:19:57
| 1,186,420,000 |
resolved fixed
|
eb9edd3
| 1,236,550,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/IViewerExtPtConstants.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorViewerDescriptor.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorViewerDescriptorManager.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/CommonNavigator.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/INavigatorViewerDescriptor.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/NavigatorTestBase.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/ViewerTest.java
|
Eclipse_Platform_UI
|
1,995 | 218,127 |
Bug 218127 [CommonNavigator] Common Navigator inherited viewer bindings
|
This enhancement describes the ability for common navigator viewer instances to "inherit" the action and content bindings from other viewers.
|
2008-02-07 00:43:25
| 1,202,360,000 |
verified fixed
|
c0842bf
| 1,236,530,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/IViewerExtPtConstants.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorViewerDescriptor.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorViewerDescriptorManager.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/ActionProviderTest.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/ActivityTest.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/NavigatorTestBase.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/NavigatorTestSuite.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/ViewerTest.java
|
Eclipse_Platform_UI
|
1,996 | 267,117 |
Bug 267117 [JFace] Provide possibility for subclasses to check if a column is visible in ViewerRow
|
Currently this is decided by checking with width but this makes Nebula-Grid fail.
|
2009-03-04 16:40:10
| 1,236,200,000 |
verified fixed
|
1947bce
| 1,236,500,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerCell.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerRow.java
|
Eclipse_Platform_UI
|
1,997 | 251,575 |
Bug 251575 [Viewers] TableViewer support for virtual selection
| null |
2008-10-21 13:49:24
| 1,224,610,000 |
resolved fixed
|
b61eb1f
| 1,236,400,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/IIndexableLazyContentProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewer.java
|
Eclipse_Platform_UI
|
1,998 | 218,673 |
Bug 218673 [DataBinding] SWTUtil should use timerExec(0,...) rather than asyncExec
|
In the event that you have a lot of cross-realm bindings, the current implementation of DisplayRealm generates a lot of flicker due to excess asyncExecs. It should be using SWTUtil.greedyExec instead. (Note: if you make this change, you may want to remove the display filter from WorkQueue. There are certain methods that do not like being called from an event filter, so running arbitrary asyncExecs during a filter may not always be safe.)
|
2008-02-12 13:45:06
| 1,202,840,000 |
resolved fixed
|
a6fdce0
| 1,236,390,000 |
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/swt/SWTUtil.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/swt/WorkQueue.java
|
Eclipse_Platform_UI
|
1,999 | 264,650 |
Bug 264650 [Viewers] [JFace] Java doc for TreeSelection is wrong
|
Build ID: I20090126-1800 The default constructor of TreeSelection says "Note that TreeSelection.EMPTY is not equals() to StructuredViewer.EMPTY". But TreeSelection.EMPTY.equals(StructuredViewer.EMPTY) == true
|
2009-02-12 04:22:27
| 1,234,430,000 |
resolved fixed
|
e019dd2
| 1,236,390,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeSelection.java
|
Eclipse_Platform_UI
|
2,000 | 264,039 |
Bug 264039 [Wizards] Selecting a project type in the New > Other dialog resizes the list box and obscures the selected item
| null |
2009-02-07 10:43:20
| 1,234,020,000 |
resolved fixed
|
c50150b
| 1,236,390,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/NewWizardNewPage.java
|
Eclipse_Platform_UI
|
2,001 | 259,952 |
Bug 259952 [Preferences] Duplicated text when using tooltip in BooleanFieldEditor
|
Build ID: M20080911-1700 Steps To Reproduce: 1. Set a tooltip to the field: bfe.getLabelControl(parent).setToolTipText(tooltipText); 2. When the preference page is shown, the text that describes the preference being edited appears duplicated. More information: The usual way to set the tool tip to a field editor is calling "getLabelControl(parent).setToolTipText(tooltipText)", but in the BooleanFieldEditor this creates a Label that is not needed (when using the BooleanFieldEditor.DEFAULT style), which makes the textual description be shown twice, in the Checkbox control, and in the (unnecessary) Label control. One solution for this issue would be to turn the method "BooleanFieldEditor.getChangeControl()" to be public instead of protected. This way one could set the tool tip directly in the checkbox Button control.
|
2009-01-05 09:28:26
| 1,231,170,000 |
resolved fixed
|
b239b91
| 1,236,390,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/preference/BooleanFieldEditor.java
|
Eclipse_Platform_UI
|
2,002 | 232,777 |
Bug 232777 [Viewers] ViewerDropAdapter holds currentTarget forever
|
Build ID: 3.3.2 Member currentTarget should be set to null after drop or after cancel, because it holds a domain object, which can't be garbage collected after Viewer.setInput(null).
|
2008-05-19 08:30:47
| 1,211,200,000 |
resolved fixed
|
2dd4c6c
| 1,236,390,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerDropAdapter.java
|
Eclipse_Platform_UI
|
2,003 | 258,679 |
Bug 258679 [Undo] NPE in OperationHistoryActionHandler$HistoryListener when deleting multiple unsaved Java editors
| null |
2008-12-12 13:11:21
| 1,229,110,000 |
verified fixed
|
196f9b2
| 1,236,390,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/operations/OperationHistoryActionHandler.java
|
Eclipse_Platform_UI
|
2,004 | 213,848 |
Bug 213848 [DataBinding] WritableSet behaves different to WritableList
|
Build ID: M20071023-1652 Steps To Reproduce: When I construct a WritableList from a List then the list is wrapped. When I do this with a Set then it is copied to a new Set and changes to the WritableSet are not reflected in the original Set anymore whiich is very nasty as one needs to copy back the writeableset. More information: public WritableSet(Realm realm, Collection c, Object elementType) { super(realm, new HashSet(c), elementType); this.elementType = elementType; } should have a constructor like public WritableSet(Realm realm, Set set, Object elementType) { super(realm, set, elementType); this.elementType = elementType; }
|
2007-12-25 11:47:46
| 1,198,600,000 |
resolved fixed
|
f224a47
| 1,236,390,000 |
bundles/org.eclipse.core.databinding.observable/src/org/eclipse/core/databinding/observable/list/WritableList.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/core/tests/databinding/observable/list/WritableListTest.java
|
Eclipse_Platform_UI
|
2,005 | 256,656 |
Bug 256656 [FieldAssist] cancel auto activation of proposal popup when caret moved
| null |
2008-11-26 10:44:36
| 1,227,710,000 |
verified fixed
|
3d43440
| 1,236,390,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
2,006 | 267,242 |
Bug 267242 [JFace] Add API to configure table and tree columns in a keyboard-accessible way
| null |
2009-03-05 13:07:29
| 1,236,280,000 |
resolved fixed
|
0e1d5a1
| 1,236,380,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/internal/ConfigureColumnsDialog.java bundles/org.eclipse.jface/src/org/eclipse/jface/util/ConfigureColumns.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/ConfigureColumnsHandler.java bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/PropertySheetPage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/AboutFeaturesPage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/AboutPluginsPage.java examples/org.eclipse.jface.snippets/Eclipse JFace Snippets/org/eclipse/jface/snippets/viewers/Snippet019TableViewerAddRemoveColumnsWithEditingNewAPI.java
|
Eclipse_Platform_UI
|
2,007 | 266,018 |
Bug 266018 ColorsAndFontsPreferencePage should set widthHint in createDescriptionControl
|
To see the current behavior, do: 1) Open Preferences Dialog 2) Select General -> Appearance -> Colors and Fonts 3) Select "View and Editor Folders" -> Part title font 4) Close Preferences Dialog 5) Open Preferences Dialog Notice that at this point the dialog has resized to be very wide. This is caused because the "Description:" text for this entry is very wide and no width hint has been provided on the text control. A simple fix would be to just set the width hint to something reasonable, but as usual it's non-trivial to figure out what that should be -- N characters? 1/4 the current Screen width?... I'll attach a patch that just sizes it based on an approx. 30 character width.
|
2009-02-24 15:13:10
| 1,235,510,000 |
resolved fixed
|
6cc1492
| 1,236,370,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/themes/ColorsAndFontsPreferencePage.java
|
Eclipse_Platform_UI
|
2,008 | 183,602 |
Bug 183602 [EditorMgmt] provide API for restoring multiple editors without materialization
| null |
2007-04-23 08:39:45
| 1,177,330,000 |
verified fixed
|
5bc5e04
| 1,236,370,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/IDE.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IWorkbenchPage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/MultiPartInitException.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/WorkbenchPage.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/api/IWorkbenchPageTest.java
|
Eclipse_Platform_UI
|
2,009 | 71,387 |
Bug 71387 [ActivityMgmt] Activity API needs to log parsing errors to workbench log
|
Malformed activity extensions currently fail silently. We need to log these failures.
|
2004-08-04 12:06:45
| 1,091,640,000 |
verified fixed
|
c34bbfe
| 1,236,370,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/activities/Persistence.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/activities/ws/ImageBindingRegistry.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/activities/ws/RegistryTriggerPoint.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/activities/ws/TriggerPointManager.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/util/ConfigurationElementMemento.java
|
Eclipse_Platform_UI
|
2,010 | 276,326 |
Bug 276326 [target] Target resolution when editing targets
|
It seems that every time a Target is edited in the preference pages there is a long (multi minute) delay while "Resolving Target Contents". It appears that several repos are being downloaded (you can see contents.jar being downloaded) and the progress seems to say that various things are being "installed". That part goes by quickly but looks like these are platform-specific fragments or some such. Note that this seems to happen similarly when opening the target editor. - p2 should be already caching and updating the repos as needed so redownloading every time the target it edited should not be needed. - The profile has all the goodies in it for the user to edit so we should not need the remote repo at all unless the user wants to add more stuff from that particular site. In general users will expect the workflows and behaviours here to be similar to that of the Install Software experience. There you can open the current profile and poke around pretty much without delay. Repos are updated as needed and loaded in the background.
|
2009-05-14 11:13:48
| 1,242,310,000 |
resolved fixed
|
26089ae
| 1,236,330,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/CommonViewer.java
|
Eclipse_Platform_UI
|
2,011 | 266,894 |
Bug 266894 [CommonNavigator] CCE thrown in CommonSorterDescriptor
| null |
2009-03-03 12:44:50
| 1,236,100,000 |
resolved fixed
|
43eb03d
| 1,236,290,000 |
bundles/org.eclipse.ui.navigator.resources/src/org/eclipse/ui/internal/navigator/resources/workbench/ResourceExtensionSorter.java
|
Eclipse_Platform_UI
|
2,012 | 266,677 |
Bug 266677 [CommonNavigator] ConcurrentModificationException when customizing view while checking out a project
|
HEAD In a clean workspace, I started to check out org.eclipse.jdt.ui.tests.refactoring from CVS. While the checkout was goin on in the background, I customized the view and only left the "Resources" content extension enabled. Clicked OK -> boom! !ENTRY org.eclipse.ui.navigator 4 0 2009-03-02 15:27:36.425 !MESSAGE java.util.ConcurrentModificationException !STACK 0 java.util.ConcurrentModificationException at java.util.HashMap$AbstractMapIterator.checkConcurrentMod(HashMap.java:123) at java.util.HashMap$AbstractMapIterator.makeNext(HashMap.java:128) at java.util.HashMap$KeyIterator.next(HashMap.java:201) at org.eclipse.ui.internal.navigator.NavigatorContentService.onExtensionActivation(NavigatorContentService.java:795) at org.eclipse.ui.internal.navigator.NavigatorActivationService.notifyListeners(NavigatorActivationService.java:254) at org.eclipse.ui.internal.navigator.NavigatorActivationService.setActive(NavigatorActivationService.java:187) at org.eclipse.ui.internal.navigator.NavigatorActivationService.activateExtensions(NavigatorActivationService.java:344) at org.eclipse.ui.internal.navigator.filters.UpdateActiveExtensionsOperation.execute(UpdateActiveExtensionsOperation.java:119) at org.eclipse.ui.internal.navigator.filters.CommonFilterSelectionDialog.okPressed(CommonFilterSelectionDialog.java:231) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:87) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.navigator.filters.SelectFiltersAction.run(SelectFiltersAction.java:51) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:586) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:503) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:413) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:87) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2388) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2352) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2204) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:499) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:333) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:492) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:556) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511) at org.eclipse.equinox.launcher.Main.run(Main.java:1284) at org.eclipse.equinox.launcher.Main.main(Main.java:1260)
|
2009-03-02 09:32:47
| 1,236,000,000 |
resolved fixed
|
d57b701
| 1,236,290,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentService.java
|
Eclipse_Platform_UI
|
2,013 | 244,354 |
Bug 244354 [CommonNavigator] ProjectExplorer property page incorrectly given in the non-resource use of CN
|
The Common Navigator is automatically adaptable to an IPropertySheetPage via the TabbedPropertySheetAdapterFactory class. This is a problem. If a creator wants to have a view that provides *no* properties sheet page at all, there is currently no way to do that. If I use the "CommonNavigator" class itself, the call to getAdapter(IPropertySheetPage.class) returns the object directly, which is fine I suppose though I feel it shouldn't do this automatically. However, if I have a subclass of CommonNavigator, and specifically overwrite the getAdapter(Class) as follows: public Object getAdapter(Class clazz) { if( clazz == IPropertySheetPage.class ) return null; return super.getAdapter(clazz); } in order to specifically have NO property page, the execution goes as follows: if (sourceObject instanceof IAdaptable) { IAdaptable adaptable = (IAdaptable) sourceObject; // THIS is where it asks the view Object result = adaptable.getAdapter(adapter); if (result != null) { // Sanity-check Assert.isTrue(adapter.isInstance(result)); return result; } } // And HERE it goes and asks the platform anyway! if (!(sourceObject instanceof PlatformObject)) { Object result; if (activatePlugins) { result = Platform.getAdapterManager().loadAdapter(sourceObject, adapter.getName()); } else { result = Platform.getAdapterManager().getAdapter(sourceObject, adapter); } This leads to an error later on in, specifically a very very cryptic error in the TabbedPropertyRegistry class complaining that I did not provide any categories. The exact error is "Contributor org.jboss.ide.eclipse.archives.ui.ProjectArchivesView cannot be created. An exception stack trace is not available." This took a decently long time to debug, actually. I suggest that this automatic adaptability be removed from the framework and instead be embedded in the CommonNavigator.getAdapter(Class clazz) code instead. This would allow subclassers the ability to *not* have a property page if they so choose and thus avoid this pretty ridiculous error. This problem can be seen in any CommonNavigator based view that does not contribute any property page data... The Data Source Explorer is one of them, and our product has two such views where this problem is seen. A patch will be attached shortly.
|
2008-08-15 20:27:53
| 1,218,850,000 |
resolved fixed
|
f0799ed
| 1,236,290,000 |
bundles/org.eclipse.ui.navigator.resources/src/org/eclipse/ui/internal/navigator/resources/workbench/TabbedPropertySheetAdapterFactory.java
|
Eclipse_Platform_UI
|
2,014 | 265,381 |
Bug 265381 [CommonNavigator] Could not acquire INavigatorContentService from part ("Welcome").
|
I20090217-2200 This error message has been seen in several Eclipse based products but the problem has nothing to do with Welcome and everything to do with the extension point org.eclipse.ui.views.properties.tabbed. To reproduce 1. Import the attached plugin into your workspace 2. Check out org.eclipse.sdk and modify plugin_customization.ini to change the default perspective using the following lines to replace the existing default perspective setting: # Property "org.eclipse.ui/defaultPerspectiveId" controls the # perspective that the workbench opens initially org.eclipse.ui/defaultPerspectiveId=org.eclipse.bugzilla.propertyperspective.perspective 3. Start a new run time workbench. Be sure to check the setting to clear theworkspace before launching. The welcome page will show. Close the welcome page by clicking on the go to workbench button. Note that there is an error message Could not acquire INavigatorContentService from part ("Welcome") in the log. The reason for this error message is that the properties view has a listener for when a part is created and if that view extends the properties view it goes through more processing which ends up in the constructor for TabbedPropertySheetTitleProvider where it calls PlatformUI.getWorkbench().getActiveWorkbenchWindow().getActivePage().getActivePart(); In this case this returns a different part to the view which was opened and an error is generated. I'm marking this as major because it has been reported several times in products which have default perspectives which contain both the properties view and project explorer.
|
2009-02-18 17:59:58
| 1,235,000,000 |
resolved fixed
|
216660e
| 1,236,290,000 |
bundles/org.eclipse.ui.navigator.resources/src/org/eclipse/ui/internal/navigator/resources/workbench/TabbedPropertySheetTitleProvider.java
|
Eclipse_Platform_UI
|
2,015 | 150,626 |
Bug 150626 [Import/Export] Create working sets when importing several projects.
|
Hi, During import of team project sets, it is possible to define a new working set. A similar option should be available for importing already existing projects from a local filesystems or archives.
|
2006-07-14 05:08:11
| 1,152,870,000 |
verified fixed
|
d6c05f4
| 1,236,280,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/wizards/datatransfer/WizardProjectsImportPage.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/wizards/datatransfer/ExternalProjectImportWizard.java
|
Eclipse_Platform_UI
|
2,016 | 221,977 |
Bug 221977 [IDE] [RCP] Use of Project Explorer in RCP requires internal IDE class WorkbenchAdapterBuilder
|
The magic incantation to get an RCP application working with resources and the CommonNavigator (or ResourceNavigator) is to call: WorkbenchAdapterBuilder.registerAdapters() However, this is an internal IDE class. If you don't call it, the CNF will fail in hard to diagnose ways (because there is no UndoRedo handler for example. In my conversations with Paul he is saying that the point of the IDE plugin is to be essentially the UI for resources and nothing more, that all of the "more" stuff is being moved to ui.ide.application. So if that's the case, then we probably just need to move this method to the API and prominently document it's requirement with the CNF/ResourceNavigator. And keep working on moving non-resource stuff out of the ui.ide plugin. And recommend that if you want to use the CNF (with resources) that you need: ui.navigator ui.navigator.resources core.resources ui.ide Alternatively, we can move the classes that are in ui.internal.ide.model to perhaps ui.navigator.resources. And then remove the dependency on ui.ide. I remain confused as to why there are two different plugins required to address the UI requirements for the CNF + resources, ui.navigator.resources and ui.ide. (I understand this might be some kind of legacy requirement).
|
2008-03-08 23:26:16
| 1,205,040,000 |
verified fixed
|
b3725b1
| 1,236,270,000 |
bundles/org.eclipse.ui.ide.application/src/org/eclipse/ui/internal/ide/application/IDEWorkbenchAdvisor.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/IDE.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/model/StandardPropertiesAdapterFactory.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/model/WorkbenchAdapterBuilder.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/model/WorkbenchAdapterFactory.java
|
Eclipse_Platform_UI
|
2,017 | 265,813 |
Bug 265813 [StatusHandling]Reduce the incompatibility between status dialog and jface ErrorDialog
| null |
2009-02-23 07:07:20
| 1,235,390,000 |
resolved fixed
|
4a1604c
| 1,236,250,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/statushandlers/WorkbenchStatusDialogManager.java
|
Eclipse_Platform_UI
|
2,018 | 243,165 |
Bug 243165 [ErrorHandling] [StatusHandling] Fatal error appears twice when reported from JOB
|
When a job reports fatal error (f.e. OutOfMemoryException) it is reported twice (and the window prompting the user to close the workbench appears). I have investigated that it is reported directly once in ProgressManager internal listener done method, and the second report is picked from log via StatusManager StatusManagerLogListener.
|
2008-08-05 10:07:02
| 1,217,950,000 |
resolved fixed
|
ad5735e
| 1,236,240,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchErrorHandler.java
|
Eclipse_Platform_UI
|
2,019 | 266,862 |
Bug 266862 [CommonNavigator] Unused copy of QuickMenuAction in common navigator
| null |
2009-03-03 10:03:00
| 1,236,090,000 |
verified fixed
|
10865b7
| 1,236,210,000 |
bundles/org.eclipse.ui.navigator.resources/src/org/eclipse/ui/internal/navigator/resources/actions/QuickMenuAction.java
|
Eclipse_Platform_UI
|
2,020 | 255,793 |
Bug 255793 [CommonNavigator] [CNF] Chosen label provider should match content provider
|
Build ID: I20080918-0100 Steps To Reproduce: 1. Create 2 "org.eclipse.ui.navigator.navigatorContent" extension to provide "similar" content but needed to show different "labels" 2. Your trigger points will indicate "which types of nodes in the tree might be interesting to our extension"(M. Elder) 3. Implement your 2 content providers with the ITreePathContentProvider and use that to find out if you should provide content based on the initial content "root" of your extension point. Otherwise the content here should be the same (for the test) 4. Code your label provider to return different text/images for the same content 4. Run you explorer 5. You will notice that the content will end up coming from one label provider for both extension point. More information: In the NavigatorServiceContentLabelProvider, in the getStyledText(Object anElement) method, the label provider is determined from all the content provider with possible children and the first to return a label "wins" the race. The problem is that we define an extension point with a pair of provider (content and label) that are both required and thus would be expected to work in tandem. Here the first selected label provider will get the object and since it is one that it understands it will return a label for it. There is no way for this provider to know where the object is in the tree or who provided content for it. The label provider is a very focused class related to its content provider and responsible only to provide labels for such content. The CNF should keep track of which provider provided each element of content in the tree and delegate the label request to its paired label provider. There is no need to go around label providers to see who wants what. By definition from the extension point, content and label are required and paired.
|
2008-11-19 09:13:57
| 1,227,100,000 |
resolved fixed
|
5a012d5
| 1,236,210,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/ContributorTrackingSet.java 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/extensions/NavigatorContentExtension.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/SafeDelegateTreeContentProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/CommonViewer.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/CommonViewerSorter.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/LabelProviderTest.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/NavigatorTestBase.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/SorterTest.java
|
Eclipse_Platform_UI
|
2,021 | 267,080 |
Bug 267080 Bring the compatibility layer back in line with the new workbench code
|
The compatibility 'product' needs to upgrade to use the new 'org.eclipse.e4.ui.workbench.swt.application' as its base. It also needs to add the WBW's shell to the localContext.
|
2009-03-04 14:12:23
| 1,236,190,000 |
resolved fixed
|
312fc47
| 1,236,190,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/WBPartFactory.java
|
Eclipse_Platform_UI
|
2,022 | 162,102 |
Bug 162102 [Workbench] User configurability for MAX_RECENT_WORKSPACES
|
MAX_RECENT_WORKSPACES=5 from org.eclipse.ui.ide.prefs needs to have an easier interface to change this value. It is obscured from users who need more then 5 workspaces.
|
2006-10-24 12:00:17
| 1,161,710,000 |
verified fixed
|
59da66d
| 1,236,190,000 |
bundles/org.eclipse.ui.ide.application/src/org/eclipse/ui/internal/ide/application/dialogs/IDEStartupPreferencePage.java bundles/org.eclipse.ui.ide.application/src/org/eclipse/ui/internal/ide/application/dialogs/RecentWorkspacesPreferencePage.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/ChooseWorkspaceData.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/IWorkbenchHelpContextIds.java
|
Eclipse_Platform_UI
|
2,023 | 266,295 |
Bug 266295 [Contributions] ShowInContext.getSelection() should only be called when needed
|
I20090224-0800, but like that since at least R3.3. For some editors computing the selection for the ShowInContext can be expensive, e.g. the Java editor needs to reconcile the Java Model with the current document state. For that reason the selection should only be queried when the ShowIn menu is opened or the ShowIn handler called. Currently, each time a Java editor is activated it has to reconcile in the UI thread. NOTE: We could do the same for the input but given that the input of a part is already present calling getInput() should really be a NOP.
|
2009-02-26 08:28:08
| 1,235,650,000 |
verified fixed
|
3dc2300
| 1,236,180,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ShowInHandler.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ShowInMenu.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/services/WorkbenchSourceProvider.java
|
Eclipse_Platform_UI
|
2,024 | 267,021 |
Bug 267021 [DataBinding] NotUsedLocally errors in org.eclipse.core.databinding
| null |
2009-03-04 09:17:37
| 1,236,180,000 |
resolved fixed
|
d68cbcc
| 1,236,180,000 |
bundles/org.eclipse.core.databinding.property/src/org/eclipse/core/databinding/property/list/DelegatingListProperty.java bundles/org.eclipse.core.databinding.property/src/org/eclipse/core/databinding/property/map/DelegatingMapProperty.java bundles/org.eclipse.core.databinding.property/src/org/eclipse/core/databinding/property/set/DelegatingSetProperty.java bundles/org.eclipse.core.databinding.property/src/org/eclipse/core/databinding/property/value/DelegatingValueProperty.java bundles/org.eclipse.core.databinding/src/org/eclipse/core/databinding/property/list/DelegatingListProperty.java bundles/org.eclipse.core.databinding/src/org/eclipse/core/databinding/property/map/DelegatingMapProperty.java bundles/org.eclipse.core.databinding/src/org/eclipse/core/databinding/property/set/DelegatingSetProperty.java bundles/org.eclipse.core.databinding/src/org/eclipse/core/databinding/property/value/DelegatingValueProperty.java
|
Eclipse_Platform_UI
|
2,025 | 266,146 |
Bug 266146 [CSS] JUnit for: Property retrieval must check instanceof and return null
| null |
2009-02-25 10:39:07
| 1,235,580,000 |
resolved fixed
|
9ffb05c
| 1,236,140,000 |
tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/ButtonTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/CSSTestCase.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/CTabFolderTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/CssSwtTestSuite.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/IdClassLabelColorTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/LabelTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/ShellTest.java
|
Eclipse_Platform_UI
|
2,026 | 186,025 |
Bug 186025 [Viewers] Virtual Manager should be cleared when Viewer is disposed
|
Got a nasty memory leak where the Workbench would keep my disposed viewer in a field since it was registered as a selection provider. In StructuredViewer#handleDisposed(), the input is set to null, however this does not clear a possible virtual manager being used from the Table Viewer. The Table Viewer should clear the cache of the virtual manager on handleDispose to make sure, no reference to any model object is retained.
|
2007-05-08 15:48:07
| 1,178,650,000 |
resolved fixed
|
f9993d6
| 1,236,140,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractTableViewer.java
|
Eclipse_Platform_UI
|
2,027 | 255,849 |
Bug 255849 [Metadata] Wrong types and methods used in org.eclipse.ui.workbench
|
That bundle is supposed to be Foundation 1.0 compliant according to the 3.4 plan. Maybe this has changed for 3.5. The EEs defined for this project are: Bundle-RequiredExecutionEnvironment: J2SE-1.4, CDC-1.0/Foundation-1.0, J2SE-1.3 And for the compilation, pde.build ends up taking the first execution environment which is 1.4. If pde.build would take the latest execution environment, it would not compile. The bundle execution environment should be changed to 1.4 or some type references and method calls should be removed. Here is the list of possible problematic references found by the new validation from api tooling: - java.lang.String.replaceAll(String, String) - java.util.regex.Pattern and its methods - java.lang.StringBuffer.append(StringBuffer) - java.lang.String.split(String) - RuntimeException(Throwable) - Error(Throwable) - java.lang.Throwable.initCause(Throwable) - java.util.regex.Matcher and its methods - javax.swing.SwingUtilities - java.awt.KeyboardFocusManager - javax.swing.FocusManager - java.lang.Throwable.getStackTrace() - java.lang.StackTraceElement.toString() Let me know if any of these references is considered to be fine. Here is the complete list that let you know in what types the references were found: The method java.lang.String.replaceAll(String, String) referenced in org.eclipse.ui.activities.ActivityCategoryPreferencePage$AdvancedDialog is not defined in bundle's required execution environment: J2SE-1.3 The type java.util.regex.Pattern referenced in org.eclipse.ui.activities.IActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.StringBuffer.append(StringBuffer) referenced in org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$ItemsListLabelProvider is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.StringBuffer.append(StringBuffer) referenced in org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$ItemsListLabelProvider is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.String.replaceAll(String, String) referenced in org.eclipse.ui.dialogs.SearchPattern is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.String.split(String) referenced in org.eclipse.ui.dialogs.WorkingSetConfigurationBlock is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.String.split(String) referenced in org.eclipse.ui.dialogs.WorkingSetConfigurationBlock is not defined in bundle's required execution environment: J2SE-1.3 The constructor RuntimeException(Throwable) referenced in org.eclipse.ui.internal.ExceptionHandler is not defined in bundle's required execution environment: J2SE-1.3 The constructor RuntimeException(Throwable) referenced in org.eclipse.ui.internal.StartupThreading is not defined in bundle's required execution environment: J2SE-1.3 The constructor Error(Throwable) referenced in org.eclipse.ui.internal.Workbench is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.Throwable.initCause(Throwable) referenced in org.eclipse.ui.internal.about.AboutBundleData is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.Throwable.initCause(Throwable) referenced in org.eclipse.ui.internal.about.AboutBundleData is not defined in bundle's required execution environment: J2SE-1.3 The type java.util.regex.Pattern referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The method java.util.regex.Pattern.compile(String) referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The method java.util.regex.Pattern.compile(String) referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The type java.util.regex.Pattern referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The method java.util.regex.Pattern.pattern() referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The method java.util.regex.Pattern.pattern() referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The type java.util.regex.Pattern referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The method java.util.regex.Pattern.compile(String) referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The method java.util.regex.Pattern.pattern() referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The method java.util.regex.Pattern.matcher(CharSequence) referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The method java.util.regex.Matcher.matches() referenced in org.eclipse.ui.internal.activities.ActivityPatternBinding is not defined in bundle's required execution environment: J2SE-1.3 The type java.util.regex.Pattern referenced in org.eclipse.ui.internal.activities.MutableActivityManager is not defined in bundle's required execution environment: J2SE-1.3 The type javax.swing.SwingUtilities referenced in org.eclipse.ui.internal.handlers.WidgetMethodHandler is not defined in bundle's required execution environment: CDC-1.0/Foundation-1.0 The type java.awt.KeyboardFocusManager referenced in org.eclipse.ui.internal.handlers.WidgetMethodHandler is not defined in bundle's required execution environment: J2SE-1.3 The type javax.swing.FocusManager referenced in org.eclipse.ui.internal.handlers.WidgetMethodHandler is not defined in bundle's required execution environment: CDC-1.0/Foundation-1.0 The method java.lang.Throwable.getStackTrace() referenced in org.eclipse.ui.internal.statushandlers.StackTraceSupportArea is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.StackTraceElement.toString() referenced in org.eclipse.ui.internal.statushandlers.StackTraceSupportArea is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.Throwable.getCause() referenced in org.eclipse.ui.internal.statushandlers.StackTraceSupportArea is not defined in bundle's required execution environment: J2SE-1.3 The method java.lang.Throwable.getCause() referenced in org.eclipse.ui.internal.statushandlers.StackTraceSupportArea is not defined in bundle's required execution environment: J2SE-1.3
|
2008-11-19 13:26:40
| 1,227,120,000 |
resolved fixed
|
5242cab
| 1,236,130,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/activities/ActivityCategoryPreferencePage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/SearchPattern.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/WorkingSetConfigurationBlock.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/plugin/AbstractUIPlugin.java
|
Eclipse_Platform_UI
|
2,028 | 266,958 |
Bug 266958 [CSS] Add ToolBar to SWT example
|
We need a ToolBar as part of the SWT example so we can explore styling it.
|
2009-03-03 21:04:34
| 1,236,130,000 |
resolved fixed
|
0eb5e98
| 1,236,130,000 |
examples/org.eclipse.e4.ui.examples.css/src/org/eclipse/e4/ui/examples/css/editor/CSSEditorSWTWidgets.java
|
Eclipse_Platform_UI
|
2,029 | 266,177 |
Bug 266177 [About] selecting a tree element and hitting CTRL+A results in NPE
|
eclipse.buildId=I20090224-0800 java.fullversion=J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20080315 (JIT enabled) J9VM - 20080314_17962_lHdSMr JIT - 20080130_0718ifx2_r8 GC - 200802_08 BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 -data /opt/pwebster/workspaces/e4 Error Wed Feb 25 13:01:44 EST 2009 Unhandled event loop exception java.lang.NullPointerException at org.eclipse.ui.internal.about.AboutFeaturesPage$2.widgetSelected(AboutFeaturesPage.java:270) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1161) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1185) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1170) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1010) at org.eclipse.ui.internal.handlers.SelectAllHandler.execute(SelectAllHandler.java:135) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:471) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:823) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:879) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:570) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:511) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:126) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1466) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1160) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1185) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1170) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1197) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:699) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2782) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:702) at org.eclipse.swt.widgets.Table.gtk_key_press_event(Table.java:1911) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1546) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4523) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4175) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:7534) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1184) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1850) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3094) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.AboutDialog$1.run(AboutDialog.java:125) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.dialogs.AboutDialog.buttonPressed(AboutDialog.java:121) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:625) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1161) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3477) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3096) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.about.AboutHandler.execute(AboutHandler.java:32) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1161) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3477) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3096) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2388) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2352) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2204) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:499) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:333) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:492) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:556) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511) at org.eclipse.equinox.launcher.Main.run(Main.java:1284)
|
2009-02-25 13:03:06
| 1,235,590,000 |
verified fixed
|
dd698b3
| 1,236,120,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/AboutFeaturesPage.java
|
Eclipse_Platform_UI
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.