id
int64 1
6.5k
| bug_id
int64 2.03k
426k
| summary
stringlengths 9
251
| description
stringlengths 1
32.8k
⌀ | report_time
stringlengths 19
19
| report_timestamp
int64 1B
1.39B
| status
stringclasses 6
values | commit
stringlengths 7
9
| commit_timestamp
int64 1B
1.39B
| files
stringlengths 25
32.8k
| project_name
stringclasses 6
values |
|---|---|---|---|---|---|---|---|---|---|---|
3,630
| 159,159
|
Bug 159159 [Undo] - redundant/awkward warning message when rename causes overwrite
|
When renaming a resource and an overwrite will occur, the warning message dialog says "Operation Warning: Xxx will be overwritten. Proceed with "Rename" anyway? The title of the dialog is Operation Warning. Having it in the message text in addition to the title makes it harder to parse what's going on.
|
2006-09-28 13:44:12
| 1,159,470,000
|
verified fixed
|
92067e5
| 1,159,470,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/operations/AdvancedValidationUserApprover.java
|
Eclipse_Platform_UI
|
3,631
| 158,973
|
Bug 158973 [Markers] All labels in tasks and breakpoints views are bold
|
I20060926 We are applying the bold font to everything in the tasks and breakpoints view
|
2006-09-27 10:51:32
| 1,159,370,000
|
verified fixed
|
d3c7948
| 1,159,380,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerViewLabelProvider.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/TableView.java
|
Eclipse_Platform_UI
|
3,632
| 158,791
|
Bug 158791 [EditorMgmt] NPE in NavigationHistoryAction.update
| null |
2006-09-26 12:00:55
| 1,159,290,000
|
verified fixed
|
c5e4d49
| 1,159,370,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/NavigationHistory.java
|
Eclipse_Platform_UI
|
3,633
| 158,959
|
Bug 158959 [Viewers] testRefreshBug141435 and testNoSelectionRefresh failing on N20060927-0010
| null |
2006-09-27 08:22:27
| 1,159,360,000
|
verified fixed
|
8aed502
| 1,159,360,000
|
tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ListViewerRefreshTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ListViewerTest.java
|
Eclipse_Platform_UI
|
3,634
| 156,674
|
Bug 156674 QuickAccess popup: remembering size and position does not work
|
I20060906-1200 QuickAccess (Ctrl+E) popup: remembering size and position does not work. - The state of the menu 'Remember Size an Postion' is always checked when the dialog comes up, even after I've switched it off - The position and size of the dialog is not remembered
|
2006-09-08 05:46:30
| 1,157,710,000
|
verified fixed
|
3ef06ba
| 1,159,300,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/incubator/CtrlEAction.java
|
Eclipse_Platform_UI
|
3,635
| 156,672
|
Bug 156672 QuickAccess command should appear in menu Window > Navigation
|
I20060906-1200 The new QuickAccess command (Ctrl+E, 'Window > QuickAccess' on Keys preference page) should appear in the menu 'Window > Navigation'. Furthermore, it's rather uncommon in Eclipse to use CamelCase command names. I would suggest to rename the command to 'Quick Access'.
|
2006-09-08 05:43:25
| 1,157,710,000
|
verified fixed
|
416853f
| 1,159,300,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/WorkbenchActionBuilder.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/actions/ActionFactory.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/QuickAccessMenu.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchMessages.java
|
Eclipse_Platform_UI
|
3,636
| 109,528
|
Bug 109528 [RCP] [Workbench] Eclipse automatically attempts to save modified files when OutOfMemoryException occurs
|
We need a way to know if the workbench is closing because of an exception (such as OutOfMemoryError), since we want to change our save behaviour in that case to *not* save over the original file (Eclipse's default 'emergency close' behaviour), but to save to a temporary file instead. It seems that all access points to IWorkbenchConfigurer are blocked off (default/private access).
|
2005-09-14 14:38:47
| 1,126,720,000
|
verified fixed
|
640889c
| 1,159,300,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Workbench.java
|
Eclipse_Platform_UI
|
3,637
| 158,016
|
Bug 158016 [Perspectives] GDI leak: Each time you create a perspective switcher an image is leaked
|
To recreate. Open a new perspective and close it. Notice your GDIs increase by 1 each time you do this. The PerspectiveSwitcher creates a PerspectiveBarManager but doesn't dispose it. The PerspectiveBarNewContributionItem does implement a dispose() method that does the right thing, but the method is never called. The following patch disposes the PerspectiveBarManager when the PerspectiveSwitcher is disposed.
|
2006-09-20 11:59:31
| 1,158,770,000
|
resolved fixed
|
f4d79be
| 1,159,300,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PerspectiveSwitcher.java
|
Eclipse_Platform_UI
|
3,638
| 141,435
|
Bug 141435 [Viewers] ListViewer without a selection loses scrolled state when refreshed
|
When the ListViewer does not contain a selection and is refreshed it loses its vertically scrolled to position. This is because AbstractListViewer removes all items and adds them back (it has to) when a refresh occurs. This is remedied in the use cases where there is a selection because the selected item is revealed after the refresh occurs. Without a selection no reveal can occur therefore it loses its position.
|
2006-05-11 17:05:08
| 1,147,380,000
|
resolved fixed
|
266b326
| 1,159,290,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractListViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ListViewer.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/AllTests.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ListViewerRefreshTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ListViewerTest.java
|
Eclipse_Platform_UI
|
3,639
| 137,435
|
Bug 137435 [DataBinding] IdentityWrapper violates requirements for equals
| null |
2006-04-19 02:12:24
| 1,145,430,000
|
resolved fixed
|
fbc1c53
| 1,159,290,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/internal/IdentityWrapper.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/internal/beans/ListenerSupport.java
|
Eclipse_Platform_UI
|
3,640
| 134,856
|
Bug 134856 [DataBinding] ValueDiff overrides Object.equals(Object) but not Object.hashCode()
|
The javadoc for Object.hashCode() states: "If two objects are equal according to the <tt>equals(Object)</tt> method, then calling the <code>hashCode</code> method on each of the two objects must produce the same integer result." The other IDiff implementations don't override Object.equals(Object) so I assume ValueDiff shouldn't either.
|
2006-04-04 16:07:32
| 1,144,180,000
|
resolved fixed
|
387e1e2
| 1,159,290,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/databinding/observable/value/ValueDiff.java
|
Eclipse_Platform_UI
|
3,641
| 152,543
|
Bug 152543 [DataBinding] ValueBinding NPE when update target from model is false
|
When a ValueBinding is constructed and instructed not to update the target from the model via the BindSpec a NPE is thrown when it tries to access the modelToTargetConverter. Exception in thread "main" java.lang.NullPointerException at org.eclipse.jface.internal.databinding.internal.ValueBinding.doUpdateTargetFromModel(ValueBinding.java:268) at org.eclipse.jface.internal.databinding.internal.ValueBinding.updateTargetFromModel(ValueBinding.java:250) at org.eclipse.jface.internal.databinding.internal.ValueBinding.<init>(ValueBinding.java:112) at Snippet.main(Snippet.java:32) Attaching patch...
|
2006-08-01 22:56:04
| 1,154,490,000
|
resolved fixed
|
4b0d1ff
| 1,159,280,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/internal/ValueBinding.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/BindingTestSuite.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/internal/databinding/internal/ValueBindingTest.java
|
Eclipse_Platform_UI
|
3,642
| 158,687
|
Bug 158687 [Databinding] WritableValue throws ValueChange events when a change has not occurred
|
WritableValue currently throws a ValueChange event anytime the value is set rather than just when the value changes. Attaching patch...
|
2006-09-25 23:21:32
| 1,159,240,000
|
verified fixed
|
c3b9e14
| 1,159,280,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/databinding/observable/value/WritableValue.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/BindingTestSuite.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/observable/value/WritableValueTest.java
|
Eclipse_Platform_UI
|
3,643
| 158,606
|
Bug 158606 make BaseLabelProvider public
| null |
2006-09-25 13:16:07
| 1,159,200,000
|
verified fixed
|
856023a
| 1,159,210,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/BaseLabelProvider.java
|
Eclipse_Platform_UI
|
3,644
| 90,170
|
Bug 90170 [Dialogs] CamelCase search on OpenResource/OpenType
| null |
2005-04-04 11:18:25
| 1,112,630,000
|
verified fixed
|
ae3d354
| 1,159,200,000
|
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/dialogs/ResourceSearcher.java bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/utils/ResourceSearchItem.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/AbstractSearcher.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/CharOperation.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/SearchPattern.java
|
Eclipse_Platform_UI
|
3,645
| 157,805
|
Bug 157805 [Workbench] Add Hide Toolbars to the Window menu
| null |
2006-09-19 09:28:30
| 1,158,670,000
|
verified fixed
|
852e30f
| 1,159,200,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/WorkbenchActionBuilder.java
|
Eclipse_Platform_UI
|
3,646
| 157,981
|
Bug 157981 Open resource dialog: Missing colons in labels
|
M2 - Navigate > Open Resource - Both labels need a colon(':') at the end and mnemonics
|
2006-09-20 09:15:05
| 1,158,760,000
|
verified fixed
|
b8407c2
| 1,159,200,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/AbstractSearchDialog.java
|
Eclipse_Platform_UI
|
3,647
| 158,204
|
Bug 158204 [Decorators] DecorationScheduler hangs on to listeners for too long
|
3.2 I have a case where an editor I'm implementing is not freed up properly when closed. In YourKit, it shows that it's being held onto via a label provider changed listener hooked on the decorator manager. In DecorationScheduler, it grabs the array of listeners from the manager, then iterates over them in the update job. At the end, though, it's left hanging on to the original array of listeners. The array should get nulled out at the end to drop these references. Suggested patch is to replace: labelProviderChangedEvent = null; removedListeners.clear(); with: labelProviderChangedEvent = null; removedListeners.clear(); listeners = null; in getUpdateJob() Also noticed a possible optimization: DecoratorManager.getListeners() does not need to take a copy of the array from listeners.getListeners(), since this is spec'ed to not be affected by subsequent add/removes.
|
2006-09-21 15:19:37
| 1,158,870,000
|
verified fixed
|
b543fc1
| 1,159,200,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/decorators/DecorationScheduler.java
|
Eclipse_Platform_UI
|
3,648
| 158,020
|
Bug 158020 Lazy initialize ViewerComparator.comparator
|
20060920 In the ViewerSorter I remember that a performance problem was that that the default constructor called Collator.getInstance() which can be expensive for the first caller. So in JDT we overrode getCollator() to do a lazy initialization. Couldn't this be added to the ViewerComparator by default? In ViewerSorter it wasn't possible as collator was protected. In ViewerComparator this isn't a problem. -> public ViewerComparator(){ this(null); } protected Comparator getComparator() { if (comparator == null) comparator= Policy.getComparator(); return comparator; }
|
2006-09-20 12:40:13
| 1,158,770,000
|
verified fixed
|
653622c
| 1,159,200,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerComparator.java
|
Eclipse_Platform_UI
|
3,649
| 157,793
|
Bug 157793 [PropertiesDialog] 'Resource' and 'Project References' property page fail if modifying closed project
|
I20060919-0010. The 'Resource' and the 'Project References' property page fail if modifying closed project 1. create a simple project and close it 2. context menu > Properties 3. change some preferences (e.g. the encoding) 4. click OK ==> !ENTRY org.eclipse.core.resources 4 4 2006-09-19 14:27:10.024 !MESSAGE Exception occurred while saving project preferences: /Simple Closed/.settings/org.eclipse.core.runtime.prefs. !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/Simple Closed' is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:145) at org.eclipse.core.internal.resources.Folder.assertCreateRequirements(Folder.java:32) at org.eclipse.core.internal.resources.Folder.create(Folder.java:88) at org.eclipse.core.internal.resources.ProjectPreferences$2.run(ProjectPreferences.java:551) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737) at org.eclipse.core.internal.resources.ProjectPreferences.save(ProjectPreferences.java:566) at org.eclipse.core.internal.preferences.EclipsePreferences.flush(EclipsePreferences.java:352) at org.eclipse.core.internal.resources.ProjectPreferences.flush(ProjectPreferences.java:364) at org.eclipse.ui.internal.ide.LineDelimiterEditor.store(LineDelimiterEditor.java:270) at org.eclipse.ui.internal.ide.dialogs.ResourceInfoPage.performOk(ResourceInfoPage.java:569) at org.eclipse.jface.preference.PreferenceDialog$11.run(PreferenceDialog.java:889) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:850) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:869) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:377) at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:230) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:638) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3390) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3009) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:156) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3390) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3009) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:348) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:165) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:341) at org.eclipse.core.launcher.Main.basicRun(Main.java:285) at org.eclipse.core.launcher.Main.run(Main.java:987) at org.eclipse.core.launcher.Main.main(Main.java:962) !SUBENTRY 1 org.eclipse.core.resources 4 372 2006-09-19 14:27:10.024 !MESSAGE Resource '/Simple Closed' is not open. !ENTRY org.eclipse.ui.ide 4 4 2006-09-19 14:27:10.034 !MESSAGE Exception occurred while saving project preferences: /Simple Closed/.settings/org.eclipse.core.runtime.prefs. !ENTRY org.eclipse.ui.ide 4 4 2006-09-19 14:27:10.034 !MESSAGE Exception occurred while saving project preferences: /Simple Closed/.settings/org.eclipse.core.runtime.prefs. !STACK 0 org.osgi.service.prefs.BackingStoreException: Exception occurred while saving project preferences: /Simple Closed/.settings/org.eclipse.core.runtime.prefs. at org.eclipse.core.internal.resources.ProjectPreferences.save(ProjectPreferences.java:574) at org.eclipse.core.internal.preferences.EclipsePreferences.flush(EclipsePreferences.java:352) at org.eclipse.core.internal.resources.ProjectPreferences.flush(ProjectPreferences.java:364) at org.eclipse.ui.internal.ide.LineDelimiterEditor.store(LineDelimiterEditor.java:270) at org.eclipse.ui.internal.ide.dialogs.ResourceInfoPage.performOk(ResourceInfoPage.java:569) at org.eclipse.jface.preference.PreferenceDialog$11.run(PreferenceDialog.java:889) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:850) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:869) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:377) at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:230) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:638) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3390) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3009) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:156) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3390) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3009) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:348) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:165) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:341) at org.eclipse.core.launcher.Main.basicRun(Main.java:285) at org.eclipse.core.launcher.Main.run(Main.java:987) at org.eclipse.core.launcher.Main.main(Main.java:962)
|
2006-09-19 08:25:42
| 1,158,670,000
|
verified fixed
|
ec673df
| 1,159,200,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/dialogs/ResourceEncodingFieldEditor.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/LineDelimiterEditor.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ProjectReferencePage.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceInfoPage.java
|
Eclipse_Platform_UI
|
3,650
| 156,775
|
Bug 156775 Allow fonts to benefit from ResourceManager
|
Eclipse 3.x added a lot of features for manipulating ImageDescriptors and managing them through ResourceManager. Currently, it is cumbersome to do the same thing with Fonts, so most people are still using global Font registry. This enhancement requests that we add features to make Fonts as easy to manage as Images are. - FontDescriptors are provided globally - FontDescriptors are easy to manipulate - Concrete fonts are obtained from the FontDescriptors via a ResourceManager as needed - Fonts benefit from reference-counted shared allocations just like Images do. The attached patch adds the following enhancements for Font management. New Features: 1. (feature) Add helper methods to FontDescriptor to allow font size and style to be set without packing and unpacking the FontData. 2. (performance) Add a getFontData() method to FontDescriptor, to make it possible to manipulate font descriptors without creating a concrete Fonts. 3. (cleanup) Remove NamedFontDescriptor, and replace it with (the more general) ArrayFontDescriptor. 4. (performance) Refactor FontRegistry to use the ResourceManager tree in order to benefit from shared allocations (like Images currently do). 5. (feature) Wherever there is a prominent method that returns a global Font, provide a version that returns a FontDescriptor. Refactor where necessary such that a concrete Font won't be allocated as long as clients are only calling the descriptor version.
|
2006-09-08 18:13:59
| 1,157,750,000
|
verified fixed
|
a68d400
| 1,159,190,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/resource/ArrayFontDescriptor.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/FontDescriptor.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/FontRegistry.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/JFaceResources.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/NamedFontDescriptor.java
|
Eclipse_Platform_UI
|
3,651
| 150,593
|
Bug 150593 Enhancements for ResourceManager
|
The attached patch addresses the following in ResourceManager - Fixes several JavaDoc bugs - Adds a "getImage" method that implements the common pattern of "return existing image if known, or allocate a new image otherwise"
|
2006-07-13 22:41:46
| 1,152,840,000
|
verified fixed
|
acad313
| 1,159,190,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/resource/DeviceResourceDescriptor.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/DeviceResourceException.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/ResourceManager.java
|
Eclipse_Platform_UI
|
3,652
| 80,116
|
Bug 80116 [DynamicUI] AbstractWorkingSetManager tries to get namespace for bundles with no symbolic name
| null |
2004-12-03 11:03:39
| 1,102,090,000
|
verified fixed
|
519f85c
| 1,159,190,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/AbstractWorkingSetManager.java
|
Eclipse_Platform_UI
|
3,653
| 157,174
|
Bug 157174 [Viewers] Refactor new Viewer API
|
We are yet not completely happy with the API and refactor it.
|
2006-09-13 11:01:37
| 1,158,160,000
|
verified fixed
|
7ed3ea0
| 1,159,190,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/BaseLabelProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/CellLabelProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ColumnLabelProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ColumnViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/DecoratingLabelProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/LabelProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/OwnerDrawLabelProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableColumnViewerLabelProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ToolTipSupport.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerColumn.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerLabelProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/WrappedViewerLabelProvider.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerViewLabelProvider.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/TableView.java examples/org.eclipse.jface.snippets/Eclipse JFace Snippets/org/eclipse/jface/snippets/viewers/CustomTooltipsSnippet.java examples/org.eclipse.jface.snippets/Eclipse JFace Snippets/org/eclipse/jface/snippets/viewers/MultiLineExample.java examples/org.eclipse.jface.snippets/Eclipse JFace Snippets/org/eclipse/jface/snippets/viewers/OwnerDrawExample.java examples/org.eclipse.jface.snippets/Eclipse JFace Snippets/org/eclipse/jface/snippets/viewers/OwnerDrawLabelProvider.java
|
Eclipse_Platform_UI
|
3,654
| 157,985
|
Bug 157985 [Workbench] Add 'Hide toolbar' action to context menu
|
M2 The 'Hide toolbar' action should be added to the context menu on toolbars. That's where I first looked for it.
|
2006-09-20 09:20:23
| 1,158,760,000
|
verified fixed
|
18a6b7f
| 1,159,190,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/WorkbenchActionBuilder.java
|
Eclipse_Platform_UI
|
3,655
| 104,714
|
Bug 104714 [ActivityMgmt] Preferences/Capabilities not sorted alphabetically.
|
Preferences/Capabilities not sorted alphabetically. My plugin lauched from PDE defines a "Seagull CICS" activity. It appears 1st in the Capabilities list box, before "Development" and "Team".
|
2005-07-21 14:58:49
| 1,121,970,000
|
verified fixed
|
5dd8eb9
| 1,159,190,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/activities/ActivityCategoryPreferencePage.java
|
Eclipse_Platform_UI
|
3,656
| 158,130
|
Bug 158130 LegacyActionPersistence causing test failures on Linux with 1.5 VM
| null |
2006-09-21 07:24:36
| 1,158,840,000
|
resolved fixed
|
1ba3dd4
| 1,158,840,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/LegacyActionPersistence.java
|
Eclipse_Platform_UI
|
3,657
| 157,883
|
Bug 157883 Very long parameters in selection drop-down for new wizards
|
I20060919-0010 I was trying to find the New Plug-in Project command in the command composer. I found File -> New but when I go to select the New Wizard parameter, I get complete descriptions of the wizards, each on a single line, as opposed to just the names. Is there any way we can just show the name of the new wizard? See screenshot to follow.
|
2006-09-19 14:29:39
| 1,158,690,000
|
resolved fixed
|
0206b47
| 1,158,800,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/registry/WizardParameterValues.java
|
Eclipse_Platform_UI
|
3,658
| 157,799
|
Bug 157799 [WorkingSets] Add to working can cause stack overflow
|
I20060918 1) set the Package Explorer to show working sets as top level element 2) select a working set 3) from the add to working set drop down attempt to add it to itself. 4) Boom headshot! This is a perfect example of why we need a working set validator class that can be used to test objects before they are added to working sets. In the interim we can simply add a hack to the working set action code to check to see if an element is a working set (or adapts to one) and if so exclude it from the operation. at java.util.ArrayList.get(ArrayList.java:321) at java.util.AbstractList$Itr.next(AbstractList.java:422) at java.util.AbstractList.hashCode(AbstractList.java:629) at org.eclipse.ui.internal.WorkingSet.hashCode(WorkingSet.java:136) at java.util.AbstractList.hashCode(AbstractList.java:630) at org.eclipse.ui.internal.WorkingSet.hashCode(WorkingSet.java:136) at java.util.AbstractList.hashCode(AbstractList.java:630) at org.eclipse.ui.internal.WorkingSet.hashCode(WorkingSet.java:136) at java.util.AbstractList.hashCode(AbstractList.java:630) at org.eclipse.ui.internal.WorkingSet.hashCode(WorkingSet.java:136) at java.util.AbstractList.hashCode(AbstractList.java:630) at org.eclipse.ui.internal.WorkingSet.hashCode(WorkingSet.java:136) at java.util.AbstractList.hashCode(AbstractList.java:630) at org.eclipse.ui.internal.WorkingSet.hashCode(WorkingSet.java:136)
|
2006-09-19 09:07:57
| 1,158,670,000
|
verified fixed
|
f7855d2
| 1,158,780,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/actions/ModifyWorkingSetDelegate.java
|
Eclipse_Platform_UI
|
3,659
| 157,633
|
Bug 157633 WorkbenchOperationStressTests takes a long time
|
WorkbenchOperationStressTests takes 82 seconds to run which is making it quite long to run the UI test suites
|
2006-09-18 10:04:52
| 1,158,590,000
|
verified fixed
|
87c2ab5
| 1,158,600,000
|
tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/operations/WorkbenchOperationStressTests.java
|
Eclipse_Platform_UI
|
3,660
| 157,566
|
Bug 157566 [Viewers] Application doesn't shutdown because background thread is running
|
This really a critical bug which should be fixed before M2 is out. In ToolTipSupport a Timer thread is started and never cancled if tooltips are not used!
|
2006-09-16 07:57:02
| 1,158,410,000
|
verified fixed
|
1ce9663
| 1,158,580,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ToolTipSupport.java
|
Eclipse_Platform_UI
|
3,661
| 157,309
|
Bug 157309 [Viewers] ListViewer should provide insert-method
|
TableViewer and TreeViewers provide methods to insert a model element and so should ListViewer
|
2006-09-14 09:45:58
| 1,158,240,000
|
verified fixed
|
6b8b013
| 1,158,270,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractListViewer.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ListViewerTest.java
|
Eclipse_Platform_UI
|
3,662
| 124,338
|
Bug 124338 [Dialogs] ResourceSelectionDialog should allow to implement custom acceptance criteria
|
I suggest to refactor ResourceSelectionDialog so there will be methods to access checked items and enable OK button respectively. This should allow to implement custom strategy to accept selected elements.
|
2006-01-18 12:40:24
| 1,137,610,000
|
verified fixed
|
10a9487
| 1,158,240,000
|
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/dialogs/ResourceSearchDialog.java bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/dialogs/ResourceSearcher.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/AbstractSearchDialog.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/AbstractSearchItem.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/AbstractSearcher.java
|
Eclipse_Platform_UI
|
3,663
| 156,864
|
Bug 156864 [Undo] Edit > Add Bookmark... does not work
|
I20060906-1200 1. start fresh workspace 2. create simple project P 3. create simple file f 4. close the editor (the editor actions works) 5. Edit > Add Bookmark... ==> bookmark is not added
|
2006-09-11 08:51:24
| 1,157,980,000
|
verified fixed
|
967264d
| 1,158,110,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/bookmarkexplorer/BookmarkPropertiesDialog.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/DialogMarkerProperties.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/DialogProblemProperties.java
|
Eclipse_Platform_UI
|
3,664
| 156,865
|
Bug 156865 Undo / Redo marker actions not updated
|
I20060906-1200 If a file gets delete after adding/changing/removing a marker then the Undo and Redo actions are not updated and still show, e.g. Undo Add Task Redo Add Task Executing the undo or redo does nothing (no feedback, no .log entry) and the undo and redo menu text remains the same and enabled.
|
2006-09-11 08:56:07
| 1,157,980,000
|
verified fixed
|
713405f
| 1,158,110,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/undo/AbstractMarkersOperation.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/undo/AbstractWorkspaceOperation.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/undo/CreateMarkersOperation.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/undo/DeleteMarkersOperation.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/undo/UpdateMarkersOperation.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/undo/UndoMessages.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/operations/WorkspaceOperationsTests.java
|
Eclipse_Platform_UI
|
3,665
| 36,918
|
Bug 36918 [Working Sets] Add to / Remove from Working Set... Context Menu in Navigator and Package Explorer
|
Editing working sets in large projects is painful, it would be really handy if there was a context menu in the navigator and package explorer that was something like: Working Set Add to Working Set... (add the current resource to the selected working set) Remove from Working Set (only enabled when you're in a working set)
|
2003-04-25 12:21:37
| 1,051,290,000
|
verified fixed
|
9f33443
| 1,158,090,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/actions/AbstractWorkingSetPulldownDelegate.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/actions/ModifyWorkingSetDelegate.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/actions/SelectWorkingSetsAction.java
|
Eclipse_Platform_UI
|
3,666
| 157,072
|
Bug 157072 [ActionSets][Contributions] QuickMenuAction funtionality should be made public
|
The QuickMenuAction class should be made public and usable by IWorkbenchWindowPulldownDelegate{2}. As it is you need to roll this functionality yourself in the run method of your delegate (and it is by no means straightforward).
|
2006-09-12 14:04:52
| 1,158,080,000
|
resolved fixed
|
3a3373f
| 1,158,090,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/actions/QuickMenuAction.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/actions/QuickMenuCreator.java
|
Eclipse_Platform_UI
|
3,667
| 156,747
|
Bug 156747 Adopt Resource.getDevice() in the JFace resource managers
|
SWT has recently added a Resource.getDevice() method. This allows several improvements to be made to the JFace resource managers: 1. The (inefficient and complex) heuristics that detect a device by creating temporary resources can be removed. 2. The one-argument descriptor factories that don't take a Device can be made just as efficient as the two-argument versions. 3. The descriptor factory methods that take a Device can be deprecated, since the second argument is no longer required and the one-argument version is just as efficient.
|
2006-09-08 14:16:58
| 1,157,740,000
|
verified fixed
|
73a4416
| 1,158,090,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/resource/ArrayFontDescriptor.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/ColorDescriptor.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/FontDescriptor.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/ImageDataImageDescriptor.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/ImageDescriptor.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/RGBColorDescriptor.java
|
Eclipse_Platform_UI
|
3,668
| 157,080
|
Bug 157080 releng warnings in the carbon plug-in
| null |
2006-09-12 15:04:48
| 1,158,090,000
|
verified fixed
|
5c98aa0
| 1,158,090,000
|
bundles/org.eclipse.ui.carbon/src/org/eclipse/ui/carbon/CarbonUIEnhancer.java
|
Eclipse_Platform_UI
|
3,669
| 156,544
|
Bug 156544 [Viewers] Vitrual lazy tree viewer - refreshing a node does not make it expandable
|
I20060830-1650 Using a tree viewer with the SWT.Vitrual style and an ILazyTreeContentProvider. If a node in a tree has no children in an underlying model, and then has children added to that node, calling refresh no the corresponding element does not add a "+" to the tree node. The code that does not consult the content provider for an element's child count if a tree item already has data mapped to it. Attatched is a sample plug-in showing the problem. The model changes from: root one two three to: root one a b c two three ... but the content provider is not consulted when calling refresh on "one". To see the problem, open the sample view, and invoke "Update Model" action from the context menu.
|
2006-09-07 12:01:08
| 1,157,640,000
|
verified fixed
|
879c9fa
| 1,158,060,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewer.java
|
Eclipse_Platform_UI
|
3,670
| 156,537
|
Bug 156537 [Viewers] Virtual tree viewer does not populate with initial children
|
I20060830-1650 When a tree viewer is created with the SWT.Vitrual flag and uses an ILazyTreeContentProvider, the viewew does not populate with the initial children in the model. The method TreeViewer.createChildren(Widget) only updates existing items if the parent (root)element has been mapped to data, and does not query the content provider for the number of children it has. Attached is a sample plug-in showing the problem. The tree "model" looks like this: root one two three When the input is set to the viewer ("root") a call is made to "createChildren", but the content provider is never used.
|
2006-09-07 11:43:19
| 1,157,640,000
|
resolved fixed
|
b1c152e
| 1,158,030,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractTreeViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewer.java
|
Eclipse_Platform_UI
|
3,671
| 151,205
|
Bug 151205 [Viewers] Add setFilters() to change multiple filters at once efficiently
|
When one needs to add more than one filter after every request a refresh command is issued which is not desired an API-Function where the user could control whether the refresh is called or not would be a great performance improvement.
|
2006-07-20 06:12:55
| 1,153,390,000
|
resolved fixed
|
9ad709c
| 1,158,030,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StructuredViewer.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/StructuredViewerTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/VirtualLazyTreeViewerTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/VirtualTableViewerTest.java
|
Eclipse_Platform_UI
|
3,672
| 115,789
|
Bug 115789 Memory Leak
|
I'm using org.eclipse.ui.tools.heapstatus plugin to monitor memory usage. when comparing two large (~30M) jar files (structure compare) some amount of memory is not released. after first GC it shows 23M used. after compare and GC it shows 160M used after second compare and GC it shows 296M used after third compare and GC it shows 432M used total amount 512M i'm using 1.5 to run eclipse eclipse Build id: I20050627-1435 also reproducable on 3.1.1
|
2005-11-10 05:16:38
| 1,131,620,000
|
verified fixed
|
b75cce4
| 1,158,000,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/NavigationHistory.java
|
Eclipse_Platform_UI
|
3,673
| 142,960
|
Bug 142960 Performance tweak for ignored file processing
|
Version: 3.2.0 Build id: I20060519-1206 The attached patch gives a very small (3-4%) performance improvement to the creation of the list of ignored pattern matchers. This is only ever done once, but it is usually during startup where every little bit helps. Two changes were made: - Iterate on the entries of the set instead of the key to avoid a redundant lookup by key - Changed usage of Vector to ArrayList to avoid extra syncronization
|
2006-05-22 06:38:13
| 1,148,290,000
|
resolved fixed
|
3586950
| 1,158,000,000
|
tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ViewerComparatorTest.java
|
Eclipse_Platform_UI
|
3,674
| 156,686
|
Bug 156686 [Contributions] Evaluation context for object contributions does not allow for eager plug-in loading
|
The evaluation context created in ObjectContribution does not setAllowPluginActivation to true. This means that any test condition that does ask for plugins to be loaded will not be honoured.
|
2006-09-08 08:52:04
| 1,157,720,000
|
verified fixed
|
38adc90
| 1,157,720,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ObjectActionContributor.java
|
Eclipse_Platform_UI
|
3,675
| 155,873
|
Bug 155873 [PropertiesView] PropertySheetPage Help Integration Does Not Work In a Wizard
|
I've created a wizard page that uses a PropertySheetPage. If the PSP has focus and I press F1 to open help, a NPE occurs. The NPE occurs in the PropertySheetPage class on line 233 which is this: getSite().getWorkbenchWindow().getWorkbench().getHelpSystem().displayHelp(HELP_CONTEXT_PROPERTY_SHEET_PAGE); getSite() returns null because the PSP is not in a view. From what I can tell, getSite() is only being called to get the help system, which can be done in another way. If the help system was acquired in a different way that didn't involve getting the site I think this would work. Here's an example I tried which works: PlatformUI.getWorkbench().getHelpSystem().displayHelp(HELP_CONTEXT_PROPERTY_SHEET_PAGE); So, I think only a minor change in the eclipse UI is required to resolve the issue I have. I will attach a patch that contains this fix.
|
2006-08-31 14:29:30
| 1,157,050,000
|
resolved fixed
|
83cafb8
| 1,157,660,000
|
bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/PropertySheetPage.java
|
Eclipse_Platform_UI
|
3,676
| 154,234
|
Bug 154234 [Dialogs] ErrorDialog.createDialogArea javadoc references missing createCustomArea method
|
The javadoc for ErrorDialog.createDialogArea indicates that subclasses should override the createCustomArea method. This method does not exist in 3.2.
|
2006-08-17 10:38:26
| 1,155,830,000
|
verified fixed
|
c587b4b
| 1,157,580,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/ErrorDialog.java
|
Eclipse_Platform_UI
|
3,677
| 155,740
|
Bug 155740 [Undo] - AdvancedValidationUserApprover accesses UI without using async/sync
|
The documentation for IOperationApprover says that implementors must be prepared to receive notifications from a background thread. AdvancedValidationUserApprover does not use the SWT sync or async when accessing UI. It has gotten away with this thus far because most validation is triggered by the undo/redo action handlers in the UI thread. However, when an operation is initially executed, it can come from a background thread. This surfaces in the implementation of some of the resource modifying undoable operations which operate in a background thread and require approval.
|
2006-08-30 17:42:18
| 1,156,970,000
|
verified fixed
|
3aa78e2
| 1,157,570,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/operations/LinearUndoViolationUserApprover.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/operations/NonLocalUndoUserApprover.java
|
Eclipse_Platform_UI
|
3,678
| 142,299
|
Bug 142299 [JFace] Class Dialog cannot be loaded in non-UI thread
|
The static initializer of org.eclipse.jface.dialogs.Dialog cannot be executed in a non-UI thread. The problematic call-chain is: JFaceResources.getImageRegistry() -> Display.getCurrent(). In a non-UI thread this returns null, causing an NPE in the static initializer. As the result, this class fails to load. I stumbled over this because I wanted to perform aspect weaving (using the new hooks in the OSGI) on a subclass of Dialog. For that purpose I had to force loading these classes from infrastructure code, perhaps even before the UI was up and running. Another (hypothetical) scenario where this will cause problems would be a configurable factory, which could be programmed like this: Class myDialogClass; void init() { myDialogClass = Class.forName(readDialogClassName()); } Dialog createDialog() { return (Dialog)myDialogClass.newInstance(); } Also in this case method init() would crash if invoked within a non-UI thread. IMHO, a static initializer should never make any assumptions about the context it is being executed in. The code in question seems to exist for backward compatibility only. (Typo in javadoc: @see Display#getSystemIcon(int ID), should read: getSystemImage, the same typo in ImageRegistry.get()). In fact ImageRegistry.get(String) re-maps the deprecated keys from Dialog to the new ones in SWT, so I believe the code in the static initializer has not even any effect, the entries entered into the image registry will never be retrieved by that name. Correct me if I'm wrong.
|
2006-05-17 14:08:45
| 1,147,890,000
|
verified fixed
|
2e1c630
| 1,157,570,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/Dialog.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/JFaceResources.java bundles/org.eclipse.jface/src/org/eclipse/jface/wizard/Wizard.java
|
Eclipse_Platform_UI
|
3,679
| 155,856
|
Bug 155856 [IDE] bad value in the IIDEActionConstants
|
code sample : ----------------------------------------------------------------------- /** * Edit menu: name of group for extra Find-like actions (value <code>"find.ext"</code>). */ public static final String FIND_EXT = "cut.ext"; //$NON-NLS-1$ ----------------------------------------------------------------------- Seems there should be "find.ext" instead of "cut.ext". This may be the cause of the messages that can appear in the error log on a rcp product : "Reference item find.ext not found for action null"
|
2006-08-31 12:14:06
| 1,157,040,000
|
verified fixed
|
59d5183
| 1,157,570,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/IIDEActionConstants.java
|
Eclipse_Platform_UI
|
3,680
| 154,714
|
Bug 154714 [EditorMgmt] "Next Editor" functionality should allow the window list to move locations
|
When using the key command to access the "Next Editor" functionality and with Eclipse split across multiple monitors, the list of editors is split directly down the middle of the screen. The editor selection list should either center itself in the middle of the active editor (instead of the application itself) or should allow the user to move the list and the list remember it's location. See attached screenshot for an example of the problem - the red-line indicates the screen split.
|
2006-08-22 12:15:50
| 1,156,260,000
|
verified fixed
|
46e21d7
| 1,157,470,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/CyclePartAction.java
|
Eclipse_Platform_UI
|
3,681
| 154,601
|
Bug 154601 [EditorMgmt] Wildcard at end of file association string should be invalid
|
You are able to use a wildcard (*) at the end of a string representing a filetype. For example the following is valid *.java@@.* This is the case even though associating a specific editor with something like the above example does not work. If you were to associate the above filetype with the Java editor you still end up getting the default editor when you tried to open the file for editing. You should either - Permit the association of a filetype ending with a wildcard to a specific editor or - Do not the use of a wildcard at the end of a filetype
|
2006-08-21 15:35:10
| 1,156,190,000
|
verified fixed
|
bc6d175
| 1,157,460,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/FileExtensionDialog.java
|
Eclipse_Platform_UI
|
3,682
| 154,467
|
Bug 154467 [WorkingSets] (Patch attached) Smart selection of single WorkingSets
|
If you open the "Select Working Set" dialog, you can check an item in the list and press ok to activate this Working set. If you do a double click in the list, nothing happens (not nothing, but nothing visible for the user). The dialog is closed and nobody knows whats going on. Here is a patch to extend the dialog by selecting the working set you double.clicked on.
|
2006-08-20 08:54:39
| 1,156,080,000
|
resolved fixed
|
21e8348
| 1,157,460,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/WorkingSetSelectionDialog.java
|
Eclipse_Platform_UI
|
3,683
| 155,422
|
Bug 155422 [PropertiesDialog] property page not showing up
|
20060828 I changed the jdt.ui property pages to use enablement instead of object contributions. However, the following enablement doesn't seem to work: <enabledWhen> <or> <adapt type="org.eclipse.core.resources.IProject"> <test property="org.eclipse.core.resources.projectNature" value="org.eclipse.jdt.core.javanature"/> </adapt> <and> <instanceof value="org.eclipse.jdt.core.IPackageFragmentRoot"/> <not> <test property="org.eclipse.jdt.core.inSourceFolder"/> </not> </and> </or> </enabledWhen> The page is supposed to be added to all projects with Java nature and all IPackageFragmentRoots that are not source folders. The page never shows up under a IProject. Debugging into it it seems that PropertyPagesRegistryReader.getObjectClassesFromEnablement(IConfigurationElement) tries to find out for waht object this is contributed. Not easy here with the or-ed condition.
|
2006-08-28 12:44:55
| 1,156,780,000
|
verified fixed
|
90abbfa
| 1,156,960,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/registry/PropertyPagesRegistryReader.java
|
Eclipse_Platform_UI
|
3,684
| 155,575
|
Bug 155575 [Viewers] IllegalArgumentException while viewing preference page
|
I've started getting IllegalArgumentExceptions when viewing certain preference pages. ex: the experimental keybinding page or Java>Editors>Content Assist>Advanced java.lang.IllegalArgumentException: Argument cannot be null at org.eclipse.swt.SWT.error(SWT.java:3358) at org.eclipse.swt.SWT.error(SWT.java:3297) at org.eclipse.swt.SWT.error(SWT.java:3268) at org.eclipse.swt.widgets.Widget.error(Widget.java:434) at org.eclipse.swt.widgets.TableItem.setText(TableItem.java:1148) at org.eclipse.jface.viewers.TableViewerRow.setText(TableViewerRow.java:138) at org.eclipse.jface.viewers.ViewerCell.setText(ViewerCell.java:114) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:98) at org.eclipse.jface.viewers.TableViewer.doUpdateItem(TableViewer.java:368) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:465) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:1955) at org.eclipse.jface.viewers.TableViewer.internalRefreshAll(TableViewer.java:790) at org.eclipse.jface.viewers.TableViewer.internalRefresh(TableViewer.java:727) at org.eclipse.jface.viewers.TableViewer.internalRefresh(TableViewer.java:714) at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1388) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1323) at org.eclipse.jface.viewers.CheckboxTableViewer.preservingSelection(CheckboxTableViewer.java:295) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1386) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1345) at org.eclipse.jdt.internal.ui.preferences.CodeAssistAdvancedConfigurationBlock.updateControls(CodeAssistAdvancedConfigurationBlock.java:627) at org.eclipse.jdt.internal.ui.preferences.CodeAssistAdvancedConfigurationBlock.createContents(CodeAssistAdvancedConfigurationBlock.java:377) at org.eclipse.jdt.internal.ui.preferences.CodeAssistAdvancedPreferencePage.createPreferenceContent(CodeAssistAdvancedPreferencePage.java:36) at org.eclipse.jdt.internal.ui.preferences.PropertyAndPreferencePage.createContents(PropertyAndPreferencePage.java:149) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:233) at org.eclipse.jdt.internal.ui.preferences.CodeAssistAdvancedPreferencePage.createControl(CodeAssistAdvancedPreferencePage.java:31) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1403) at org.eclipse.jface.preference.PreferenceDialog$12.run(PreferenceDialog.java:1162) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1156) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:439) at org.eclipse.jface.preference.PreferenceDialog$8.selectionChanged(PreferenceDialog.java:661) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:839) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:837) at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1143) at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1163) at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:236) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:230) at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:404) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3170) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2872) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3193) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2869) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) eclipse.buildId=I20060807-2000 java.version=1.4.2_08 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 -data /opt/pwebster/workspaces/general320
|
2006-08-29 14:28:46
| 1,156,880,000
|
verified fixed
|
e0fd32c
| 1,156,880,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewerRow.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewerRow.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/AllTests.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/SimpleTableViewerTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/SimpleTreeViewerTest.java
|
Eclipse_Platform_UI
|
3,685
| 142,836
|
Bug 142836 No F1 help for problems view
|
3.2 RC5 There is no help context for the problems view. In addition, the help for the Tasks view says: <context id="task_list_view_context"> <description>This view shows build problems and tasks (reminders) that are either user-created or are automatically generated during building.</description> This is no longer correct (the tasks view does not show build problems).
|
2006-05-19 15:31:16
| 1,148,070,000
|
resolved fixed
|
3cb1ae3
| 1,156,780,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/ProblemView.java
|
Eclipse_Platform_UI
|
3,686
| 154,104
|
Bug 154104 [Workbench] Search based navigation
|
Because traditional navigation-by-browsing does not scale to large data sets, we should generalize and extend the existing search-based rapid navigation mechanisms (e.g. "Quick Find Class"). [UI, UA]
|
2006-08-16 13:44:47
| 1,155,750,000
|
verified fixed
|
33d7ea7
| 1,156,370,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/incubator/CtrlEAction.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/incubator/IncubatorMessages.java
|
Eclipse_Platform_UI
|
3,687
| 66,375
|
Bug 66375 [Dialogs] TaskPropertiesDialog and DialogMarkerProperties need a common superclass
|
RC1 Despite these two classes being pretty much identical they share almost no code. TaskPropertiesDialog should be a subclass a DialogMarkerProperties. As this is an API change post 3.0
|
2004-06-09 14:36:51
| 1,086,810,000
|
verified fixed
|
5dfab9a
| 1,156,290,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/bookmarkexplorer/BookmarkPropertiesDialog.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/DialogMarkerProperties.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/DialogTaskProperties.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/tasklist/TaskPropertiesDialog.java
|
Eclipse_Platform_UI
|
3,688
| 154,410
|
Bug 154410 [Cell Editors] - Cell Editor action handler doesn't handle dynamic undo text
|
The CellEditorActionHandler allows clients to install an undo and redo handler that should be used when the cell editor is not open. However, there is no support for the fact that most undo and redo handlers update their action text according to the operation to be undone/redone. Further, the enablement conditions on undo and redo action handlers change dynamically. CellEditorActionHandlers need to monitor property change events of their underlying undo/redo actions and update the enablement and text accordingly. This is required so that the task views, bookmark views, etc. show the correct text in the undo/redo actions when there is a marker operation to be undone.
|
2006-08-18 17:57:24
| 1,155,940,000
|
verified fixed
|
3ad3405
| 1,156,290,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/part/CellEditorActionHandler.java
|
Eclipse_Platform_UI
|
3,689
| 154,445
|
Bug 154445 [Wizards] Incomplete javadoc for WizardNewProjectCreationClass.getProjectHandle
|
This method return systematically the handle of the project relative to the workspace root. However, a user could expect to get the handle of the project taking the path specified in the page into account. This should be explained in the javadoc or the method should be changed...
|
2006-08-19 17:36:50
| 1,156,020,000
|
verified fixed
|
a975ae9
| 1,156,260,000
|
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/dialogs/WizardNewProjectCreationPage.java
|
Eclipse_Platform_UI
|
3,690
| 154,523
|
Bug 154523 [Viewers] Needless API function in ViewerLabelProvider
|
public boolean useNativeTooltip(Object object, int columnIndex) not needed
|
2006-08-21 08:50:25
| 1,156,160,000
|
verified fixed
|
76b3452
| 1,156,180,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerLabelProvider.java
|
Eclipse_Platform_UI
|
3,691
| 153,552
|
Bug 153552 [LinkedResources] LinkedResourceDecorator shows wrong decoration for non-local targets
|
LinkedResourceDecorator.decorate uses resource.getLocation to check if the target of a link exists. This returns null when the target is on a non-local (EFS) filesystem, and as a consequence linked resources pointing to non-local files or folders are displayed with a warning overlay. It seems that using getLocationURI instead would fix the problem?
|
2006-08-11 05:54:03
| 1,155,290,000
|
resolved fixed
|
28c0759
| 1,155,840,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/LinkedResourceDecorator.java
|
Eclipse_Platform_UI
|
3,692
| 144,294
|
Bug 144294 Performance: CommonNavigator could easily cache its ISelection to improve its performance
|
Currently, the CommonNavigator does not override the getSelection() method, which is quite expensive when called repeatedly by clients since it gets the current selection from the underlying SWT widget each time it gets called. A simple trick is to cache the selection and update it only when it actually changes. This would result in improved performance for clients who call getSelection() often. This defect is related to 140032. Please refer to it for more info. I will be submitting a patch shortly.
|
2006-05-29 15:14:20
| 1,148,930,000
|
verified fixed
|
76fbec5
| 1,155,760,000
|
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/CommonViewer.java
|
Eclipse_Platform_UI
|
3,693
| 154,064
|
Bug 154064 Need a way to access the TreeItem or TableItem on a refresh
|
It is not currently possible to know when an item is refreshed. This is required for ownerDraw support in viewers.
|
2006-08-16 11:36:49
| 1,155,740,000
|
verified fixed
|
993eb3b
| 1,155,740,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ColumnViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerCell.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerColumn.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerRow.java
|
Eclipse_Platform_UI
|
3,694
| 153,943
|
Bug 153943 [Viewers] Rename new API, e.g. RowPart -> ViewerRow
| null |
2006-08-15 13:44:26
| 1,155,660,000
|
verified fixed
|
710f22a
| 1,155,670,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/Cell.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ColumnViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ColumnViewerPart.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/RowPart.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableColumnViewerPart.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableEditorImpl.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableRowPart.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewerRow.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TooltipSupport.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeColumnViewerPart.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeEditorImpl.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeRowPart.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewerRow.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerCell.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerColumn.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerRow.java
|
Eclipse_Platform_UI
|
3,695
| 145,431
|
Bug 145431 [KeyBindings] TVT3.2:TCT857: DA: Incorrect sort of dropdown list
|
OS: RHEL 3.1 Must fix or not a must fix: YES Build date: 060406 Component name = Base Blocking: NO Language: da Bitmap Location: V:\defects\da\04.001150.pg Tester Name: Elsebeth Flarup Problem Description: On the menu bar from the main Workbench panel, click Windows > Preference Expand and Select General Select Keys Click on the Modify tab on the right-hand pane Click on the drop-down arrow for the Category menu Salect Uncategorized Click on the drop-down arrow for the Name menu The list is incorrectly sorted for Danish. The bottom part of the list has the Danish letter '?' sorted after the Danish letter '?'. This is incorrect. There is also one single entry in the list which starts with a lower case letter, and this is sorted incorrectly in between 'Z' and a Danish national character. It looks as if the sort is basic US ASCII (binary) sort, not locale-specific. Working as designed, not even sorted in English. Thanks. I don't agree. The list is sorted in English. You don't see upper case 'W' come before 'V' - which is exactly equivalent to the problem I have in Danish. This article was reassigned from Category:''TVT/Testing''.
|
2006-06-05 17:06:14
| 1,149,540,000
|
verified fixed
|
698b824
| 1,155,670,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/KeysPreferencePage.java
|
Eclipse_Platform_UI
|
3,696
| 153,803
|
Bug 153803 [Wizards] A primary INewWizard does not show up if it's the only INewWizard and uncategorized
|
If an INewWizard is uncategorized and is the only wizard in the RCP application, and is also a primary wizard, then it does not show up in the wizard selection in the NewWizard wizard. The cause of this seems to be the assumption by the org.eclipse.ui.internal.dialogs.WizardContentProvider that if there's only one item in the children of the AdaptablesList, it must be a wizard category (WizardCollectionElement) and wants to return all it's children. But when all the wizards are primary, it seems the categories are not used, and the content provider is trying to return the children of the wizard (WorkbenchWizardElement), instead of returning the wizard itself. This sounds complicated, but I hope it made sense. The problematic place in 3.2 is // if there is only one category, return it's children directly (flatten list) if (list.size() == 1) { return getChildren(list.get(0)); } (lines 71-74) I'll attach a patch against the R3_2_maintenance branch
|
2006-08-14 14:06:10
| 1,155,580,000
|
verified fixed
|
45f2238
| 1,155,670,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/WizardContentProvider.java
|
Eclipse_Platform_UI
|
3,697
| 153,892
|
Bug 153892 [WorkingSets] Select Working Sets is not "exlusive"
|
I discovered the great new feature "window working set" in eclipse 3.2 and started to use it. Previously I used the working sets manually in each perspective like "package explorer". The old behaviour was, that I selected a new working set and the previous one was automatically deselected. It was a "switch working set" operation. The window working set has a new behaviour. I select another working set and see thereofore two working sets at the same time in the package explorer. Now I have to use the window working set a second time and deselect the previous working set. I have to click twice for the same behaviour as before. Is there a hidden workaround to perform a "switch working set" operation with window working set by only selecting "window working set" once?
|
2006-08-15 09:03:17
| 1,155,650,000
|
verified fixed
|
2fb108a
| 1,155,660,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/actions/SelectWorkingSetsAction.java
|
Eclipse_Platform_UI
|
3,698
| 153,503
|
Bug 153503 [Viewers] ComboViewer#setSelection does't select element w/o equals override
|
I use a ComboViewer to show elements of a class that does not override Object#equals and #hashCode. Therefore I specified an IElementComparer via ComboViewer#setComparer to do the job. My expectation was that the comparer would be used in setSelection to find the element to be selected. Apparently this is not the case. To me this looks like a bug, or is this behaviour desired? The attached test case reproduces this behaviour.
|
2006-08-10 18:36:00
| 1,155,250,000
|
resolved fixed
|
e7c0ee4
| 1,155,660,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractListViewer.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/AllTests.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ComboViewerComparerTest.java
|
Eclipse_Platform_UI
|
3,699
| 142,329
|
Bug 142329 SlaveContextService does not accept NULL expression
|
SlaveContextService#activateContext(String contextId, Expression expression, boolean global) attempts to construct an AndExpression containing the default expression and NULL. This results in a NullPointerException. The fix is to avoid constructing the AndExpression and simply use the default.
|
2006-05-17 15:55:05
| 1,147,900,000
|
verified fixed
|
bb43d75
| 1,155,660,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/contexts/SlaveContextService.java
|
Eclipse_Platform_UI
|
3,700
| 153,832
|
Bug 153832 [FilteredTree] need a createText(...)
|
We need some type of createText method similar to what we need for the createTreeViewer. The reasoning behind this is that a user may want to supply their own text control. In PDE's case, we would like to use FormToolkit to adapt the text control when created.
|
2006-08-14 17:24:28
| 1,155,590,000
|
verified fixed
|
bd15a76
| 1,155,660,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/FilteredTree.java
|
Eclipse_Platform_UI
|
3,701
| 153,766
|
Bug 153766 [IDE] Open properties via editor causes IllegalAccessException
|
3.3 M1 1. start fresh workspce 2. create a simple project 3. add a simple text file 4. from the text editor open the properties dialog (Alt+Enter) ==> error is writtent to .log: !ENTRY org.eclipse.equinox.registry 4 1 2006-08-14 16:05:38.723 !MESSAGE Plug-in "org.eclipse.ui.ide" was unable to instantiate class "org.eclipse.ui.internal.ide.model.FileInputAdapterFactory". !STACK 0 java.lang.IllegalAccessException: Class org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI can not access a member of class org.eclipse.ui.internal.ide.model.FileInputAdapterFactory with modifiers "" at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) at java.lang.Class.newInstance0(Class.java:344) at java.lang.Class.newInstance(Class.java:303) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:170) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:787) 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.core.internal.runtime.AdapterFactoryProxy.loadFactory(AdapterFactoryProxy.java:114) at org.eclipse.core.internal.runtime.AdapterManager.classForName(AdapterManager.java:140) at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:283) at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:266) at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:73) at org.eclipse.ui.internal.dialogs.RegistryPageContributor.failsEnablement(RegistryPageContributor.java:263) at org.eclipse.ui.internal.dialogs.RegistryPageContributor.isApplicableTo(RegistryPageContributor.java:207) at org.eclipse.ui.internal.dialogs.PropertyPageContributorManager.contribute(PropertyPageContributorManager.java:143) at org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:61) at org.eclipse.ui.dialogs.PropertyDialogAction.createDialog(PropertyDialogAction.java:175) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:154) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:229) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3377) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2997) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-08-14 10:37:51
| 1,155,570,000
|
resolved fixed
|
593e3f0
| 1,155,660,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/model/FileInputAdapterFactory.java
|
Eclipse_Platform_UI
|
3,702
| 152,170
|
Bug 152170 [FilteredTree] Make it easier to use other viewers
|
Right now it's not easy to make use of a checkboxtreeviewer in a FilteredTree. It's possible to override createTreeControl(...), however, it adds a disposelistener which references a protected field (refreshJob). Maybe it would be best to put this dispose logic somewhere else so clients can use their own custom tree viewers (ie., createTreeViewer(...)? Does this make sense :)?
|
2006-07-28 12:33:00
| 1,154,100,000
|
verified fixed
|
7a5882a
| 1,155,590,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/FilteredTree.java
|
Eclipse_Platform_UI
|
3,703
| 68,178
|
Bug 68178 [ActivityMgmt] Capabilities Preference Page Resizing
|
Resizing the Capabilities preference page should give most of the extra space to the tree view on the top, and little to the description area on the bottom; currently all extra space goes to the bottom area.
|
2004-06-22 11:24:52
| 1,087,920,000
|
closed fixed
|
8a8115b
| 1,155,580,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/activities/ActivitiesPreferencePage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/activities/ActivityCategoryPreferencePage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/activities/ws/ActivityEnabler.java
|
Eclipse_Platform_UI
|
3,704
| 135,709
|
Bug 135709 [WorkingSets] Select Working Sets Select All/Deselect All Enablement
|
If there are no working sets than both buttons should be disabled.
|
2006-04-08 08:20:52
| 1,144,500,000
|
verified fixed
|
a0d2437
| 1,155,580,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceWorkingSetPage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/actions/SelectWorkingSetsAction.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/AbstractWorkingSetDialog.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/WorkingSetSelectionDialog.java
|
Eclipse_Platform_UI
|
3,705
| 153,536
|
Bug 153536 [Wizards] Description in wizard does not wrap
|
Build: 3.3 M1 Something happened at the Platform/UI level between 3.2 and 3.3M1 since the same PDE code now shows weird behaviour on M1. 1. Open the New plug-in project wizard. 2. Once you get to the templates page of the wizard, choose the 'Hello World' template, press Next. Note how the description of the page does not wrap and the wizard becomes very wide. When I run the same PDE code against 3.2, the description wraps nicely onto two lines.
|
2006-08-11 03:36:14
| 1,155,280,000
|
verified fixed
|
748032f
| 1,155,570,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/wizard/WizardDialog.java
|
Eclipse_Platform_UI
|
3,706
| 153,103
|
Bug 153103 [Wizards] NPE while validating project location
|
- File > New > Project... - Select General > Project, click Next - Uncheck "Use default location" - Enter "C:\test" for location It validates at each keystroke, and when you reach "C:" and "C:\" it logs the following exception: java.lang.NullPointerException at org.eclipse.core.internal.resources.WorkspaceRoot.getProject(WorkspaceRoot.java(Compiled Code)) at org.eclipse.ui.internal.ide.dialogs.ProjectContentsLocationArea.checkValidLocation(ProjectContentsLocationArea.java:388) at org.eclipse.ui.internal.ide.dialogs.ProjectContentsLocationArea$3.modifyText(ProjectContentsLocationArea.java:229) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java(Compiled Code)) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java(Compiled Code)) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Inlined Compiled Code)) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Compiled Code)) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Inlined Compiled Code)) at org.eclipse.swt.widgets.Text.wmCommandChild(Text.java(Compiled Code)) at org.eclipse.swt.widgets.Control.WM_COMMAND(Control.java(Compiled Code)) at org.eclipse.swt.widgets.Control.windowProc(Control.java(Compiled Code)) at org.eclipse.swt.widgets.Display.windowProc(Display.java(Compiled Code)) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java(Inlined Compiled Code)) at org.eclipse.swt.widgets.Text.callWindowProc(Text.java(Compiled Code)) at org.eclipse.swt.widgets.Control.windowProc(Control.java(Compiled Code)) at org.eclipse.swt.widgets.Text.windowProc(Text.java(Compiled Code)) at org.eclipse.swt.widgets.Display.windowProc(Display.java(Compiled Code)) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java(Inlined Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code)) at org.eclipse.jface.window.Window.runEventLoop(Window.java(Compiled Code)) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.java:181) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java(Inlined Compiled Code)) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java(Compiled Code)) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java(Compiled Code)) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Inlined Compiled Code)) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code)) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled Code)) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-08-08 11:54:35
| 1,155,050,000
|
verified fixed
|
9ec5940
| 1,155,570,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ProjectContentsLocationArea.java
|
Eclipse_Platform_UI
|
3,707
| 153,201
|
Bug 153201 Not externalizing string "false" in the Properties panel for a stored procedure
|
Reference: RATLC defect: 1123758 TVT10:02.002760: Unxternalized string "false" in the properties panel Steps to recreate the problem: -Enable Data developement using the Window > Preferences > General (expand) > Capabilities > click on Data. -Create a new data development project: File > New > Data Development Project. -Select any connection that is available. -Create a new Java SP: Expand project > Stored procedures folder > New > Stored Procedure. In wizard, select Java as the language. Click Finish. -Highlight this newly created Java stored procedure. Click on the Properties tab in the Output View. Problem description: String "false" is not translated in the Value column; it is not externalized Related string "true" is translated and externalized
|
2006-08-08 18:30:20
| 1,155,080,000
|
verified fixed
|
48814f3
| 1,155,570,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/properties/ResourcePropertySource.java
|
Eclipse_Platform_UI
|
3,708
| 138,006
|
Bug 138006 [Themes] Theme description read incorrectly
| null |
2006-04-21 13:06:30
| 1,145,640,000
|
verified fixed
|
b325a82
| 1,155,570,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/themes/ThemeDescriptor.java
|
Eclipse_Platform_UI
|
3,709
| 73,729
|
Bug 73729 [Workbench] [Mac] Dual preferences menu items
|
On Mac OS X, the preferences menu item appears in the Eclipse menu. This is correct. However, the same menu item that does the same thing also appears in the Window menu, which is correct on other platforms but not the Mac. It should be removed from the Window menu.
|
2004-09-11 19:12:42
| 1,094,940,000
|
verified fixed
|
010830d
| 1,155,560,000
|
bundles/org.eclipse.ui.carbon/src/org/eclipse/ui/carbon/CarbonUIEnhancer.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/WorkbenchActionBuilder.java
|
Eclipse_Platform_UI
|
3,710
| 152,966
|
Bug 152966 [EditorMgmt] MockMapping is missing an equals method
|
The TypeFilteringDialog will not check the correct extension in checkInitialSelections() without it. e.g. in the File System import wizard The equals method should be the same as in FileEditorMapping
|
2006-08-07 09:13:09
| 1,154,960,000
|
verified fixed
|
d25e312
| 1,155,560,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/registry/EditorRegistry.java
|
Eclipse_Platform_UI
|
3,711
| 151,838
|
Bug 151838 [Markers] ArrayIndexOutOfBoundsException while queuing viewer updates
|
I installed Eclipse 3.2 0n Suse Linux 10.1, with CDT 3.1. The operating system was installed just 2 hours ago; I unpacked Eclipse 3.2 SDK archive and unpacked and copied CDT 3.1 (we do development in C and C++) to Eclipse folder. Immediately, upon producing changes to code in a project I'm working on, the code compiles and right then this message box "Queueing viewer updates - error" appears. On and on. Is there anything I can do to prevent this? Will I have to revert back to Eclipse 3.1 and the previous CDT package? Thanks.
|
2006-07-26 08:31:46
| 1,153,920,000
|
verified fixed
|
0b88f7b
| 1,155,560,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java
|
Eclipse_Platform_UI
|
3,712
| 150,597
|
Bug 150597 Patch that adds enhancements to GridDataFactory
| null |
2006-07-14 00:13:12
| 1,152,850,000
|
verified fixed
|
0cfa406
| 1,155,560,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/layout/GridDataFactory.java bundles/org.eclipse.jface/src/org/eclipse/jface/layout/LayoutGenerator.java
|
Eclipse_Platform_UI
|
3,713
| 153,071
|
Bug 153071 Errors when showing properties for non-existing location of linked folder
|
I20060807-2000 1. create simple project 'P' 2. add a linked folder to a location that does not exist (I used 'xxx') 3. select the new folder in the Navigator 4. context menu > Properties ==> error dialog + .log entries: !ENTRY org.eclipse.ui.ide 4 4 2006-08-08 12:51:09.103 !MESSAGE Must specify a URI scheme:xxx !ENTRY org.eclipse.core.filesystem 4 566 2006-08-08 12:51:09.113 !MESSAGE Must specify a URI scheme:xxx !ENTRY org.eclipse.ui.ide 4 4 2006-08-08 12:51:09.113 !MESSAGE Must specify a URI scheme:xxx !ENTRY org.eclipse.core.filesystem 4 566 2006-08-08 12:51:09.113 !MESSAGE Must specify a URI scheme:xxx !ENTRY org.eclipse.ui.ide 4 4 2006-08-08 12:51:09.123 !MESSAGE Must specify a URI scheme:xxx !ENTRY org.eclipse.core.filesystem 4 566 2006-08-08 12:51:09.123 !MESSAGE Must specify a URI scheme:xxx !ENTRY org.eclipse.jface 4 2 2006-08-08 12:51:09.123 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NullPointerException at org.eclipse.core.internal.filesystem.InternalFileSystemCore.getFileSystem(InternalFileSystemCore.java:61) at org.eclipse.core.filesystem.EFS.getFileSystem(EFS.java:256) at org.eclipse.ui.internal.ide.dialogs.ResourceInfoPage.createStateGroup(ResourceInfoPage.java:447) at org.eclipse.ui.internal.ide.dialogs.ResourceInfoPage.createContents(ResourceInfoPage.java:266) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:233) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1403) at org.eclipse.jface.preference.PreferenceDialog$12.run(PreferenceDialog.java:1162) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1156) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:439) at org.eclipse.jface.preference.PreferenceDialog$8.selectionChanged(PreferenceDialog.java:661) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:839) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:837) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1578) at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:958) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:482) at org.eclipse.jface.preference.PreferenceDialog$3.run(PreferenceDialog.java:345) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:341) at org.eclipse.jface.window.Window.create(Window.java:426) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1124) at org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:82) at org.eclipse.ui.dialogs.PropertyDialogAction.createDialog(PropertyDialogAction.java:175) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:154) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3377) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2997) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-08-08 06:49:40
| 1,155,030,000
|
verified fixed
|
1cd9416
| 1,155,060,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceInfoPage.java
|
Eclipse_Platform_UI
|
3,714
| 152,785
|
Bug 152785 Improve javadocs for org.eclipse.ui.IStartup
|
The codeing example for method earlyStartup needs to be enclosed in <pre> element. Patch follows: ### Eclipse Workspace Patch 1.0 #P org.eclipse.ui.workbench Index: Eclipse UI/org/eclipse/ui/IStartup.java =================================================================== RCS file: /cvsroot/eclipse/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IStartup.java,v retrieving revision 1.9 diff -u -r1.9 IStartup.java --- Eclipse UI/org/eclipse/ui/IStartup.java 8 May 2006 20:55:31 -0000 1.9 +++ Eclipse UI/org/eclipse/ui/IStartup.java 3 Aug 2006 19:54:52 -0000 @@ -26,6 +26,7 @@ * since they may access SWT. For example, to obtain the current workbench * window, use: * <code> + * <pre> * final IWorkbench workbench = PlatformUI.getWorkbench(); * workbench.getDisplay().asyncExec(new Runnable() { * public void run() { @@ -35,6 +36,7 @@ * } * } * }); + * </pre> * </code> * </p> * @see org.eclipse.swt.widgets.Display#asyncExec
|
2006-08-03 15:54:14
| 1,154,630,000
|
resolved fixed
|
74e8ba1
| 1,154,640,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IStartup.java
|
Eclipse_Platform_UI
|
3,715
| 151,958
|
Bug 151958 [Markers] Custom problem filter not updated
|
- create a minimal plugin with a plugin.xml like this: <?xml version="1.0" encoding="UTF-8"?> <?eclipse version="3.2"?> <plugin> <extension point="org.eclipse.ui.ide.markerSupport"> <problemFilter name="Problems" id="markererror.myPlugin.filterId" enabled="true" scope="ON_ANY_IN_SAME_CONTAINER"> <selectedType/> </problemFilter> </extension> </plugin> - start a runtime workbench, introduce a compile error in a Java class to get a problem marker. - in the problems view, disable the default filter, the filter "Problems" remains activated. - no markers are shown in the problem view. I debugged a little and found that the method MarkerFilter.setFocusResource() is only called for the default filter, not for the plugin-defined "Problems" filter: The latter filter is only contained in the field MarkerView.enabledFilters. The field MarkerView.markerFilters contains only the default filter.
|
2006-07-27 03:40:27
| 1,153,990,000
|
verified fixed
|
af307db
| 1,154,530,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/DialogMarkerFilter.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java
|
Eclipse_Platform_UI
|
3,716
| 152,586
|
Bug 152586 [Properties view] Querying nonexistent project for properties causes NPE
| null |
2006-08-02 09:00:41
| 1,154,520,000
|
verified fixed
|
3678b3d
| 1,154,530,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/properties/ResourcePropertySource.java
|
Eclipse_Platform_UI
|
3,717
| 152,035
|
Bug 152035 [BiDi] Menu items do not appear for IFile resources when -nl iw is used
| null |
2006-07-27 13:44:39
| 1,154,020,000
|
closed fixed
|
71b7547
| 1,154,530,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/model/WorkbenchFile.java
|
Eclipse_Platform_UI
|
3,718
| 135,055
|
Bug 135055 Save action state is not refreshed when Properties View is active for a selection in Common Navigator
|
The Properties View now delegates the save behavior to the source of the properties instead of the active editor. Its initial state is ok. However, if there is an active editor that is not dirty but Properties View is displayed for selection in Common Navigator that represents another (dirty) model then Save is properly enabled. And if the user hits CTRL+S it actually works fine: the model is saved and Common Navigator labels (model itself and title bar) are properly updated but the Save action itself does not change the state - it is still enabled. Similarly, if the initial selection is in a non-dirty model, the Save action is disabled, then make change through the Properties View and you can see the labels in Common Navigator being updated but Save action does not get enabled. It does if the element is re-selected in Common Navigator.
|
2006-04-05 11:43:32
| 1,144,250,000
|
verified fixed
|
cca9d46
| 1,154,470,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/BaseSaveAction.java
|
Eclipse_Platform_UI
|
3,719
| 151,781
|
Bug 151781 [Progress] ProgressManager$JobMonitor mishandles empty subtask
|
ProgressManager$JobMonitor#subTask(...) is implemented such that it does nothing if the 'name' parameter is a 0-length string. This is a problem because it makes the JobMonitor doesn't correctly update for code that uses the method of clearing a monitor's subtask (subTask("")). For example, this is incompatible with the way that SubProgressMonitors work (see SubProgressMonitor#done()). The workaround that clients used to trick the JobMonitor into working correctly is to call subTask(" ").
|
2006-07-25 18:52:28
| 1,153,870,000
|
verified fixed
|
0f37591
| 1,154,460,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressManager.java
|
Eclipse_Platform_UI
|
3,720
| 149,643
|
Bug 149643 [EditorMgmt] File > Properties in editor has IEditorInput as selection
|
I20060704-0800 Open a Text/Java/Ant/PDE editor on a file from your workspace. When the editor is active, File > Properties only shows the CVS properties page. When the file is selected in the Package Explorer, the Info properties page is shown as well. I would expect that the Info page is also shown when the editor is active.
|
2006-07-05 05:17:03
| 1,152,090,000
|
verified fixed
|
9d24b3c
| 1,154,440,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/model/FileInputAdapterFactory.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/ui/tests/propertyPages/TestPropertyPage.java
|
Eclipse_Platform_UI
|
3,721
| 138,608
|
Bug 138608 [Viewers] JFace AbstractTreeViewer: itemExists doesn't handle equal tree entries
|
I use a TreeViewer with - setUseHashLookup(true) - without any sorter or filter - with a comparer When I try to add an object that is equal to an existing entry in the tree, it will not be added. This is because the method private boolean itemExists(Item[] items, Object element) { if(usingElementMap()) { return findItem(element) != null; } for (int i = 0; i < items.length; i++) { if(items[i].getData().equals(element)) { return true; } } return false; } takes a shortcut if there is an element map, but the shortcut doesn't handle the 'multiple equal elements' case. There is a workaround, however: Setting a dummy sorter will avoid the call to itemExists and multiple equal elements can be added to the tree.
|
2006-04-26 08:27:56
| 1,146,050,000
|
verified fixed
|
e104856
| 1,154,340,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractTreeViewer.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/AllTests.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/Bug138608Test.java
|
Eclipse_Platform_UI
|
3,722
| 131,330
|
Bug 131330 [IDE] Misleading error message that workspace is currently in use
|
3.2M5 I currently moved to a new PC which had different drive letters. I start up one Eclipse instance, and then in there run a second instance under the debugger. In the launch configuration I still had the old path name to my workspace, like "D:\workspace". But that's not right anymore (everything is on C:). So when I tried to launch the second instance (Run > Debug...) I got an error dialog, but the message was misleading. It said: "Workspace Cannot be Locked Could not launch the product because the associated workspace is currently in use." It's not in use, it's completely missing. Also it would be nice for it to tell me what workspace directory it was complaining about since I have several.
|
2006-03-10 10:07:47
| 1,142,000,000
|
resolved fixed
|
0f0d123
| 1,154,250,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEApplication.java
|
Eclipse_Platform_UI
|
3,723
| 73,263
|
Bug 73263 [IDE] Need file pathname in titlebar
|
Currently, Eclipse displays the name of the active file in the titlebar. It would be nice to have the full pathname followed by the filename in the titlebar. example, instead of displaying only: MyClass.java display: /src/framework/model/domain/MyClass.java This is useful for a number of reasons: 1. To distinguish based on path, classes that have the same name. 2. For projects with multiple root directories, to tell where in the directory stucture one is currently editing. 3. Is an easy fix!
|
2004-09-03 14:15:06
| 1,094,240,000
|
resolved fixed
|
ab2611c
| 1,154,250,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchWindowAdvisor.java
|
Eclipse_Platform_UI
|
3,724
| 151,239
|
Bug 151239 [IDE] NPE in ResourceInfoPage
|
I20060718-0800 1. open the propertie pages on an JAR entry in the JRE container 2. error dialogs says that a page couldn't be shown java.lang.NullPointerException at org.eclipse.ui.internal.ide.dialogs.ResourceInfoPage.createContents(ResourceInfoPage.java:234) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:233) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1403) at org.eclipse.jface.preference.PreferenceDialog$12.run(PreferenceDialog.java:1162) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1156) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:439) at org.eclipse.jface.preference.PreferenceDialog$8.selectionChanged(PreferenceDialog.java:661) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:839) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:837) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1578) at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:958) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:482) at org.eclipse.jface.preference.PreferenceDialog$3.run(PreferenceDialog.java:345) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:341) at org.eclipse.jface.window.Window.create(Window.java:426) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1124) at org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:82) at org.eclipse.ui.dialogs.PropertyDialogAction.createDialog(PropertyDialogAction.java:175) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:154) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3377) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2997) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
|
2006-07-20 10:14:15
| 1,153,400,000
|
resolved fixed
|
885bdd3
| 1,154,100,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchMessages.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceInfoPage.java
|
Eclipse_Platform_UI
|
3,725
| 151,886
|
Bug 151886 [KeyBindings] Startup fails if default active scheme is undefined
|
Build: I20060718. In BindingPersistence.readActiveScheme, if defaultActiveSchemeId is "" then startup fails because it calls BindingManager.getScheme(defaultActiveSchemeId), which throws IllegalArgumentException if the argument is "". Since anyone can access the preference tree and change this value, BindingPersistence should protect against it to avoid startup failure.
|
2006-07-26 13:55:12
| 1,153,940,000
|
verified fixed
|
769ec00
| 1,154,090,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/BindingPersistence.java
|
Eclipse_Platform_UI
|
3,726
| 150,998
|
Bug 150998 [Import/Export] Import Projects Wizard: Finish is enabled even if no project is selected
|
In Import Existing Projects Wizard, the Finish button is enabled even when no projects are selected for import. When the Import wizard is first invoked, Finish is disabled, since no projects have been selected for import. If a directory with no Eclipse projects is selected, Finish remains disabled. If a directory with at least one Eclipse project is selected, then Finish becomes enabled. If none of the projects are selected for import, then Finish remains enabled. Although this behaviour does not cause any functional problems, the UI seems inconsistent.
|
2006-07-18 15:26:15
| 1,153,250,000
|
resolved fixed
|
0632162
| 1,154,090,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/wizards/datatransfer/WizardProjectsImportPage.java
|
Eclipse_Platform_UI
|
3,727
| 68,079
|
Bug 68079 [PerspectiveBar] Can't switch perspectives to item on the chevron
|
RC3, Windows XP There three items in the perspective switcher: debug, resource, and java. The window is the default size. The perspective switcher is as small as it can be. The debug perspective is active and I am running a debugging session. The other two items are on the chevron. Selecting one of those items does not switch perspectives. If the perspective switcher is expanded so that the items become visible, then it becomes possible to switch the perspectives.
|
2004-06-21 15:45:29
| 1,087,850,000
|
verified fixed
|
b65c769
| 1,154,030,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PerspectiveBarManager.java
|
Eclipse_Platform_UI
|
3,728
| 151,778
|
Bug 151778 Errors in ResourceManager JavaDoc
|
In the doc of createImage method you read: Creates an image, given an image descriptor. Images allocated in this manner must be disposed by disposeImage, and never by calling Image.dispose(). disposeImage is not present, maybe it should be destroyImage? The same error for the other creation methods.
|
2006-07-25 18:12:56
| 1,153,870,000
|
resolved fixed
|
243b350
| 1,153,920,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/resource/ResourceManager.java
|
Eclipse_Platform_UI
|
3,729
| 144,988
|
Bug 144988 [WorkspaceLauncher] Disallow space as workspace name
|
In Windows, when I launch Eclipse 3.2, a workspace window box is launched. I was able to specify simply the space character as the workspace path. It wasn't allow in Eclipse 3.1.2
|
2006-06-01 17:26:36
| 1,149,200,000
|
verified fixed
|
c2d727b
| 1,153,920,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/ChooseWorkspaceDialog.java
|
Eclipse_Platform_UI
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.