id
int64 1
6.5k
| bug_id
int64 2.03k
426k
| summary
stringlengths 9
251
| description
stringlengths 1
32.8k
⌀ | report_time
stringlengths 19
19
| report_timestamp
int64 1B
1.39B
| status
stringclasses 6
values | commit
stringlengths 7
9
| commit_timestamp
int64 1B
1.39B
| files
stringlengths 25
32.8k
| project_name
stringclasses 6
values |
|---|---|---|---|---|---|---|---|---|---|---|
1,630 | 296,056 |
Bug 296056 Deadlock between syncExec and IJobManager.beginRule
|
The following case now produces a deadlock (since N20091120-2000): 1) The UI is waiting to begin a scheduling rule 2) The thread that owns the scheduling rule attempts to perform a syncExec.
|
2009-11-24 16:02:10
| 1,259,100,000 |
resolved fixed
|
4ecf6b2
| 1,259,180,000 |
tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/concurrency/ConcurrencyTestSuite.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/concurrency/SyncExecWhileUIThreadWaitsForRuleTest.java
|
Eclipse_Platform_UI
|
1,631 | 253,232 |
Bug 253232 [Trim] locationURI "before" and "after" don't work for status trim
|
I would like to position a toolbar on the far left of the status trim. From the documentation, "toolbar:org.eclipse.ui.trim.status?before=org.eclipse.jface.action.StatusLineManager" should put it before the status line manager. However, the queries have no effect and my toolbar is always added at the end. Test case is attached. TrimContributionManager#update(boolean, boolean) does not seem to read the query part of my location when it reads my contribution. Is this handled somewhere else? I am attaching a test case.
|
2008-11-03 11:10:03
| 1,225,730,000 |
verified fixed
|
c254491
| 1,259,180,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/TrimContributionManager.java
|
Eclipse_Platform_UI
|
1,632 | 294,790 |
Bug 294790 [KeyBindings] LegacyActionTools should support SWT.F13 - F20
| null |
2009-11-10 14:34:55
| 1,257,880,000 |
verified fixed
|
bf32b1f
| 1,259,170,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/action/LegacyActionTools.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/BindingPersistence.java
|
Eclipse_Platform_UI
|
1,633 | 292,091 |
Bug 292091 [KeyBindings] Set extension point "org.eclipse.ui.bindings" 's element 'sequenceModifier' becomes disabled key bindings.
|
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.25 Safari/532.0 Build Identifier: 20090619-0625 If set "sequenceModifier" elements and found binding keys, they are disabled on linux platform.(I checked at prefenence page.[General->keys]) I'm tested like example below. <extension point="org.eclipse.ui.bindings"> <sequenceModifier find="M1+M2" replace="M2+M3" platforms="cocoa,carbon" /> <key sequence="M2+F5" commandId="example.commandId" schemeId="org.eclipse.ui.defaultAcceleratorConfiguration" contextId="org.eclipse.ui.contexts.dialog" /> <key sequence="M1+M2+8" commandId="another.example.commandId" schemeId="org.eclipse.ui.defaultAcceleratorConfiguration" contextId="org.eclipse.ui.contexts.window" /> <key sequence="M2+F7" commandId="other.commandId" schemeId="default.id" contextId="org.eclipse.ui.contexts.dialog" /> <scheme name="Default" description="Default shortcuts for Eclipse" id="default.id" /> </extension> Reproducible: Always
|
2009-10-12 21:03:20
| 1,255,400,000 |
verified fixed
|
6ec985a
| 1,259,160,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/BindingPersistence.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/keys/BindingPersistenceTest.java
|
Eclipse_Platform_UI
|
1,634 | 294,210 |
Bug 294210 [Contributions] 'Customize Perspective > Tool Bar Visibility' breaks with Separator
|
I20091103-0941 - enable Preferences > General Editors > Close editors automatically - open an editor - open Customize Perspective dialog - expand 'Navigate' => second to last item is empty (it's the separator in front of the 'Pin' action) - hover over the empty item => log entry below The separator should either not be shown (like in Menu Visibility), or it should be rendered with a label and a proper hover. !ENTRY org.eclipse.ui 4 0 2009-11-04 16:28:09.730 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.IllegalArgumentException: Argument cannot be null at org.eclipse.swt.SWT.error(SWT.java:4012) at org.eclipse.swt.SWT.error(SWT.java:3946) at org.eclipse.swt.SWT.error(SWT.java:3917) at org.eclipse.swt.widgets.Widget.error(Widget.java:463) at org.eclipse.swt.widgets.Label.setText(Label.java:388) at org.eclipse.ui.internal.dialogs.CustomizePerspectiveDialog$NameAndDescriptionToolTip.createEntry(CustomizePerspectiveDialog.java:758) at org.eclipse.ui.internal.dialogs.CustomizePerspectiveDialog$NameAndDescriptionToolTip.createToolTipContentArea(CustomizePerspectiveDialog.ja va:708) at org.eclipse.jface.window.ToolTip.toolTipShow(ToolTip.java:363) at org.eclipse.jface.window.ToolTip.toolTipOpen(ToolTip.java:530) at org.eclipse.jface.window.ToolTip.toolTipCreate(ToolTip.java:352) at org.eclipse.jface.window.ToolTip.access$2(ToolTip.java:346) at org.eclipse.jface.window.ToolTip$ToolTipOwnerControlListener.handleEvent(ToolTip.java:678) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3917) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3510) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.WorkbenchPage.editActionSets(WorkbenchPage.java:1875) at org.eclipse.ui.internal.handlers.EditActionSetsHandler.execute(EditActionSetsHandler.java:41) ...
|
2009-11-04 10:28:09
| 1,257,350,000 |
verified fixed
|
0fcd2e2
| 1,259,160,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/CustomizePerspectiveDialog.java
|
Eclipse_Platform_UI
|
1,635 | 270,092 |
Bug 270092 [CellEditors] [cell editors] TextCellEditor should not specify minimum size
| null |
2009-03-26 05:41:04
| 1,238,060,000 |
verified fixed
|
4afefa8
| 1,259,100,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TextCellEditor.java
|
Eclipse_Platform_UI
|
1,636 | 294,796 |
Bug 294796 [Contributions] API request: LegacyActionTools#escapeMnemonics(String)
| null |
2009-11-10 14:48:39
| 1,257,880,000 |
verified fixed
|
4d68f0f
| 1,259,090,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/action/LegacyActionTools.java bundles/org.eclipse.jface/src/org/eclipse/jface/action/StatusLine.java bundles/org.eclipse.jface/src/org/eclipse/jface/action/StatusLineContributionItem.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/FilteredItemsSelectionDialog.java
|
Eclipse_Platform_UI
|
1,637 | 293,512 |
Bug 293512 [Workbench] Make IWorkbench into an OSGi service
|
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 Build Identifier: I would like to be when the IWorkbench is available for use. I am currently being started before the IWorkbench is ready and it is causing severe problems. If IWorkbench was a OSGi service, then I could use a ServiceTracker to acquire the initialized IWorkbench when it is available. Reproducible: Always
|
2009-10-27 16:54:11
| 1,256,680,000 |
verified fixed
|
26a795f
| 1,259,090,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Workbench.java tests/org.eclipse.ui.tests.harness/src/org/eclipse/ui/tests/harness/util/UITestCase.java
|
Eclipse_Platform_UI
|
1,638 | 257,185 |
Bug 257185 [Contributions] Some submenus are still visible
|
Usually, if all children are hidden, the menu will automatically be hidden (i.e. the above isVisible call will return false). In some cases, unfortunately, this is not the case, so we must calculate it ourself.
|
2008-12-02 07:53:19
| 1,228,220,000 |
verified fixed
|
8578b24
| 1,259,090,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/CustomizePerspectiveDialog.java
|
Eclipse_Platform_UI
|
1,639 | 294,303 |
Bug 294303 [Markers] 'Queuing Viewer Updates' in Problems view
| null |
2009-11-05 06:29:29
| 1,257,420,000 |
resolved fixed
|
d5ddffb
| 1,259,080,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/ExtendedMarkersView.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/MarkerCategory.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/MarkerUpdateJob.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/MarkersChangeListener.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/UIUpdateJob.java
|
Eclipse_Platform_UI
|
1,640 | 283,898 |
Bug 283898 [DnD] EditorSiteDragAndDropServiceImpl should remove MergedDropTarget as listener when control gets disposed
|
Build ID: I20090611-1540 Steps To Reproduce: 1. Create a new Plug-in Project with the template "Plug-in with a multi-page editor" 2. Edit the file MultiPageEditor.java: - In method createPage1, replace the fontButton's SelectionAdapter's implementation of method widgetSelected: from: setFont(); to: removePage(0); createPage0(); - (optionally, change the fontButton's text to "Reload") - In method createPage0, force the page to index 0 by changing: from: int index = addPage(editor, getEditorInput()); setPageText(index, editor.getTitle()); to: addPage(0, editor, getEditorInput()); setPageText(0, editor.getTitle()); 3. Launch the project with Run As -> Eclipse Application 4. In the new workbench, create a new General Project 5. In the context menu for the new project, select New -> Other... -> Sample Wizards -> Multi-page Editor file 6. In the "new_file.mpe" tab, edit the text to create a huge document (ex: ~5MB) and Save it 7. In the "Properties" tab, click the Reload button (or Change Font... if it wasn't renamed) many times 8. The replaced editor in page 0 stays in memory and leaks heap (ex: ~10MB) every time the button is pressed More information: When the AbstractTextEditor method createPartControl is called, an instance of MergedDropTarget is added to the DragAndDropService (EditorSiteDragAndDropServiceImpl) tied to the site. The MergedDropTarget holds a reference to a DropTargetListener which is an inner class (DropTargetAdapter) of the AbstractTextEditor. When the AbstractTextEditor is disposed, it does not remove its MergedDropTarget from the DragAndDropService. Normally the DragAndDropService is disposed at the same time as the editor part is closed. But in the case of an AbstractTextEditor added to a MultiPageEditorSite of a MultiPageEditorPart, the AbstractTextEditor can be disposed through a call to removePage on the MultiPageEditorPart, while the DragAndDropService (EditorSiteDragAndDropServiceImpl) remains in memory since there is a single common instance of it tied to the parent MultiPageEditorPart. As a result, since the EditorSiteDragAndDropServiceImpl keeps in its addedListeners table the MergedDropTarget which contains a reference to the AbstractTextEditor's DropTargetAdapter, the removed AbstractTextEditor can not be garbage collected and remains in memory until the whole MultiPageEditorPart is disposed. The proposed solution is to call the method uninstallTextDragAndDrop from within AbstractTextEditor's dispose method. Note 1 (MultiPageEditorPart patch): To remove the MergedDropTarget from the DragAndDropService, the current implementation of AbstractTextEditor's uninstallTextDragAndDrop method needs a reference to the SourceViewer's TextWidget (of class StyledText). In the removePage method of MultiPageEditorPart, the pageControl is disposed before the editor. Consequently, when the AbstractTextEditor's dispose method is called, the SourceViewer's TextWidget has already been disposed and it can no longer be used to remove the MergedDropTarget. The proposed solution is to change the order in the removePage method so that the editor is disposed before the pageControl, which ensures that the TextWidget (StyledText) is still available at that moment. Note 2 (EditorSiteDragAndDropServiceImpl patch): When the MergedDropTarget is created, it creates an internal instance of the class DropTarget and stores it the "realDropTarget" member variable. This instance is also stored in the control's data (the instance of class StyledText) with the DROP_TARGET_KEY. The MergedDropTarget is then added to the listeners of the EditorSiteDragAndDropServiceImpl instance. But when the method removeMergedDropTarget is called with the StyledText control as a parameter, the "realDropTarget" instance of DropTarget is retrieved from the control with the DROP_TARGET_KEY. This DropTarget instance is then attempted to be removed from the listeners of EditorSiteDragAndDropServiceImpl, but since it is the owner MergedDropTarget instance which is stored in the listener table, this remove fails. Also, only the DropTarget instance is disposed. The proposed solution is to loop through all the MergedDropTarget instances in the listener table, and remove and dispose each of them for which the "realDropTarget" is equal to the StyledText control's DropTarget. The DropTarget is then also disposed.
|
2009-07-17 17:08:44
| 1,247,860,000 |
verified fixed
|
9ff35e3
| 1,259,070,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorSiteDragAndDropServiceImpl.java
|
Eclipse_Platform_UI
|
1,641 | 60,574 |
Bug 60574 [Javadoc][EditorMgmt] IWorkbenchPage.getEditors() and .getViews() need explaining
|
The above methods have been deprecated (not sure when). I can hazard a guess that they were deprecated because they have the side effect of instantiating all editors and views in the page. This should be documented in the javadoc for the methods as it is not clear why they were deprecated.
|
2004-04-30 10:41:58
| 1,083,340,000 |
verified fixed
|
d649e52
| 1,259,070,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IWorkbenchPage.java
|
Eclipse_Platform_UI
|
1,642 | 58,474 |
Bug 58474 [EditorMgmt] typo in IEditorReference.getName
|
Should be "May return null IF.." /** * Returns the editor input name. May return null is the * name is not available or if the editor failed to be * restored. */ public String getName();
|
2004-04-14 10:26:42
| 1,081,950,000 |
verified fixed
|
cddf8a6
| 1,259,070,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IEditorReference.java
|
Eclipse_Platform_UI
|
1,643 | 295,880 |
Bug 295880 [context] Context-to-Injector link streamlining
| null |
2009-11-23 10:28:15
| 1,258,990,000 |
resolved fixed
|
0f338c4
| 1,258,990,000 |
bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/ReflectionContributionFactory.java
|
Eclipse_Platform_UI
|
1,644 | 295,611 |
Bug 295611 [UI] The MPart tests leave many open shells
|
This turns out to be caused by the PRE's 'stop' method only working correctly when an MApplication is the 'uiRoot' element.
|
2009-11-19 11:24:54
| 1,258,650,000 |
resolved fixed
|
7079894
| 1,258,650,000 |
bundles/org.eclipse.e4.ui.workbench.swt/src/org/eclipse/e4/ui/workbench/swt/internal/PartRenderingEngine.java
|
Eclipse_Platform_UI
|
1,645 | 293,130 |
Bug 293130 Polishing the Filter extension point
| null |
2009-10-23 05:00:18
| 1,256,290,000 |
resolved fixed
|
7839e56
| 1,258,580,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceFilterGroup.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/AndFileInfoMatcher.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/NotFileInfoMatcher.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/OrFileInfoMatcher.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/StringFileInfoMatcher.java
|
Eclipse_Platform_UI
|
1,646 | 286,107 |
Bug 286107 [ViewMgmt] [GlobalActions] Closing project ignores Saveables
|
CloseResourceAction saves only Editors, while other Saveables (part or non-part) are ignored. This causes data loss (because changes made in f.e. view cannot be saved to closed project on workbench exit).
|
2009-08-10 06:36:42
| 1,249,900,000 |
verified fixed
|
a48f383
| 1,258,490,000 |
tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/api/SaveableMockViewPart.java
|
Eclipse_Platform_UI
|
1,647 | 295,277 |
Bug 295277 Part context is disposed twice when tab item is closed
|
Thread [main] (Suspended (breakpoint at line 305 in EclipseContext)) EclipseContext.dispose() line: 305 ContributedPartRenderer$2.widgetDisposed(DisposeEvent) line: 129 TypedListener.handleEvent(Event) line: 117 EventTable.sendEvent(Event) line: 84 Composite(Widget).sendEvent(Event) line: 1002 Composite(Widget).sendEvent(int, Event, boolean) line: 1026 Composite(Widget).sendEvent(int) line: 1007 Composite(Widget).release(boolean) line: 803 Composite(Widget).dispose() line: 441 ContributedPartRenderer(SWTPartRenderer).disposeWidget(MUIElement) line: 95 PartRenderingEngine.removeGui(MUIElement) line: 306 PartRenderingEngine$1.handleEvent(Event) line: 83 UIEventHandler$1.run() line: 42 Synchronizer.syncExec(Runnable) line: 179 Display.syncExec(Runnable) line: 4364 UIEventHandler.handleEvent(Event) line: 40 EventHandlerWrapper.handleEvent(Event, Permission) line: 177 EventHandlerTracker.dispatchEvent(Object, Object, int, Object) line: 198 EventManager.dispatchEvent(Set, EventDispatcher, int, Object) line: 227 ListenerQueue.dispatchEventSynchronous(int, Object) line: 149 EventAdminImpl.dispatchEvent(Event, boolean) line: 139 EventAdminImpl.sendEvent(Event) line: 78 EventComponent.sendEvent(Event) line: 39 EventBroker.send(String, Object) line: 67 UIEventPublisher.notifyChanged(Notification) line: 69 PartImpl(BasicNotifierImpl).eNotify(Notification) line: 280 PartImpl.setVisible(boolean) line: 394 StackRenderer$8.close(CTabFolderEvent) line: 447 ETabFolder(CTabFolder).onMouse(Event) line: 2189 CTabFolder$1.handleEvent(Event) line: 317 EventTable.sendEvent(Event) line: 84 ETabFolder(Widget).sendEvent(Event) line: 1002 Display.runDeferredEvents() line: 3917 Display.readAndDispatch() line: 3510 PartRenderingEngine$4.run() line: 422 Realm.runWithDefault(Realm, Runnable) line: 332 PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 369 Thread [main] (Suspended (breakpoint at line 305 in EclipseContext)) EclipseContext.dispose() line: 305 PartRenderingEngine.removeGui(MUIElement) line: 316 PartRenderingEngine$1.handleEvent(Event) line: 83 UIEventHandler$1.run() line: 42 Synchronizer.syncExec(Runnable) line: 179 Display.syncExec(Runnable) line: 4364 UIEventHandler.handleEvent(Event) line: 40 EventHandlerWrapper.handleEvent(Event, Permission) line: 177 EventHandlerTracker.dispatchEvent(Object, Object, int, Object) line: 198 EventManager.dispatchEvent(Set, EventDispatcher, int, Object) line: 227 ListenerQueue.dispatchEventSynchronous(int, Object) line: 149 EventAdminImpl.dispatchEvent(Event, boolean) line: 139 EventAdminImpl.sendEvent(Event) line: 78 EventComponent.sendEvent(Event) line: 39 EventBroker.send(String, Object) line: 67 UIEventPublisher.notifyChanged(Notification) line: 69 PartImpl(BasicNotifierImpl).eNotify(Notification) line: 280 PartImpl.setVisible(boolean) line: 394 StackRenderer$8.close(CTabFolderEvent) line: 447 ETabFolder(CTabFolder).onMouse(Event) line: 2189 CTabFolder$1.handleEvent(Event) line: 317 EventTable.sendEvent(Event) line: 84 ETabFolder(Widget).sendEvent(Event) line: 1002 Display.runDeferredEvents() line: 3917 Display.readAndDispatch() line: 3510 PartRenderingEngine$4.run() line: 422 Realm.runWithDefault(Realm, Runnable) line: 332 PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 369
|
2009-11-16 13:26:43
| 1,258,400,000 |
resolved fixed
|
7d5a054
| 1,258,400,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/ContributedPartRenderer.java
|
Eclipse_Platform_UI
|
1,648 | 159,176 |
Bug 159176 [Presentations] Editor minimize/maximize buttons visible on startup even though perspective is fixed
|
In a simple RCP application with one (fixed) perspective and no views (just editors), the editor area minimize/maximize buttons are made visible when workbench is first restored. Opening one or more editors and then closing them removes the buttons for the duration of the session (subsequent editor opening/closing doesn't make the buttons reappear). Even though the buttons are visible, they are not functional (as expected). It appears that when the editor presentation is first created, there is no active perspective in the workbench page and thus WorkbenchPage.isFixedLayout() returns true. This causes the min/max buttons to be made visible. Next time the editor presentation is created (i.e., after closing all initial editors), the perspective is there and WorkbenchPage.isFixedLayout() returns true. This makes the min/max buttons invisible. One workaround is to implement a custom presentation factory, extend createEdirorPresentation and decorate the provided IStackPresentationSite with an implementation that does not support the minimize/maximize states.
|
2006-09-28 14:58:42
| 1,159,470,000 |
verified fixed
|
ecc1330
| 1,258,400,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Perspective.java
|
Eclipse_Platform_UI
|
1,649 | 294,992 |
Bug 294992 [context] Simplify handling of field and method prefixes
|
The context injection uses field and method prefixes to identify items to be injected. I'd like to: - leave one single prefix Currently code allows contexts to override default prefixes. While that might be interesting in theory, it complicates the code as prefixes have to be passed from contexts to object links to injectors. It is unclear if there is any practical use for overriding injection prefixes, especially as focus shifted on annotation-based injections. As such, I think we only need one clearly defined prefix that is sufficiently unique, to be stored in the IContextConstants.INJECTION_PREFIX. - change prefix value from "inject_" to "inject__" (two underscores at the end) With the point above, I'd like to strengthen uniqueness of our injection prefix. "inject__" seems be easy to read and sufficiently unique. The patch also removes IContextConstants.OUTPUTS that are no longer used.
|
2009-11-12 12:03:44
| 1,258,050,000 |
resolved fixed
|
98f0a91
| 1,258,050,000 |
bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/ActiveChildOutputFunction.java
|
Eclipse_Platform_UI
|
1,650 | 294,777 |
Bug 294777 [context] Clarify default state of @Optional
|
The "@Optional" annotation now is mixed up about its default state. The Javadoc says that its default state is "true", while some code paths think it is "false". What we need to consider: - in *all* cases in demos we have so far we use "@Optional(true)" - the original intent was (AFAIK): constructors: default is @Optional(false) method arguments: default is @Optional(false) methods on #make: default should be @Optional(true) ? I'd like to propose the following scheme based on the patters we see in demos: - arguments (of either method or constructor) are required by default - calling injectable methods [and setting fields] is optional by default This would mean that any explicit calls (#invoke(), #make()) must have their arguments available in the context to succeed. However, any calls generated by DI behind the scene (as a result of #inject()) are optional. On, in other terms, we don't have to call injectable methods unless specifically instructed. However, if we do call a method, we expect its arguments to be in the context. (This, of course, is the deafult state and can be change by using @Optional annotation.) The upside of this approach is that it fits well into patterns we see in the E4 demos (= DI "just works"). The downside is that, as evident from this text, it is not that easy to explain exactly what are the default states. From simplicicty of the programming model, it would be much better to just say that the default is always true or always false. Any opinions on this proposal?
|
2009-11-10 13:42:48
| 1,257,880,000 |
resolved fixed
|
2e46876
| 1,258,040,000 |
examples/org.eclipse.e4.demo.contacts/src/org/eclipse/e4/demo/contacts/views/DetailsView.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/ExifTable.java
|
Eclipse_Platform_UI
|
1,651 | 294,738 |
Bug 294738 [Viewers] (JFace) Assertion for missing LabelProvider in ViewerColumn
|
ViewerColumn should throw an AssertionException if the LabelProvider is missing for a column to provide a helpful error message.
|
2009-11-10 09:08:11
| 1,257,860,000 |
verified fixed
|
9666544
| 1,257,990,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerColumn.java
|
Eclipse_Platform_UI
|
1,652 | 292,247 |
Bug 292247 [Viewers] StructuredViewer.findItems(Object) javadoc is not precise
|
The javadoc says "If the element map is disabled, the widget is found via <code>doFindInputItem</code>." but in the code method doFindItem is called.
|
2009-10-14 08:32:38
| 1,255,520,000 |
verified fixed
|
75dd40c
| 1,257,980,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StructuredViewer.java
|
Eclipse_Platform_UI
|
1,653 | 289,409 |
Bug 289409 [Viewers] ILazyTreePathContentProvider documentation request
|
I believe the JavaDoc for ILazyTreePathContentProvider#updateElement() should mention that the implementation can call TreeViewer#setHasChildren() instead of TreeViewer#setChildCount() if the content provider can more efficiently determine the has-children status than it can the actual number of children. This optimization was made possible by 156883. I think it needs to be advertised so clients can take advantage of it in their implementation of ILazyTreePathContentProvider#updateElement(). In fact, I think clients that use ILazyTreeContentProvider also have access to that optimization. If so, that JavaDoc should be updated, too.
|
2009-09-14 22:20:10
| 1,252,980,000 |
verified fixed
|
ddc7768
| 1,257,960,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ILazyTreeContentProvider.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ILazyTreePathContentProvider.java
|
Eclipse_Platform_UI
|
1,654 | 294,307 |
Bug 294307 [ErrorHandling] StatusDialogManagerTest failure in N20091104-2000
|
There were 2 failures in last nights tests: expected:<org.eclipse.ui.statushandlers.StatusAdapter@c65dad> but was:<org.eclipse.ui.statushandlers.StatusAdapter@cc6a3b> junit.framework.AssertionFailedError: expected:<org.eclipse.ui.statushandlers.StatusAdapter@c65dad> but was:<org.eclipse.ui.statushandlers.StatusAdapter@cc6a3b> at org.eclipse.ui.tests.statushandlers.StatusDialogManagerTest.testList2(StatusDialogManagerTest.java:578) expected:<[TEST_MESSAGE_2]> but was:<[See 'Details' for more information.]> at org.eclipse.ui.tests.statushandlers.StatusDialogManagerTest.testList3(StatusDialogManagerTest.java:602)
|
2009-11-05 07:30:30
| 1,257,420,000 |
verified fixed
|
b8c6f60
| 1,257,780,000 |
tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/statushandlers/StatusDialogManagerTest.java
|
Eclipse_Platform_UI
|
1,655 | 294,497 |
Bug 294497 NPE thrown when switching between populated and empty albums
|
1. Run the photo demo. 2. Select an album with pictures in it. 3. Select the 'Exif' part. 4. Select an entry in the table. 5. Select an empty album. 6. An NPE is thrown. java.lang.NullPointerException at java.util.Hashtable.put(Unknown Source) at org.eclipse.e4.ui.services.internal.events.EventBroker.constructEvent(EventBroker.java:91) at org.eclipse.e4.ui.services.internal.events.EventBroker.post(EventBroker.java:72) at org.eclipse.e4.demo.e4photo.ExifTable$2.selectionChanged(ExifTable.java:161) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162) at org.eclipse.jface.util.SafeRunnable$1.run(SafeRunnable.java:128) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2132) at org.eclipse.jface.viewers.TableViewer.remove(TableViewer.java:417) at org.eclipse.jface.viewers.AbstractTableViewer.remove(AbstractTableViewer.java:856) at org.eclipse.jface.internal.databinding.viewers.TableViewerUpdater.remove(TableViewerUpdater.java:36) at org.eclipse.jface.databinding.viewers.ObservableListContentProvider$2.handleRemove(ObservableListContentProvider.java:124) at org.eclipse.core.databinding.observable.list.ListDiff.accept(ListDiff.java:137) at org.eclipse.jface.databinding.viewers.ObservableListContentProvider$Impl.handleListChange(ObservableListContentProvider.java:118) at org.eclipse.core.databinding.observable.list.ListChangeEvent.dispatch(ListChangeEvent.java:61) at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) at org.eclipse.core.databinding.observable.list.ObservableList.fireListChange(ObservableList.java:73) at org.eclipse.core.databinding.observable.list.WritableList.clear(WritableList.java:269) at org.eclipse.e4.demo.e4photo.ExifTable.setSelection(ExifTable.java:81) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.e4.core.services.internal.context.ContextInjector.callMethod(ContextInjector.java:561) at org.eclipse.e4.core.services.internal.context.ContextInjector.access$2(ContextInjector.java:538) at org.eclipse.e4.core.services.internal.context.ContextInjector$Processor.processMethod(ContextInjector.java:108) at org.eclipse.e4.core.services.internal.context.ContextInjector.processMethods(ContextInjector.java:376) at org.eclipse.e4.core.services.internal.context.ContextInjector.processClass(ContextInjector.java:319) at org.eclipse.e4.core.services.internal.context.ContextInjector.processClassHierarchy(ContextInjector.java:335) at org.eclipse.e4.core.services.internal.context.ContextInjector.inject(ContextInjector.java:211) at org.eclipse.e4.core.services.internal.context.ContextToObjectLink.handleAdd(ContextToObjectLink.java:59) at org.eclipse.e4.core.services.internal.context.ContextToObjectLink.notify(ContextToObjectLink.java:152) at org.eclipse.e4.core.services.internal.context.EclipseContext$TrackableComputationExt.notify(EclipseContext.java:197) at org.eclipse.e4.workbench.ui.internal.UISchedulerStrategy$1.run(UISchedulerStrategy.java:40) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152) at org.eclipse.jface.databinding.swt.SWTObservables$DisplayRealm.access$0(SWTObservables.java:1) at org.eclipse.jface.databinding.swt.SWTObservables$1.run(SWTObservables.java:502) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3892)
|
2009-11-06 13:06:46
| 1,257,530,000 |
resolved fixed
|
aa6fca6
| 1,257,530,000 |
bundles/org.eclipse.e4.ui.services/src/org/eclipse/e4/ui/services/internal/events/EventBroker.java
|
Eclipse_Platform_UI
|
1,656 | 294,493 |
Bug 294493 XMI definition of part icon is ignored
|
The icon URI definition for parts seem to be ignored as the part tabs don't have any icons.
|
2009-11-06 12:40:23
| 1,257,530,000 |
resolved fixed
|
c5baf0d
| 1,257,530,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/SWTPartRenderer.java tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/application/UIStartupTest.java tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/workbench/MPartTest.java
|
Eclipse_Platform_UI
|
1,657 | 294,046 |
Bug 294046 Improve the FileListControl
| null |
2009-11-03 07:34:07
| 1,257,250,000 |
resolved fixed
|
19ab3a8
| 1,257,340,000 |
tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/UIAllTests.java tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/workbench/MPartTest.java
|
Eclipse_Platform_UI
|
1,658 | 294,096 |
Bug 294096 Changing a MPart's name does not alter the CTabItem's text
| null |
2009-11-03 13:21:22
| 1,257,270,000 |
verified fixed
|
570be43
| 1,257,280,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/StackRenderer.java
|
Eclipse_Platform_UI
|
1,659 | 288,767 |
Bug 288767 [statushandling]no option to wrap error text
| null |
2009-09-07 12:42:47
| 1,252,340,000 |
verified fixed
|
2bc210c
| 1,257,240,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/statushandlers/DefaultDetailsArea.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/statushandlers/WorkbenchStatusDialogManager.java
|
Eclipse_Platform_UI
|
1,660 | 293,787 |
Bug 293787 Markers view not filtering by workingsets
| null |
2009-10-30 09:55:04
| 1,256,910,000 |
verified fixed
|
30120d0
| 1,256,920,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/MarkerContentGenerator.java
|
Eclipse_Platform_UI
|
1,661 | 293,600 |
Bug 293600 Failure in StatusDialogManagerTest.testBug288765
| null |
2009-10-28 13:28:33
| 1,256,750,000 |
verified fixed
|
31a2162
| 1,256,820,000 |
tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/statushandlers/StatusDialogManagerTest.java
|
Eclipse_Platform_UI
|
1,662 | 289,988 |
Bug 289988 Use IResource#setDerived(boolean, IProgressMonitor) instead of IResource#setDerived(boolean)
| null |
2009-09-21 07:05:42
| 1,253,530,000 |
resolved fixed
|
97890db
| 1,256,730,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceInfoPage.java
|
Eclipse_Platform_UI
|
1,663 | 293,357 |
Bug 293357 [context] Switch annotation processing to JSR 330
| null |
2009-10-26 15:14:56
| 1,256,580,000 |
resolved fixed
|
743b62e
| 1,256,680,000 |
bundles/org.eclipse.e4.core.commands/src/org/eclipse/e4/core/commands/internal/CommandServiceImpl.java bundles/org.eclipse.e4.core.commands/src/org/eclipse/e4/core/commands/internal/HandlerServiceImpl.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/LazyStackRenderer.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/MenuItemRenderer.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/StackRenderer.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/WBWRenderer.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/WorkbenchLogger.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/ExifTable.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Preview.java examples/org.eclipse.e4.demo.e4photo/src/org/eclipse/e4/demo/e4photo/Thumbnails.java tests/org.eclipse.e4.core.commands.tests/src/org/eclipse/e4/core/commands/tests/HandlerTest.java
|
Eclipse_Platform_UI
|
1,664 | 293,346 |
Bug 293346 annotation refactoring causes test NPEs
|
I have 2 test failures in my command test suite: CommandTestSuite org.eclipse.e4.core.commands.tests.CommandTestSuite org.eclipse.e4.core.commands.tests.HandlerTest testMethodInfo(org.eclipse.e4.core.commands.tests.HandlerTest) java.lang.NullPointerException testMethodWithAnnocation(org.eclipse.e4.core.commands.tests.HandlerTest) java.lang.NullPointerException The NPEs look like: java.lang.NullPointerException at org.osgi.util.tracker.ServiceTracker.<init>(ServiceTracker.java:198) at org.eclipse.e4.internal.core.services.osgi.OSGiContextStrategy.lookup(OSGiContextStrategy.java:120) at org.eclipse.e4.core.services.internal.context.EclipseContext.internalGet(EclipseContext.java:356) at org.eclipse.e4.core.services.internal.context.EclipseContext.internalGet(EclipseContext.java:380) at org.eclipse.e4.core.services.internal.context.EclipseContext.internalGet(EclipseContext.java:380) at org.eclipse.e4.core.services.internal.context.EclipseContext.get(EclipseContext.java:325) at org.eclipse.e4.core.services.internal.context.ContextToObjectLink.processInvoke(ContextToObjectLink.java:610) at org.eclipse.e4.core.services.internal.context.ContextInjectionImpl.invoke(ContextInjectionImpl.java:60) at org.eclipse.e4.core.services.context.spi.ContextInjectionFactory.invoke(ContextInjectionFactory.java:143) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:113) at org.eclipse.e4.core.commands.tests.HandlerTest.testMethodInfo(HandlerTest.java:231) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.CoreTestApplication.run(CoreTestApplication.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:367) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:611) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:566) at org.eclipse.equinox.launcher.Main.run(Main.java:1363) at org.eclipse.equinox.launcher.Main.main(Main.java:1339)
|
2009-10-26 13:41:13
| 1,256,580,000 |
resolved fixed
|
3f37799
| 1,256,580,000 |
tests/org.eclipse.e4.core.commands.tests/src/org/eclipse/e4/core/commands/tests/HandlerTest.java
|
Eclipse_Platform_UI
|
1,665 | 293,310 |
Bug 293310 NPE when adding a String Matcher with no matching string
| null |
2009-10-26 09:46:38
| 1,256,560,000 |
resolved fixed
|
cddc98d
| 1,256,570,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/StringMatcherFilter.java
|
Eclipse_Platform_UI
|
1,666 | 293,303 |
Bug 293303 NPE when adding a Regular Expression with no matching string
|
I20091025-2000 Steps: 1. Open Resource Filters properties page for a folder 2. Add an Exclude filter of type Regular Expression 3. Do *not* enter a matching string and press OK => Take a look at the Error Log: java.lang.NullPointerException at org.eclipse.core.internal.resources.RegexFilterFactory$RegexFilterType.matches(RegexFilterFactory.java:36) at org.eclipse.core.internal.resources.Filter.match(Filter.java:57) at org.eclipse.core.internal.resources.Filter.filterExcludes(Filter.java:147) at org.eclipse.core.internal.resources.Filter.filter(Filter.java:100) at org.eclipse.core.internal.resources.Resource.filterChildren(Resource.java:2228) at org.eclipse.core.internal.localstore.UnifiedTree.getLocalList(UnifiedTree.java:344) at org.eclipse.core.internal.localstore.UnifiedTree.addChildren(UnifiedTree.java:137) at org.eclipse.core.internal.localstore.UnifiedTree.addNodeChildrenToQueue(UnifiedTree.java:243) at org.eclipse.core.internal.localstore.UnifiedTree.accept(UnifiedTree.java:109) at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:790) at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:774) at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1779) at org.eclipse.core.internal.refresh.RefreshJob.runInWorkspace(RefreshJob.java:166) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
|
2009-10-26 08:20:12
| 1,256,560,000 |
verified fixed
|
828d13e
| 1,256,560,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/StringMatcherFilter.java
|
Eclipse_Platform_UI
|
1,667 | 292,672 |
Bug 292672 IWorkbenchPage's showView(String, String, int) method has grammatical problems
| null |
2009-10-19 10:00:51
| 1,255,960,000 |
closed fixed
|
c9fc84b
| 1,256,400,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IWorkbenchPage.java
|
Eclipse_Platform_UI
|
1,668 | 293,199 |
Bug 293199 [FieldAssist] Content assist popup appears in the wrong location (bounds are incorrect)
|
When content assist is attached to a Text widget, the location of the suggestion popup is incorrect. Content assist is applied as follows: bc. TextContentAdapter textContentAdapter = new TextContentAdapter(); IContentProposalProvider provider = // provider ContentAssistCommandAdapter adapter = new ContentAssistCommandAdapter(nameText, textContentAdapter, provider, org.eclipse.ui.fieldassist.ContentAssistCommandAdapter.CONTENT_PROPOSAL_COMMAND, new char[0],true); adapter.setProposalAcceptanceStyle(ContentAssistCommandAdapter.PROPOSAL_REPLACE); I'm not sure if it matters, the Text is embedded in an expandable section in a SashForm in a multipage editor. attaching two screenshots showing popup placement issue.
|
2009-10-23 13:00:23
| 1,256,320,000 |
verified fixed
|
c7e8787
| 1,256,340,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
1,669 | 190,288 |
Bug 190288 [About] Allow sorting by secondary column in plug-in details dialog
|
It would be nice if we could sort by a second column in this dialog in the event that two or more elements are equal based on their primary column.
|
2007-05-31 13:37:30
| 1,180,630,000 |
verified fixed
|
6df258a
| 1,256,250,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/AboutPluginsPage.java
|
Eclipse_Platform_UI
|
1,670 | 288,766 |
Bug 288766 [statushandling] initial size is small, could be a ratio of error content
| null |
2009-09-07 12:41:11
| 1,252,340,000 |
verified fixed
|
f6adcb3
| 1,256,220,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/statushandlers/DefaultDetailsArea.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/statushandlers/StatusDialogManagerTest.java
|
Eclipse_Platform_UI
|
1,671 | 250,604 |
Bug 250604 [FieldAssist] API - ContentProposalAdapter needs isShowing() method
|
Please implement a method ContentProposalAdapter.isShwoing(). The method should return a boolean whether the content assistant proposal popup is open or not.
|
2008-10-13 02:54:16
| 1,223,880,000 |
verified fixed
|
1c4020c
| 1,256,170,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/FieldAssistTestCase.java
|
Eclipse_Platform_UI
|
1,672 | 292,901 |
Bug 292901 Confusing "Target" group for children filters
|
Steps: 1) I added a compound filter "or" and set "Mode" to "Exclude" and "Target" to "Folders" 2) I tried to add "Regex Filter" as a child for the compound one, and I see that I can choose "Target" here too Maybe we should choose "Target" only for top-level filters as we do with "Mode"? Or "Mode" should be available to set only if not already chosen for the parent?
|
2009-10-21 10:25:52
| 1,256,140,000 |
resolved fixed
|
cd77c53
| 1,256,150,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceFilterGroup.java
|
Eclipse_Platform_UI
|
1,673 | 193,600 |
Bug 193600 [Commands] org.eclipse.ui.menus/menuContribution locationURI query placement "endof=..." not implemented?
|
Build id: I20070608-1718 According to the specification of org.eclipse.ui.menus/menuContribution/separator, the query placement "endof=..." should be support in the locationURI: see the description of the na,e attribute below. <!ELEMENT separator EMPTY> <!ATTLIST separator name CDATA #REQUIRED visible (true | false) > Inserts a separator at the current insertion point. name - The 'id' of this contribution. If defined then it can be used as a reference in the Query part of the location defining whether the additions are to go before or after this element (or at the end of the logical group containing this element using the 'endOf' value). Separator contributions that have an id define the start of a logical group so the result of using the 'endof' value for placement is to search forward in the current menu to locate the next id'd separator and to place the inserted elements before that element. If no trailing separator is found then the items are placed at the end of the menu. visible - Indicates whether or not the separator should be visible in the UI. false by default.
|
2007-06-20 15:22:14
| 1,182,370,000 |
verified fixed
|
9c156c4
| 1,256,070,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/WorkbenchMenuService.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/menus/MenuUtil.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/menus/MenuPopulationTest.java
|
Eclipse_Platform_UI
|
1,674 | 292,762 |
Bug 292762 [Contributions] MenuUtil provides constants and static methods ... it should be marked noextend
|
MenuUtil has always been a utility class that we use to publish our menu contribution locationURIs. We just forgot to mark it as @noextend. I'd like to do that now. PW
|
2009-10-20 08:55:06
| 1,256,040,000 |
verified fixed
|
8acc813
| 1,256,050,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/menus/MenuUtil.java
|
Eclipse_Platform_UI
|
1,675 | 292,759 |
Bug 292759 The "Edit Resource Filter" dialog doesn't populate the "Type" field
|
Steps: 1) Open the "Edit Resource Filter" dialog on a compound filter 2) See, that "Type" is not populated
|
2009-10-20 07:04:58
| 1,256,040,000 |
verified fixed
|
cd448a8
| 1,256,050,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceFilterGroup.java
|
Eclipse_Platform_UI
|
1,676 | 280,799 |
Bug 280799 [Commands] ActivateEditorHandler unnecessarily calls setFocus()
|
Build id: I20090603-2000 According to setFocus()'s javadoc... Clients should not call this method (the workbench calls this method at appropriate times). To have the workbench activate a part, use IWorkbenchPage.activate(IWorkbenchPart) instead. In ActivateEditorHandler, activate(IWorkbenchPart) is invoked quickly followed by a setFocus() invocation on lines 57 and 58. From the stack trace below, setFocus() is already called when activate(IWorkbenchPart) is invoked, so the explicit call to setFocus() appears to serve no purpose. Thread [main] (Suspended (breakpoint at line 6077 in AbstractTextEditor)) CompilationUnitEditor(AbstractTextEditor).setFocus() line: 6077 CompilationUnitEditor(JavaEditor).setFocus() line: 2362 EditorPane(PartPane).setFocus() line: 332 EditorPane.setFocus() line: 127 WorkbenchPage$3.run() line: 626 SafeRunner.run(ISafeRunnable) line: 42 Platform.run(ISafeRunnable) line: 888 WorkbenchPage.activatePart(IWorkbenchPart) line: 621 WorkbenchPage.setActivePart(IWorkbenchPart) line: 3527 WorkbenchPage.activate(IWorkbenchPart) line: 614 ActivateEditorHandler.execute(ExecutionEvent) line: 57 Thread [main] (Suspended (breakpoint at line 6077 in AbstractTextEditor)) CompilationUnitEditor(AbstractTextEditor).setFocus() line: 6077 CompilationUnitEditor(JavaEditor).setFocus() line: 2362 ActivateEditorHandler.execute(ExecutionEvent) line: 58
|
2009-06-18 12:25:03
| 1,245,340,000 |
verified fixed
|
712c766
| 1,256,040,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ActivateEditorHandler.java
|
Eclipse_Platform_UI
|
1,677 | 291,755 |
Bug 291755 [Filters] Filters implementation and API cleanup
|
This bug is raised to track reviewing and cleanup of filters API and implementation.
|
2009-10-08 10:26:46
| 1,255,010,000 |
resolved fixed
|
f4b8a79
| 1,256,030,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceFilterGroup.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/AndResourceFilter.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/CompoundResourceFilter.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/NotResourceFilter.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/OrResourceFilter.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/StringMatcherFilter.java
|
Eclipse_Platform_UI
|
1,678 | 259,048 |
Bug 259048 [Contributions] toolbar control contributions cause plugin startup
| null |
2008-12-16 19:47:10
| 1,229,470,000 |
verified fixed
|
9afb79c
| 1,256,020,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/DynamicToolBarContributionItem.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/MenuAdditionCacheEntry.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/menus/WorkbenchWindowControlContribution.java
|
Eclipse_Platform_UI
|
1,679 | 290,964 |
Bug 290964 Factor out model loading from Workbench so that it is plugable
|
We want to support different workbench restoreing possibilities and for this we need to delegate the loading to an external instance
|
2009-09-30 16:08:05
| 1,254,340,000 |
resolved fixed
|
6340f4c
| 1,255,970,000 |
bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/ResourceHandler.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Workbench.java
|
Eclipse_Platform_UI
|
1,680 | 277,886 |
Bug 277886 [IDE] Remove manual start of org.eclipse.update.configurator
| null |
2009-05-26 12:00:09
| 1,243,350,000 |
verified fixed
|
ddf3ece
| 1,255,960,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchPlugin.java
|
Eclipse_Platform_UI
|
1,681 | 165,180 |
Bug 165180 [Progress] org.eclipse.ui.progress.IProgressService#runInUI does not make clear expectations
|
Based on the name I would expect ProgressManager.runInUI to run the given IRunnableWithProgress on the UI thread. THe java doc says: Runs the given operation in the UI thread using the given runnable context. But to my surprise the code fails to run on the UI thread. Here is the first bit of runInUI: final IJobManager manager = Platform.getJobManager(); final InvocationTargetException[] exception = new InvocationTargetException[1]; final InterruptedException[] canceled = new InterruptedException[1]; BusyIndicator.showWhile(... As you can see there is no code to consider this thread or the UI thread and certainly no effort to switch threads. When BusyIndicator.showWhile runs, it fails in a call to checkDevice() inside of display.getSystemCursor(). So either the code is seriously confused or the documentation. It certainly has me confused ;-).
|
2006-11-20 12:17:14
| 1,164,040,000 |
resolved fixed
|
e2c92c9
| 1,255,940,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressManager.java
|
Eclipse_Platform_UI
|
1,682 | 256,651 |
Bug 256651 [FieldAssist] Wrong location calculation of proposal popup shell if content control is near bottom in the screen
| null |
2008-11-26 10:14:51
| 1,227,710,000 |
verified fixed
|
193cd09
| 1,255,650,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/AbstractFieldAssistTestCase.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/AbstractFieldAssistWindow.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/FieldAssistTestCase.java
|
Eclipse_Platform_UI
|
1,683 | 288,804 |
Bug 288804 [FieldAssist] [JFace] ContentProposalAdapter needs new setFocus() method
|
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729) Build Identifier: I20090611-1540 Please implement a public setFocus() method for ContentProposalAdapter. Is needed to set the focus to the control manually. Reproducible: Always
|
2009-09-08 05:01:18
| 1,252,400,000 |
verified fixed
|
f8d1ba0
| 1,255,560,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/AbstractFieldAssistWindow.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/FieldAssistTestCase.java
|
Eclipse_Platform_UI
|
1,684 | 284,330 |
Bug 284330 [JFace] Add isVisible API to ControlDecoration
|
Build ID: 3.5 Steps To Reproduce: This is an enhancement request. I would like to be able to programmatically determine if a ControlDecoration is visible. This is especially useful for testing.
|
2009-07-22 16:26:37
| 1,248,290,000 |
verified fixed
|
ffcc3e7
| 1,255,560,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ControlDecoration.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/FieldAssistTestCase.java
|
Eclipse_Platform_UI
|
1,685 | 262,022 |
Bug 262022 [FieldAssist] ContentProposalAdapter.recomputeProposals might throw a NPE
|
When a control using content proposal gets disposed during usage the recomputeProposals() method might throw a NPE. This is caused by getting "allProposals" using a call to getProposals() which is allowed to return null. When using allProposals.length this will crash. I'm not sure if the simple solution if ((allProposals == null) || (allProposals.length == 0) { proposals = new IContentProposal[0]; close(); } else { // cont. will work or if the popup will have problems with a disposed control.
|
2009-01-22 10:14:14
| 1,232,640,000 |
verified fixed
|
a7a963c
| 1,255,560,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/FieldAssistTestCase.java
|
Eclipse_Platform_UI
|
1,686 | 279,553 |
Bug 279553 [FieldAssist] ControlDecoration strange behavior when description text is empty string
|
Build ID: 3.5RC3 With the following simple code, when I hover over the control decoration, a huge yellow box quickly flashes on the screen and then disappears. I also tried on 3.4.2 and observed the same behavior. Display display = new Display(); Shell shell = new Shell(display); shell.setLayout(new GridLayout(1, false)); Text t = new Text(shell, SWT.BORDER); t.setText("hover on decoration ->"); ControlDecoration decoration = new ControlDecoration(t, SWT.RIGHT); decoration.setImage(FieldDecorationRegistry.getDefault() .getFieldDecoration(FieldDecorationRegistry.DEC_INFORMATION).getImage()); decoration.setDescriptionText(""); shell.pack(); shell.open(); while (!isInterrupted() && !shell.isDisposed()) { if (!display.readAndDispatch()) display.sleep(); } display.dispose();
|
2009-06-08 22:28:12
| 1,244,510,000 |
verified fixed
|
da16435
| 1,255,560,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ControlDecoration.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/AbstractFieldAssistTestCase.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/fieldassist/FieldAssistTestCase.java
|
Eclipse_Platform_UI
|
1,687 | 292,170 |
Bug 292170 [CSS] Missing license headers in org.eclipse.e4.ui.css.legacy and org.eclipse.e4.ui.examples.css.rcp
|
Will fix this after M1 is declared.
|
2009-10-13 13:31:36
| 1,255,460,000 |
resolved fixed
|
5984cc2
| 1,255,540,000 |
examples/org.eclipse.e4.ui.examples.css.rcp/src/org/eclipse/e4/ui/examples/css/rcp/Activator.java examples/org.eclipse.e4.ui.examples.css.rcp/src/org/eclipse/e4/ui/examples/css/rcp/Application.java examples/org.eclipse.e4.ui.examples.css.rcp/src/org/eclipse/e4/ui/examples/css/rcp/ApplicationActionBarAdvisor.java examples/org.eclipse.e4.ui.examples.css.rcp/src/org/eclipse/e4/ui/examples/css/rcp/ApplicationWorkbenchAdvisor.java examples/org.eclipse.e4.ui.examples.css.rcp/src/org/eclipse/e4/ui/examples/css/rcp/ICommandIds.java examples/org.eclipse.e4.ui.examples.css.rcp/src/org/eclipse/e4/ui/examples/css/rcp/MarkAsReadAction.java examples/org.eclipse.e4.ui.examples.css.rcp/src/org/eclipse/e4/ui/examples/css/rcp/OpenViewAction.java examples/org.eclipse.e4.ui.examples.css.rcp/src/org/eclipse/e4/ui/examples/css/rcp/Perspective.java
|
Eclipse_Platform_UI
|
1,688 | 287,454 |
Bug 287454 [KeyBindings] F16-F19 unusable as shortcut keys in General -> Keys
| null |
2009-08-24 12:35:48
| 1,251,130,000 |
verified fixed
|
627c4c5
| 1,255,460,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/bindings/keys/IKeyLookup.java bundles/org.eclipse.jface/src/org/eclipse/jface/bindings/keys/SWTKeyLookup.java
|
Eclipse_Platform_UI
|
1,689 | 276,164 |
Bug 276164 [KeyBindings] Mac: Exporting keyboard preferences to CSV writes question marks instead of modifiers such as "Ctrl" and special keys like "Up"
|
Build ID: I20090430-2300 Steps To Reproduce: 1. Mac Carbon or Cocoa 2. Preferences, General > Keys 3. Click "Export CSV" and export a CSV file Result: The CSV file has a lot of question marks where it should have modifiers like "Ctrl". For example, one line says: "Edit","Quick Fix","?1","In Dialogs and Windows" In other places, question marks are written for other keys such as the up arrow. The "Move Lines Up" command is assigned to Option+Up, but it shows up like this: "Text Editing","Move Lines Up","??","Editing Text" Windows does it right, e.g. the shortcut for "Move Lines Up" is written out as "Alt+Up".
|
2009-05-13 14:38:27
| 1,242,240,000 |
verified fixed
|
b0b25e6
| 1,255,460,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/model/KeyController.java
|
Eclipse_Platform_UI
|
1,690 | 199,127 |
Bug 199127 [Commands] ContentAssistCommandAdapter#setEnabled(..) does not update handler activation
|
I20070807-0010 ContentAssistCommandAdapter#setEnabled(..) does not enable/disable the command handlers on the Mac. To reproduce, open the Find/Replace dialog on a text editor and then toggle the Regular Expressions checkbox. The lightbulb on the find field is correctly added/removed, but the availability of Ctrl+Space to open the content assist proposals popup is only updated when the field has lost focus. The problem is not reproducible on Windows, probably because the find field always loses focus on Windows when the checkbox is toggled.
|
2007-08-07 13:27:15
| 1,186,510,000 |
verified fixed
|
b52b87a
| 1,255,460,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/fieldassist/ContentAssistCommandAdapter.java
|
Eclipse_Platform_UI
|
1,691 | 290,834 |
Bug 290834 [JFace] Unnecessary call in every saferunner invocation
|
In JFaceUtil.initializeJFace() an ISafeRunnableRunner() is set as the singleton runner. Thing is, the implementation uses the deprecated method Platform#run. That simply calls SafeRunner#run(), and is deprecated mentioning that developers should call that instead. So, we basically have an extraneous call in every use of SafeRunner. Considering how often that is used, and how easy it is to avoid the extraneous method call, seems like a no-brainer to just adjust this.
|
2009-09-29 14:16:46
| 1,254,250,000 |
verified fixed
|
77638e4
| 1,255,450,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/JFaceUtil.java
|
Eclipse_Platform_UI
|
1,692 | 282,653 |
Bug 282653 [Markers] [ErrorHandling] Problems view: strange dialog if no quick fix is found
|
R3.5 (and R3.4). A strange/ugly dialog is shown if the marker resolution generator claims to have quick fixes (==> menu enabled) but when executed doesn't return any resolutions. 1. missing '.' 2. Details button which reveals nothing new (same message as above is shown) Given this is just an info I would expect this to appear in a simple info dialog. Code is in org.eclipse.ui.internal.views.markers.QuickFixHandler.execute(ExecutionEvent) after if (resolutions.isEmpty()) {
|
2009-07-07 06:43:25
| 1,246,960,000 |
verified fixed
|
29385af
| 1,255,440,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/QuickFixHandler.java
|
Eclipse_Platform_UI
|
1,693 | 275,477 |
Bug 275477 [Markers] TasksView: Scope settings selects two (!) radio buttons
|
Found with 3.5 M7. To reproduce: 1. Open Tasks View 2. View Menu > Configure Contents... 3. Scope section click on 'Select' 4. 'No working sets' 5. Ok Result: two radio buttons are selected: 'On selected element and its children' and 'On working set'. Expected: 'On working set' should be selected. Screencast at URL shows example.
|
2009-05-08 11:45:01
| 1,241,800,000 |
closed fixed
|
3024819
| 1,255,430,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/ScopeArea.java
|
Eclipse_Platform_UI
|
1,694 | 282,535 |
Bug 282535 [Markers] The Problem view does not update the status line
|
Build ID: M20090211-1700 Steps To Reproduce: 1. Set the "Build Automatically" property to true 1. Edit a JAVA file and introduce an error on purpose 2. Save the file => The error is displayed in the Problems View 3. Click on that error in the Problems view => the status line is updated to show the error description 4. Fix the problem in the JAVA file and save it => the Problems view is cleared 5. Set the focus on the Problems view = > the status line is updated to show the error description although this error was fixed More information:
|
2009-07-06 11:13:19
| 1,246,890,000 |
closed fixed
|
a8555e8
| 1,255,430,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/ExtendedMarkersView.java
|
Eclipse_Platform_UI
|
1,695 | 274,262 |
Bug 274262 [History] Allow to never prune history
|
I20090429-0100. I never want to loose my history and I never want to waste time on shutdown (or start up) to do any history pruning. Please add a preference to disable pruning entirely.
|
2009-04-29 05:16:21
| 1,241,000,000 |
verified fixed
|
71e7cc5
| 1,255,430,000 |
bundles/org.eclipse.ui.ide.application/src/org/eclipse/ui/internal/ide/application/IDEWorkbenchAdvisor.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchMessages.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/FileStatesPage.java
|
Eclipse_Platform_UI
|
1,696 | 281,145 |
Bug 281145 [CheatSheet] Simple mechanism to publish internal resources of cheatsheet plugin via http urls
|
Build ID: M20080221-1800 Steps To Reproduce: 1. Create a new cheatsheet plugin 2. Add a contribution to the org.eclipse.ui.cheatsheets.cheatSheetContent extension 3. Add a category 4. Create a new cheatsheet file using the New Wizard 5. Register the new cheatsheet file 6. Add a jpg file or an html file to the plugin project 7. Add a command to a cheatsheet step or sub-step. In the browse dialog select the Open Browser command 8. In the url option for the Open Browser command, specify the path to the jpg or html file created in step 6. I have tried all different combinations of paths with the plugin id, without the plugin id, with a jar url 9. Preview the cheatsheet file and click on the Open Browser action which should open a browser window with the jpg or html file displayed. More information: I have made sure that the html or jpg resource is exported in the plugin editor.
|
2009-06-22 16:36:35
| 1,245,700,000 |
resolved fixed
|
2fe599e
| 1,255,380,000 |
bundles/org.eclipse.ui.browser/src/org/eclipse/ui/internal/browser/OpenBundleResourceHandler.java
|
Eclipse_Platform_UI
|
1,697 | 259,357 |
Bug 259357 [StatusHandling] Perspective registry hides message from WorkbenchException's status
|
Perspective registry hides message from WorkbenchException's status by overriding it with predefined message
|
2008-12-19 06:55:38
| 1,229,690,000 |
verified fixed
|
6b8f580
| 1,255,350,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/registry/PerspectiveRegistry.java
|
Eclipse_Platform_UI
|
1,698 | 288,769 |
Bug 288769 [statushandling] can't deselect text
| null |
2009-09-07 12:46:06
| 1,252,340,000 |
verified fixed
|
0f72a5e
| 1,255,280,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/statushandlers/DefaultDetailsArea.java
|
Eclipse_Platform_UI
|
1,699 | 291,934 |
Bug 291934 Sash tests failing over part renderer call
| null |
2009-10-09 12:47:04
| 1,255,110,000 |
resolved fixed
|
e9f88a8
| 1,255,110,000 |
tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/workbench/MSashTest.java tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/workbench/RenderingTestCase.java
|
Eclipse_Platform_UI
|
1,700 | 288,770 |
Bug 288770 [statushandling] with multiple errors, top pane get space when resizing (bottom should get all the space)
| null |
2009-09-07 12:48:18
| 1,252,340,000 |
verified fixed
|
7ca7aa2
| 1,255,090,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/statushandlers/WorkbenchStatusDialogManager.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/statushandlers/StatusDialogManagerTest.java
|
Eclipse_Platform_UI
|
1,701 | 290,450 |
Bug 290450 [Forms] TextSegment should call drawText instead of drawString
|
org.eclipse.ui.internal.forms.widgets.TextSegment calls GC.textExtent when measuring strings and drawString to draw them. For consistency, it should call drawText instead of drawString.
|
2009-09-24 15:15:53
| 1,253,820,000 |
resolved fixed
|
191256d
| 1,254,420,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/internal/forms/widgets/TextSegment.java
|
Eclipse_Platform_UI
|
1,702 | 201,650 |
Bug 201650 [Actions] Build Project is disabled when going from problems view to an editor
|
Build ID: I20070625-1500 Steps To Reproduce: 1. Turn off build automatically 2. Build a project with errors or warnings 3. Double click on a problem marker 4. Notice that Build Project is disabled. 5. You can click back and forth between the problems view and the editor and it's still disabled. More information: You have to click on the navigator view or similar to get the action enabled again. The problem is that the selection is calculated incorrectly. When you click on the editor after being on the problems view, the selection is a marker. When you click back on a marker in the problems view, the selection is a text selection. Set a breakpoint in org.eclipse.ui.internal.ide.actions.BuildUtilities.findSelectedProjects(IWorkbenchWindow) to see what I mean. It would appear that the wrong window is being found - see org.eclipse.ui.actions.BuildAction.isEnabled() for how the active window is determined. It certainly doesn't seem right. You could fix this particular issue without changing that logic by having Marker adapter to IResource, but that doesn't seem like the correct approach. I set the severity as major since this is such a common development task - going between the problems view and the editor containing the errors, and building.
|
2007-08-29 16:31:46
| 1,188,420,000 |
verified fixed
|
683d190
| 1,254,410,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WWinPartService.java
|
Eclipse_Platform_UI
|
1,703 | 211,664 |
Bug 211664 [ErrorHandling] ErrorDialog should not display 'Details' button when the children status don't have message
|
Build ID: I20070625-1500 Steps To Reproduce: Currently, ErrorDialog will display the 'Details' button when the status is a MultiStatus or the status has exception. But if it is MultiStatus and all its children status don't have any message, 'Details' button will open a list with nothing in it. It would be nice if ErrorDialog can check if the children status have any message. If not, don't display the 'Details' button. More information:
|
2007-11-30 20:33:51
| 1,196,470,000 |
verified fixed
|
4a62f05
| 1,254,400,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/ErrorDialog.java
|
Eclipse_Platform_UI
|
1,704 | 64,830 |
Bug 64830 [Workbench] Creating OK statuses
| null |
2004-05-31 16:34:32
| 1,086,040,000 |
verified fixed
|
54e8157
| 1,254,390,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorHistory.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorHistoryItem.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorSashContainer.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PartStack.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Perspective.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ViewFactory.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Workbench.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/registry/PerspectiveDescriptor.java
|
Eclipse_Platform_UI
|
1,705 | 290,909 |
Bug 290909 ISizeProvider client contract unclear
|
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) Build Identifier: 3.5.1 The interface ISizeProvider has an @noimplement annotation saying "This interface is not intended to be implemented by clients.". On the other hand the official documentation of IViewPart says: "As of 3.4, views may optionally adapt to {@link ISizeProvider} if they have a preferred size.[..]" Several bugzilla entries (e.g. #104234, #151715, #189939) are referring to this capability as part of a solution, so it seems that this description is either outdated or incorrect. Reproducible: Always
|
2009-09-30 09:45:45
| 1,254,320,000 |
verified fixed
|
498db05
| 1,254,390,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/ISizeProvider.java
|
Eclipse_Platform_UI
|
1,706 | 245,457 |
Bug 245457 [Forms] ExpandableComposite should have option of not drawing the title focus box
| null |
2008-08-27 18:50:36
| 1,219,880,000 |
resolved fixed
|
8e07891
| 1,254,340,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/forms/widgets/ExpandableComposite.java
|
Eclipse_Platform_UI
|
1,707 | 289,599 |
Bug 289599 [Preferences] PreferenceStore.setToDefault fires redundant PropertyChangeEvents
| null |
2009-09-16 09:06:49
| 1,253,110,000 |
verified fixed
|
205b0fc
| 1,254,330,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/preference/PreferenceStore.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/preferences/StringFieldEditorTest.java
|
Eclipse_Platform_UI
|
1,708 | 283,551 |
Bug 283551 [FieldAssist] ContentProposalAdapter Class-JavaDoc and Method-JavaDoc contradict each other
|
The class documentation says: --8<-- This class is not intended to be subclassed. --8<-- But there are methods like openProposalPopup, closeProposalPopup who state something like this: --8<-- This method is used by subclasses to explicitly invoke the opening of the popup. If there are no proposals to show, the popup will not open and a beep will be sounded. --8<-- So did we opened the class since its first release but forgot to update the JavaDoc of the class?
|
2009-07-15 10:13:12
| 1,247,670,000 |
verified fixed
|
0a0bd8b
| 1,254,250,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
1,709 | 174,481 |
Bug 174481 [ViewMgmt] Show View dialog selects wrong entry on Enter
|
I20070213-0907 - Open the Show View dialog and type "plug" - Select and open view "Plug-ins" - Open the Show View dialog again => "Plug-ins" is already selected (good) - type "pl" => depending on how fast you typed, different things happen: a) typed very fast: => "Plug-ins" stays selected (good) - press "Enter" => "Plug-in Dependencies" is selected. It's clearly wrong to select another entry on Enter. b) typed slowly => The folder "PDE" is selected, which does not make sense since they cannot be opened. I would expect that "Plug-ins" stays selected. - press "Enter" => "Plug-in Dependencies" is selected I would prefer if Enter just opened the selected view. Arrow_Down already moves the focus to the tree. The selection in the tree should not depend on typing speed, and it should be predictable. The originally selected view should stay selected as long as it matches the pattern. When the selected view gets removed from the tree, the selection should go to the next best match and stay there
|
2007-02-16 13:37:44
| 1,171,650,000 |
verified fixed
|
8b457ae
| 1,254,250,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/FilteredTree.java
|
Eclipse_Platform_UI
|
1,710 | 249,915 |
Bug 249915 [Dialogs] TitleAreaDialog does not short circuit if message is null
|
M20080911-1700 When profiling use of a custom WizardDialog on Linux/GTK, a lot of time was spent in WizardPage.setMessage(...). It turns out that this was because we were setting a message of null after each keypress, and the page's description (DialogPage.getDescription()) was also null. In this case the short-circuit in TitleAreaDialog.setMessage(String, int) fails to notice that the message has not changed, and does a layout every time. For our dialog this takes about 40ms each time, which is noticeable when compounded with other work.
|
2008-10-07 04:44:16
| 1,223,370,000 |
verified fixed
|
a85bb7b
| 1,254,180,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/TitleAreaDialog.java
|
Eclipse_Platform_UI
|
1,711 | 282,779 |
Bug 282779 [About] Features Dialog - icon is not transparent on white background
|
The icon displayed in the "About ... feature" dialog in the white box at the bottom is not transparent. Instead its background is filled by the platforms button background colour. The text box that displays the about text and the icon should set its background mode to SWT.INHERIT_FORCE
|
2009-07-08 02:37:10
| 1,247,040,000 |
verified fixed
|
2ffd61c
| 1,254,180,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/AboutFeaturesPage.java
|
Eclipse_Platform_UI
|
1,712 | 170,731 |
Bug 170731 [About] Improve layout behavior "About Eclipse SDK Features"
|
Build ID: 200609210005 Steps To Reproduce: 1. click Help -> About Eclipse SDK 2. In the dialog "About Eclipse SDK", click Button "Feature Detail" 3. A Dialog named "About Eclipse SDK Features" is shown 4. Maximize the dialog, the Table doesn't take all the spaces below it. More information: I hope the table take all the spaces when we resize the dialog
|
2007-01-17 03:00:36
| 1,169,020,000 |
verified fixed
|
ba4ba37
| 1,254,180,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/AboutFeaturesPage.java
|
Eclipse_Platform_UI
|
1,713 | 283,120 |
Bug 283120 [About] NPE on Configuration tab in Installation dialog when in a self-hosted Eclipse
|
I20090707-0800 Steps: 1. Run a self-hosted Eclipse 2. Go to Help > About > Installation Details, note that most of the tabs are empty as the running profile cannot be determined 3. Switch to the last tab (Configuration) => java.lang.NullPointerException at org.eclipse.ui.internal.ide.dialogs.ConfigurationLogUpdateSection.writeInstalledIUs(ConfigurationLogUpdateSection.java:61) at org.eclipse.ui.internal.ide.dialogs.ConfigurationLogUpdateSection.write(ConfigurationLogUpdateSection.java:127) at org.eclipse.ui.internal.ConfigurationInfo.appendExtensions(ConfigurationInfo.java:107) at org.eclipse.ui.internal.ConfigurationInfo.getSystemSummary(ConfigurationInfo.java:73) at org.eclipse.ui.internal.about.AboutSystemPage$1.run(AboutSystemPage.java:67) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.about.AboutSystemPage.createControl(AboutSystemPage.java:65) at org.eclipse.ui.internal.about.InstallationDialog.tabSelected(InstallationDialog.java:271) at org.eclipse.ui.internal.about.InstallationDialog.access$1(InstallationDialog.java:262) at org.eclipse.ui.internal.about.InstallationDialog$2.widgetSelected(InstallationDialog.java:254) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.AboutDialog$1.run(AboutDialog.java:127) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.dialogs.AboutDialog.buttonPressed(AboutDialog.java:122) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.about.AboutHandler.execute(AboutHandler.java:32) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
|
2009-07-10 05:15:49
| 1,247,220,000 |
verified fixed
|
104e5d0
| 1,253,820,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ConfigurationLogUpdateSection.java
|
Eclipse_Platform_UI
|
1,714 | 283,555 |
Bug 283555 [Markers] Configure Contents dialog: Types section should not have columns
| null |
2009-07-15 10:18:55
| 1,247,670,000 |
resolved fixed
|
f48bc4d
| 1,253,800,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/TypesConfigurationArea.java
|
Eclipse_Platform_UI
|
1,715 | 66,889 |
Bug 66889 [ViewMgmt] Package explorer message clipped
|
3.0 RC2 1) set the package explorer to "hierarchical" mode. 2) "go into" org.eclipse.jdt.internal.core 3) observe: the package explorer shows the name of it's input in the title bar. 4) make the package explorer progressively narrower 5) observe: the package name shown in the title bar gets clipped without any indication that it is clipped. I was mislead into thinking that I was in a different context.
|
2004-06-14 05:17:11
| 1,087,200,000 |
verified fixed
|
cbd0ab2
| 1,253,740,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/presentations/PaneFolder.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/presentations/defaultpresentation/DefaultTabFolder.java
|
Eclipse_Platform_UI
|
1,716 | 266,545 |
Bug 266545 [About] Content of the configuration tab should be populated in the background
|
The computation of the content for the configuration details is very slow and should be done in teh background to allow for the UI to come up quickly
|
2009-02-27 14:42:56
| 1,235,760,000 |
verified fixed
|
8461209
| 1,253,730,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchMessages.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/AboutSystemPage.java
|
Eclipse_Platform_UI
|
1,717 | 286,542 |
Bug 286542 Unnecessary line of code in ResourceEncodingFieldEditor
|
Around line 268 String defaultCharset = getCharsetFromDescription(); defaultCharset = getCharsetFromDescription();
|
2009-08-13 12:11:13
| 1,250,180,000 |
resolved fixed
|
980aeda
| 1,253,700,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/dialogs/ResourceEncodingFieldEditor.java
|
Eclipse_Platform_UI
|
1,718 | 279,263 |
Bug 279263 [Compatibility] Consider addition of legacy view / editor containers
|
While working on the debug view, it became apparent that this view expects to have an intermediary Composite container between itself and the CTabItem. In this particular case absence of the intermediary causes loss of the initial layout message. One possible "real" solution to this is to create such an intermediary container for legacy views. (For instance, in the LegacyViewFactory.) Generalizing this, chances are that E4 will need to do some special processing for "legacy" views and editors: generate extra notifications, alter context information, and so on. Having an "official" container around legacy parts will provide a logical place for all that special code.
|
2009-06-05 10:21:32
| 1,244,210,000 |
resolved fixed
|
cb022c5
| 1,253,130,000 |
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/PerspectiveRenderer.java
|
Eclipse_Platform_UI
|
1,719 | 289,090 |
Bug 289090 [CommonNavigator] labels are missing
| null |
2009-09-10 11:42:45
| 1,252,600,000 |
verified fixed
|
a045bf9
| 1,252,740,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentServiceLabelProvider.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/LabelProviderTest.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProvider.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderBlank.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderBlue.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderCyan.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderGreen.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderPlainGreen.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderPlainRed.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderRed.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderStyledGreen.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderStyledRed.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestStyledLabelProvider.java
|
Eclipse_Platform_UI
|
1,720 | 287,103 |
Bug 287103 [CommonNavigator] contentServiceLabelProvider doesn't properly implement overrides
| null |
2009-08-19 13:24:29
| 1,250,700,000 |
verified fixed
|
8c251a3
| 1,252,740,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/ContributorTrackingSet.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentService.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentServiceContentProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentServiceLabelProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/Policy.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorContentDescriptor.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorContentDescriptorManager.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/LabelProviderTest.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/NavigatorTestBase.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/NavigatorTestSuite.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/PipelineTest.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/SorterTest.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestContentProviderPipelined.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProvider.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderBlank.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderBlue.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderCyan.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderGreen.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestLabelProviderRed.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TrackingLabelProvider.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/jst/CompressedJavaLibraries.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/jst/CompressedJavaProject.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/jst/ICompressedNode.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/jst/JstPipelineTest.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/jst/WebJavaContentProvider.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/jst/WebJavaLabelProvider.java
|
Eclipse_Platform_UI
|
1,721 | 271,501 |
Bug 271501 [CSS] CSSSWTApplyStylesListener - does it need to shell.pack()
| null |
2009-04-07 14:02:18
| 1,239,130,000 |
resolved fixed
|
4e4250b
| 1,252,700,000 |
bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/engine/CSSSWTApplyStylesListener.java
|
Eclipse_Platform_UI
|
1,722 | 279,939 |
Bug 279939 [CSS] Remove CSSSWTLazyHandlerEngineImpl and packages
|
There are no references to CSSSWTLazyHandlerEngineImpl, we don't ever instantiate the CSSSWTLazyHandlerEngineImpl, either in our examples or tests. Do we still need/want it? It brings with it the following packages which presumably would also be deleted: .registerPackage("org.eclipse.e4.ui.css.swt.properties.css2.lazy.classification"); .registerPackage("org.eclipse.e4.ui.css.swt.properties.css2.lazy.border"); .registerPackage("org.eclipse.e4.ui.css.swt.properties.css2.lazy.font"); .registerPackage("org.eclipse.e4.ui.css.swt.properties.css2.lazy.background"); .registerPackage("org.eclipse.e4.ui.css.swt.properties.css2.lazy.text");
|
2009-06-11 09:52:39
| 1,244,730,000 |
resolved fixed
|
3627de2
| 1,252,690,000 |
bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/background/CSSPropertyBackgroundColorHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/background/CSSPropertyBackgroundHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/background/CSSPropertyBackgroundImageHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/border/AbstractCSSPropertyBorderSWTHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/border/CSSPropertyBorderColorHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/border/CSSPropertyBorderHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/border/CSSPropertyBorderSWTHandler2.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/border/CSSPropertyBorderStyleHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/border/CSSPropertyBorderWidthHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/classification/CSSPropertyCursorHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/font/AbstractCSSPropertyFontSWTHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/font/CSSPropertyFontFamilyHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/font/CSSPropertyFontHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/font/CSSPropertyFontSWTHandler2.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/font/CSSPropertyFontSizeHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/font/CSSPropertyFontStyleHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/font/CSSPropertyFontWeightHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/text/CSSPropertyColorHandler.java
|
Eclipse_Platform_UI
|
1,723 | 86,248 |
Bug 86248 [Commands] request: ctrl+pageup/down action doesn't have item in preferences/keys
|
hi, in 3.0.1 the behaviour of ctrl+pageup/down is much better and quickier inc comparison to ctrl/shift/+f6 i want the same behaviour as ctrl+pageup triggers to be mapped on F1/F2 as some extension to firefox does it, but it is not possible to remap it, cos there is no such item in preferences/keys anywhere (i did go through all of them watchig for ctrl+pageup -> no success :( )
|
2005-02-23 06:56:44
| 1,109,160,000 |
verified fixed
|
72c90d1
| 1,252,440,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/handlers/TraversePageHandler.java
|
Eclipse_Platform_UI
|
1,724 | 275,018 |
Bug 275018 [Markers] Problems View / Configure Contents dialog should support rename
| null |
2009-05-05 12:26:41
| 1,241,540,000 |
resolved fixed
|
5b14a8a
| 1,252,440,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/FiltersConfigurationDialog.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerMessages.java
|
Eclipse_Platform_UI
|
1,725 | 231,619 |
Bug 231619 [PropertiesDialog] Open up the API for org.eclipse.ui.internal.dialogs.PropertyDialog
|
This request is to open up the API of org.eclipse.ui.internal.dialogs.PropertyDialog. I need to perform some custom validations prior to displaying the properties dialog. I'm using actions and can subclass org.eclipse.ui.dialogs.PropertyDialogAction to perform the validations. I'm converting to commands and handlers, however, the handler equivalent of the action, PropertyDialogHandler, is in an internal package. Instead of making it public, it would be more flexible to make the PropertyDialog public. If the dialog were public it could be invoked from a custom handler (or action). By being public, the dialog would also allow callers to provide a custom initial page id or a custom element.
|
2008-05-12 14:05:18
| 1,210,620,000 |
verified fixed
|
71e20e7
| 1,252,010,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/PreferencesUtil.java
|
Eclipse_Platform_UI
|
1,726 | 288,154 |
Bug 288154 [perfs] Comments applied for performance tests may be obsolete
| null |
2009-08-31 12:39:56
| 1,251,740,000 |
verified fixed
|
67e92cf
| 1,251,990,000 |
tests/org.eclipse.ui.tests.performance/src/org/eclipse/jface/tests/performance/CollatorPerformanceTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/jface/tests/performance/ComboViewerRefreshTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/jface/tests/performance/ListViewerRefreshTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/jface/tests/performance/TreeAddTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/ObjectContributionsPerformance.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/OpenCloseWindowTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/OpenMultipleEditorTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/PerspectiveSwitchTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/layout/LayoutTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/presentations/PresentationActivePartPropertyTest.java
|
Eclipse_Platform_UI
|
1,727 | 89,606 |
Bug 89606 [Viewers] Remove protected API added to support prototype of grouping by working sets
| null |
2005-03-30 12:06:20
| 1,112,200,000 |
resolved wontfix
|
a4f1441
| 1,251,920,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractTreeViewer.java
|
Eclipse_Platform_UI
|
1,728 | 288,394 |
Bug 288394 [MPE] MultiPageEditorSite does not remove properly its KeyBindingService
| null |
2009-09-02 13:55:28
| 1,251,910,000 |
verified fixed
|
d41b972
| 1,251,910,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/part/MultiPageEditorSite.java
|
Eclipse_Platform_UI
|
1,729 | 288,388 |
Bug 288388 [ActivityMgmt] WorkbenchActivityHelper restrictArray is returning NULL for objects failing the test "restrictUseOf(Object)"
| null |
2009-09-02 13:35:58
| 1,251,910,000 |
verified fixed
|
715ba24
| 1,251,910,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/activities/WorkbenchActivityHelper.java
|
Eclipse_Platform_UI
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.