id
int64 1
6.5k
| bug_id
int64 2.03k
426k
| summary
stringlengths 9
251
| description
stringlengths 1
32.8k
⌀ | report_time
stringlengths 19
19
| report_timestamp
int64 1B
1.39B
| status
stringclasses 6
values | commit
stringlengths 7
9
| commit_timestamp
int64 1B
1.39B
| files
stringlengths 25
32.8k
| project_name
stringclasses 6
values |
|---|---|---|---|---|---|---|---|---|---|---|
3,730
| 104,839
|
Bug 104839 [Forms] TableWrapLayout requires too much vertical space with wrapped label in WizardPage
|
My understanding is that the whole purpose of the TableWrapLayout is to deal with wrapped labels. But this example shows that the layout requests a height much greater than is required. I recently tested this in 3.1 - and it happened in 3.0 and 3.0.1, IIRC. Run the example and a Wizard will appear...which on my system takes up the entire height of the screen. Dismiss the Wizard and the 2nd example will appear: adding a textfield fixes the problem. But not really...as you can see in the 3rd example - multiple wrapped labels still force the wizard taller than it needs to be. Example code: package test; import org.eclipse.jface.wizard.*; import org.eclipse.swt.widgets.*; import org.eclipse.swt.*; import org.eclipse.ui.forms.widgets.*; /** */ public class MyWizardPage extends WizardPage { public MyWizardPage(int variation) { super("intro"); setTitle("title"); setDescription("description"); _variation = variation; } public void createControl(Composite parent) { toolkit = new FormToolkit(parent.getDisplay()); // toolkit.setBackground(parent.getBackground()); form = toolkit.createForm(parent); form.setText("prompt"); setControl(form); Composite body = form.getBody(); TableWrapLayout layout = new TableWrapLayout(); layout.numColumns = 2; layout.verticalSpacing = 10; layout.topMargin = 10; layout.bottomMargin = 10; layout.leftMargin = 10; layout.rightMargin = 10; body.setLayout(layout); Label label1 = toolkit.createLabel(body, "Here is a long line. It is pretty long. Well, long enough to wrap in the wizard, anyway. It goes on and on an on for no particular purpose, really. It just keeps going. Kinda like that bunny in those battery commercials.", SWT.WRAP); label1.setLayoutData(new TableWrapData(TableWrapData.FILL, TableWrapData.CENTER, 1, 2)); if (_variation == 3) { Label label2 = toolkit.createLabel(body, "Here is a long line. It is pretty long. Well, long enough to wrap in the wizard, anyway. It goes on and on an on for no particular purpose, really. It just keeps going. Kinda like that bunny in those battery commercials.", SWT.WRAP); label2.setLayoutData(new TableWrapData(TableWrapData.FILL, TableWrapData.CENTER, 1, 2)); Label label3 = toolkit.createLabel(body, "Here is a long line. It is pretty long. Well, long enough to wrap in the wizard, anyway. It goes on and on an on for no particular purpose, really. It just keeps going. Kinda like that bunny in those battery commercials.", SWT.WRAP); label3.setLayoutData(new TableWrapData(TableWrapData.FILL, TableWrapData.CENTER, 1, 2)); } if (_variation > 1) { Text _url_field = toolkit.createText(body, "Adding this text field fixed the problem! Why?", SWT.BORDER); _url_field.setLayoutData(new TableWrapData(TableWrapData.FILL_GRAB)); } } public static void main(String[] args) { Display display = new Display(); Shell shell = new Shell(display); shell.setText("testing..."); shell.pack(); shell.open(); createWizard(shell, 1); createWizard(shell, 2); createWizard(shell, 3); } private static void createWizard(Shell shell, int variation) { Wizard wizard = new Wizard() { public boolean performFinish() { return true; //To change body of implemented methods use File | Settings | File Templates. } }; wizard.addPage(new MyWizardPage(variation)); WizardDialog dialog = new WizardDialog(shell, wizard); dialog.open(); } public void dispose() { super.dispose(); toolkit.dispose(); } private FormToolkit toolkit; private Form form; int _variation; }
|
2005-07-22 13:15:17
| 1,122,050,000
|
resolved fixed
|
7ae291a
| 1,153,750,000
|
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/forms/widgets/TableWrapLayout.java
|
Eclipse_Platform_UI
|
3,731
| 150,609
|
Bug 150609 [Properties dialog][EFS] File properties for custom filesystem not shown
|
While implementing a custom filesystem, we came across the following problem: the properties 'last modified', 'location' and 'size' receive the value '<resource does not exist>'. The problem is due to the use of IResource#getLocation() in ResourcePropertySource and FilePropertySource which returns null in case of resources that are not stored on the default local filesystem. IResource#getLocationURI() should be used instead. In fact, this already happens in IDEResourceInfoUtils, which contains static versions of the same property retrieval methods implemented in ResourcePropertySource and FilePropertySource.
|
2006-07-14 03:37:03
| 1,152,860,000
|
verified fixed
|
856d729
| 1,153,520,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/properties/FilePropertySource.java
|
Eclipse_Platform_UI
|
3,732
| 151,442
|
Bug 151442 Javadoc error in ResourceAndContainerGroup.getResource()
|
/** * Returns a string that is the path of the currently selected * container. Returns an empty string if no container has been * selected. */ public String getResource() { return resourceNameField.getText(); } I don't believe "...currently selected 'container'..." is what is meant for this method, as 'container' is refers to the container field of this group, not the resource file name that this method is associated with.
|
2006-07-21 13:50:54
| 1,153,500,000
|
resolved fixed
|
88168a9
| 1,153,510,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/ResourceAndContainerGroup.java
|
Eclipse_Platform_UI
|
3,733
| 151,089
|
Bug 151089 [EFS] Closed projects on remote filesystem cause unwanted connection attempts
|
When a project is located on a remote filesystem (e.g. a WebDAV server) and this project is closed when starting Eclipse, Eclipse will cause cconnection attempts to that remote system. This is especially undesirable if those projects were closed because the remote system was shut down in the first place. The following is a stacktrace of Eclipse's first attempt to reach a remote system at startup, followed by some clarification. 8 WebDAVFileSystem.getStore(URI) line: 49 7 InternalFileSystemCore.getStore(URI) line: 107 6 EFS.getStore(URI) line: 296 5 FileStoreRoot.toLocalPath(URI) line: 120 4 FileStoreRoot.<init>(URI, IPath) line: 57 3 FileSystemResourceManager.setLocation(IResource, ResourceInfo, URI) line: 806 2 Project.internalSetDescription(IProjectDescription, boolean) line: 663 1 SaveManager.restoreMetaInfo(Project, IProgressMonitor) line: 782 SaveManager.restoreMetaInfo(MultiStatus, IProgressMonitor) line: 746 SaveManager.restore(IProgressMonitor) line: 637 SaveManager.startup(IProgressMonitor) line: 1299 Workspace.startup(IProgressMonitor) line: 1883 Workspace.open(IProgressMonitor) line: 1653 ResourcesPlugin.startup() line: 367 ... 1 SaveManager.restoreMetaInfo(Project, IProgressMonitor) line: 782 A project description is tried to be read; if the project is closed, it cannot be read and a dummy IProjectDescription is created. This description is then set with an internal method (the API method setDescription can only be used on existing open projects). 2 Project.internalSetDescription(IProjectDescription, boolean) line: 663 For some reason Eclipse interprets a closed project as being a resource that has its location changed and so it is set again (to a WebDAV location: webdav://). 3 FileSystemResourceManager.setLocation(IResource, ResourceInfo, URI) line: 806 To set the location, a new FileStoreRoot is created with root URI the URI of the remote project location (webdav://). 4 FileStoreRoot.<init>(URI, IPath) line: 57 The FileStoreRoot constructor tries to find out the local file that corresponds with the given WebDAV URI. If this is not possible, null will be stored (eventually this will happen, but only after the nonreachable remote system has been tried to be contacted). 5 FileStoreRoot.toLocalPath(URI) line: 120 The filesystem corresponding to the URI scheme (webdav) is requested with EFS. 6 EFS.getStore(URI) line: 296 An IFileStore is requested for the given WebDAV URI. 7 InternalFileSystemCore.getStore(URI) line: 107 The IFileSystem corresponding with the scheme of the given URI (webdav) is retrieved (WebDAVFileSystem). This filesystem is asked for an IFileStore representing the given URI. 8 WebDAVFileSystem.getStore(URI) line: 49 An attempt is made to create a WebDAVFileStore that represents the given URI. If it is not possible to create a file store corresponding to the provided URI, a file store belonging to the null file system should be returned. However, in order to know whether it is possible to create a file store, the WebDAV server should be contacted to determine if it responds. In my opinion, step 3 is the strangest: why must a closed project have its location set?
|
2006-07-19 11:07:25
| 1,153,320,000
|
resolved fixed
|
5690ece
| 1,153,430,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/IDEResourceInfoUtils.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/properties/ResourcePropertySource.java
|
Eclipse_Platform_UI
|
3,734
| 24,928
|
Bug 24928 [JFace] Need ComboFieldEditor
|
Build 20021016 There seems to be a need for a combo box field editor: there are 3 copies in the system and I have to introduce another one.
|
2002-10-17 07:37:35
| 1,034,850,000
|
resolved fixed
|
50195da
| 1,152,290,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/preference/ComboFieldEditor.java
|
Eclipse_Platform_UI
|
3,735
| 149,857
|
Bug 149857 [Progress] Calling isCanceled after job is done causes Progress View entry to stick around
| null |
2006-07-06 12:59:27
| 1,152,210,000
|
resolved fixed
|
161e36b
| 1,152,280,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressManager.java
|
Eclipse_Platform_UI
|
3,736
| 39,003
|
Bug 39003 [JFace] Window exception handler
|
Hi all, The org.eclipse.jface.window.Window class contains the following sequence of code: public static void setExceptionHandler(IExceptionHandler handler) { if(exceptionHandler instanceof DefaultExceptionHandler) exceptionHandler = handler; } The instanceof check actually prevents setting a custom exception handler. The DefaultExceptionHandler class is made private and cannot be extended to hack around of this code. The DefaultExceptionHandler handles exceptions by printing stacktrace to the standard output. This problem effectively prevents the use of jface Window and it's subclass ApplicationWindow classes in any non trivial application. Regards, Peter.
|
2003-06-17 05:23:10
| 1,055,840,000
|
resolved wontfix
|
dd0b92a
| 1,152,210,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/window/Window.java
|
Eclipse_Platform_UI
|
3,737
| 144,974
|
Bug 144974 [Preferences] TVT3.2:TCT829: DE : Base : Truncation in Ant Preferences Panel
|
OS : RHEL 3.1 Must fix or not a must fix: NO Build date: 0531 Component name = Base Blocking: no Language: de Bitmap Location: V:\defects\de\ Tester Name: Ruth Nestvold Problem Description: The "Browse..." button is truncated on the Prefences panel Steps: On the menu bar from the main Workbench panel, click Windows > Preference Expand and Select Ant The Browse button on the Ant panel is truncated This article was reassigned from Category:''TVT/Testing''.
|
2006-06-01 16:23:21
| 1,149,190,000
|
verified fixed
|
ccfa699
| 1,152,200,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/preference/StringButtonFieldEditor.java
|
Eclipse_Platform_UI
|
3,738
| 116,614
|
Bug 116614 [CellEditors] Mixing up between undo and redo in CellEditorActionHandler
| null |
2005-11-16 02:26:29
| 1,132,130,000
|
verified fixed
|
e9c2dd3
| 1,152,200,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/part/CellEditorActionHandler.java
|
Eclipse_Platform_UI
|
3,739
| 149,663
|
Bug 149663 [PropertyPages] CCE when closing Properties dialog for Java project
|
I20060704-0800 - select a Java project in the Package Explorer - choose File > Properties - press OK Changes on other properties pages are also not saved because of this exception. java.lang.ClassCastException: org.eclipse.jdt.internal.core.JavaProject at org.eclipse.ui.internal.ide.dialogs.ResourceInfoPage.performOk(ResourceInfoPage.java:537) at org.eclipse.jface.preference.PreferenceDialog$11.run(PreferenceDialog.java:889) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:869) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:377) at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:230) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3375) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2995) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:156) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3375) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2995) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-07-05 09:06:44
| 1,152,100,000
|
verified fixed
|
6abfa24
| 1,152,120,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceInfoPage.java
|
Eclipse_Platform_UI
|
3,740
| 149,311
|
Bug 149311 [WorkingSets] working set selection wizard page has faulty layout
|
The layout for the Working set type: label of the New/Edit WorkingSetTypePage wizard page is not correct. If you select a type, then go back, you will see the label's layout is grabbing excess vertical space when it shouldn't be. I have a patch to fix this.
|
2006-06-30 10:52:34
| 1,151,680,000
|
verified fixed
|
1e4d2fa
| 1,151,680,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/WorkingSetTypePage.java
|
Eclipse_Platform_UI
|
3,741
| 50,994
|
Bug 50994 [Wizards] NewWizardShortcutAction does not properly size wizard
|
We are using org.eclipse.ui.actions.NewWizardMenu() to create the New> menu option on a popup menu inside a tree view. The wizards registered for the perspective are coming up with odd, outlandish sizes. We traced the problem to org.eclipse.ui.internal.ide.NewWizardShortcutAction. When NewWizardShortcutAction creates the WizardDialog, it does not properly size the wizard. The problem does not show up from the general NewWizardDialog (where an individual wizard is selected from all available) because NewWizardAction handles the sizing of the initial WizardDialog, and the subsequent WizardPages added absorb the correct size. This is a simple fix, which could be accomplished with the following (minor) change: _Currently in NewWizardAction.java#159-64_ Shell parent = workbenchWindow.getShell(); WizardDialog dialog = new WizardDialog(parent, wizard); dialog.create(); // the following is the key line missing from NewWizardShortcutAction dialog.getShell().setSize( Math.max(SIZING_WIZARD_WIDTH, dialog.getShell().getSize().x), SIZING_WIZARD_HEIGHT); WorkbenchHelp.setHelp(dialog.getShell(), IHelpContextIds.NEW_WIZARD); dialog.open(); _Add the same line to NewWizardShortcutAction.java#92-98_ wizard.init(window.getWorkbench(), selectionToPass); Shell parent = window.getShell(); WizardDialog dialog = new WizardDialog(parent, wizard); dialog.create(); dialog.getShell().setSize( Math.max(SIZING_WIZARD_WIDTH, dialog.getShell().getSize().x), SIZING_WIZARD_HEIGHT); WorkbenchHelp.setHelp(dialog.getShell(), IHelpContextIds.NEW_WIZARD_SHORTCUT); dialog.open(); We have not tested the above modification. [Using Eclipse 3.0M6 on Windows 2000]
|
2004-01-30 15:28:34
| 1,075,490,000
|
verified fixed
|
21a9146
| 1,151,600,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/actions/NewWizardShortcutAction.java
|
Eclipse_Platform_UI
|
3,742
| 147,848
|
Bug 147848 [Dialogs] Context Menu > Copy in ErrorDialog ignores details
| null |
2006-06-20 06:39:07
| 1,150,800,000
|
verified fixed
|
be3b2f0
| 1,151,600,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/ErrorDialog.java
|
Eclipse_Platform_UI
|
3,743
| 120,704
|
Bug 120704 [Wizards] Problems with the "New" wizard
|
1. there is a small red square in the top right 2. the filter does not line up on the right with the viewer and looks bad. 3. the viewer is small vertically, and yet there is a lot of real estate that is being ununsed on the bottom. 4. why is there a help icon on the bottom right, and why is it never enabled? screenshot to follow
|
2005-12-13 15:14:45
| 1,134,500,000
|
verified fixed
|
e7a8c0b
| 1,151,530,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/NewWizardNewPage.java
|
Eclipse_Platform_UI
|
3,744
| 143,757
|
Bug 143757 [Import/Export] Cannot Import existing project into workspace if <name> different from actual folder name
|
Hi, I am not sure where this belongs Core/ UI or Debug; however discovered this today, In eclipse I can "Import exiting projects into Workspace", *IF and only IF* the <name></name> in the .project file matches the name of the folder in which it exists. To confirm; I created a Java project in my workspace, by name HelloWorld. Subsquently deleted it from workspace, WITHOUT deleting contents from the file system. Next in the file system, edited ONLY the ".project" file of this project. I changed <name>HellWorld</name> into <name>Not-HelloWorld</name> Returning back to eclipse, tried the command File -> Import -> Import exiting projects into Workspace Specified the folder for the HelloWorld. The Projects list box in the dialog listed Not-HelloWorld. (read the .project file). I selected it and clicked finnish. An error dialog popped up, saying Invalid project description. Detail showed D:\Users\Jeevan\workspace\HelloWorld overlaps the workspace location: D:\Users\Jeevan\workspace. I reedited the .project file manually and restored the <name></name> following which I was able to import it into my workspace. This happens with: Eclipse SDK Version: 3.1.2 Build id: M20060118-1600 But does NOT with a older version. Eclipse SDK Version: 3.1.0 Build id: I20050627-1435
|
2006-05-25 12:18:30
| 1,148,570,000
|
verified fixed
|
97e4630
| 1,151,520,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/wizards/datatransfer/WizardProjectsImportPage.java
|
Eclipse_Platform_UI
|
3,745
| 148,674
|
Bug 148674 [PropertyPages] Property pages extension point should also deprecate adaptable
|
3.2 We deprecated the propertyPages extension point attribute objectClass in favour of enabledWhen. We should also deprecate the adaptable flag as it is used with objectClass.
|
2006-06-26 12:34:53
| 1,151,340,000
|
verified fixed
|
1d3429f
| 1,151,520,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ResourceInfoPage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/PropertyPageContributorManager.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/registry/PropertyPagesRegistryReader.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/dynamicplugins/DynamicTestType.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/dynamicplugins/PropertyPageTests.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/preferences/PreferencesTestSuite.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertyPages/PropertyPageEnablementTest.java
|
Eclipse_Platform_UI
|
3,746
| 145,035
|
Bug 145035 [IDE] ESC does not work as expected on renaming a resource
|
When I m in the team synchronizing perspective I press F2 to rename a resource. A dialog pops up and when I press cancel everything is fine. But when I press ESC (or use the "X" button") I m asked if I want to overwrite the existing resource.
|
2006-06-02 06:22:51
| 1,149,240,000
|
resolved fixed
|
1d9ef8d
| 1,151,350,000
|
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/actions/RenameResourceAction.java
|
Eclipse_Platform_UI
|
3,747
| 148,551
|
Bug 148551 [Import/Export] Import File System Problem
|
When going to import some files if you choose General, then Filesystem. As you browse to the folder where you want to import items from and select it, the option to "Select All" is not available until you either select the folder or a file in the folder.
|
2006-06-24 21:44:58
| 1,151,200,000
|
verified fixed
|
7553678
| 1,151,340,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/wizards/datatransfer/WizardFileSystemResourceImportPage1.java
|
Eclipse_Platform_UI
|
3,748
| 24,143
|
Bug 24143 [DND] Incorrect javadoc for NavigatorDragAdapter
|
Build 20020924 The javadoc that is generated for NavigatorDragAdapter (look in reference section of online help), looks like this: void dragFinished(DragSourceEvent event) This implementation of dragFinished does nothing. void dragSetData(DragSourceEvent event) This implementation of dragSetData does nothing. void dragStart(DragSourceEvent event) This implementation of dragStart permits the drag operation to This javadoc is incorrect. It has been copied from the generic superclass DragSourceAdapter. I guess we need to override the javadoc for API classes in cases where the implementation differs significantly from the superclass. There are probably many more examples of this throughout the UI.
|
2002-09-26 10:54:02
| 1,033,050,000
|
verified fixed
|
1ee6d1f
| 1,151,090,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/navigator/NavigatorDragAdapter.java
|
Eclipse_Platform_UI
|
3,749
| 88,325
|
Bug 88325 [Progress] IProgressService document enhancements
|
The topmost comment on the IProgressService is speaking about IProgressManager and looks like a typo. it should say IProgressService Through testing the method of the IProgressService; busyCursorWhile run(boolean,boolean,IRunnableWithProgress) If the IProgressService is returned by IWorkbench, must both be called from the UI thread. I wonder if this means all thread running methods of the IProgressService returned by IWorkbench must be called from the UI thread. If so it would be nice if the workbench specified that on its getProgressService() method.
|
2005-03-17 09:17:25
| 1,111,070,000
|
verified fixed
|
e5d7e39
| 1,151,080,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/progress/IProgressService.java
|
Eclipse_Platform_UI
|
3,750
| 145,378
|
Bug 145378 [Coolbar]RCP appication loses Icons/actions with IDE Stable Builds RC6 and RC7
|
When launching an RCP application from PDE icons/actions are lost. RC6 loses a general action from the toolbar even thou' it appears in the main menu. The action is added to the toolbar from the plugin manifest and is hooked in as follows using the ToolBarContributionItem. protected void fillCoolBar(ICoolBarManager cbManager) { cbManager.add(new GroupMarker("group.file")); { // File Group IToolBarManager fileToolBar = new ToolBarManager(cbManager.getStyle()); fileToolBar.add(new Separator(IWorkbenchActionConstants.NEW_GROUP)); fileToolBar.add(new GroupMarker(IWorkbenchActionConstants.OPEN_EXT)); fileToolBar.add(new Separator(IWorkbenchActionConstants.MB_ADDITIONS)); cbManager.add(new ToolBarContributionItem(fileToolBar,IWorkbenchActionConstants.TOOLBAR_FILE)); } cbManager.add(new GroupMarker(IWorkbenchActionConstants.MB_ADDITIONS)); cbManager.add(new GroupMarker(IWorkbenchActionConstants.GROUP_EDITOR)); } RC7 loses the above as well as the "run garbage collection" icon on the bottom right of the workbench window. The two mentioned problems work correctly in the Eclipse 3.1.2 final release.
|
2006-06-05 12:54:08
| 1,149,530,000
|
verified fixed
|
8a290f9
| 1,151,070,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/action/ToolBarContributionItem.java
|
Eclipse_Platform_UI
|
3,751
| 147,846
|
Bug 147846 [OLE] OLE Error using Open With > In-Place Editor
|
3.2 RC7 and latest 3.3 I-build (I20060614-0843) 1. select any file (text, html, java, ...) in the Navigator 2. Open With > In-Place Editor ==> error dialog appears, nothing in .log. Empty editor gets opened.
|
2006-06-20 06:26:04
| 1,150,800,000
|
verified fixed
|
915e091
| 1,150,910,000
|
bundles/org.eclipse.ui.win32/src/org/eclipse/ui/internal/editorsupport/win32/OleEditor.java
|
Eclipse_Platform_UI
|
3,752
| 142,785
|
Bug 142785 NavigatorSaveablesServices NPEs on shutdown
|
On Build id: I20060505-1306: The following exception was encountered on shutdown, and encountered multiple times (about 20). I'm not sure I have a scenario that can reproduce this, but there were many more Navigator extensions than base platform (roughly 20). I think by the time this was reached, the Project Explorer had been disposed. !ENTRY org.eclipse.osgi 4 0 2006-05-19 11:21:38.993 !MESSAGE An unexpected runtime error has occurred. !STACK 0 java.lang.NullPointerException at org.eclipse.ui.internal.navigator.NavigatorSaveablesService.computeSaveables(NavigatorSaveablesService.java:216) at org.eclipse.ui.internal.navigator.NavigatorSaveablesService.recomputeSaveablesAndNotify(NavigatorSaveablesService.java:374) at org.eclipse.ui.internal.navigator.NavigatorSaveablesService.handleBundleStopped(NavigatorSaveablesService.java:457) at org.eclipse.ui.internal.navigator.NavigatorSaveablesService.bundleChanged(NavigatorSaveablesService.java:100) at org.eclipse.ui.internal.navigator.NavigatorPlugin$1.bundleChanged(NavigatorPlugin.java:35) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:1206) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:189) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:291) 11
|
2006-05-19 11:29:10
| 1,148,050,000
|
verified fixed
|
092b316
| 1,150,830,000
|
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/CommonViewer.java
|
Eclipse_Platform_UI
|
3,753
| 92,738
|
Bug 92738 [Progress] progress view flashes even when no visible update occurs
| null |
2005-04-26 04:19:32
| 1,114,500,000
|
verified fixed
|
8da017b
| 1,150,810,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/DetailedProgressViewer.java
|
Eclipse_Platform_UI
|
3,754
| 147,737
|
Bug 147737 [Wizards] Delete dead multi step wizard code
| null |
2006-06-19 11:31:17
| 1,150,730,000
|
verified fixed
|
302948d
| 1,150,750,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/CreateProjectStep.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/CreateProjectWizard.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/MultiStepConfigureWizardPage.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/MultiStepReviewWizardPage.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/MultiStepWizard.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/MultiStepWizardDialog.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/NewProjectWizard.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/WizardNewProjectNameAndLocationPage.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/WizardStep.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/WizardStepGroup.java
|
Eclipse_Platform_UI
|
3,755
| 144,556
|
Bug 144556 [Dialogs] TitleAreaDialog fails to properly recreate when an instance is reopened
|
When a TitleAreaDialog is created, opened, closed and opened again on the same instance the messageArea is not properly checked against disposal when it is accessed in setWarningMessage throwing an SWTException for disposed when the message area is updated the second time the dialog is opened.
|
2006-05-30 17:22:57
| 1,149,020,000
|
verified fixed
|
7012167
| 1,150,740,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/TitleAreaDialog.java
|
Eclipse_Platform_UI
|
3,756
| 137,946
|
Bug 137946 [Preferences] Mock 3.2 - Truncated strings in Preference - keys dialog
|
Instructions to recreate the bugs Go to Windows > Preferences. Expand General. Select Keys. "Edit" and "Export" strings are truncated.
|
2006-04-21 10:31:58
| 1,145,630,000
|
verified fixed
|
659087b
| 1,150,730,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/KeysPreferencePage.java
|
Eclipse_Platform_UI
|
3,757
| 147,727
|
Bug 147727 UI incorrectly prevents overlapping project locations on disk
| null |
2006-06-19 10:39:17
| 1,150,730,000
|
verified fixed
|
46c7552
| 1,150,730,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchMessages.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/ProjectContentsLocationArea.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/WizardNewProjectNameAndLocationPage.java
|
Eclipse_Platform_UI
|
3,758
| 135,559
|
Bug 135559 [Markers] Problem view sections collapse after manual build
|
3.2 M6 The sections in the problem view collapse after a manual build For example: - set autobuild off - expand the errors section in the problem view - click on a problem - fix the problem - build - notice that the "error" section is now collapsed.
|
2006-04-07 10:51:06
| 1,144,420,000
|
verified fixed
|
d584568
| 1,150,730,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerView.java
|
Eclipse_Platform_UI
|
3,759
| 135,316
|
Bug 135316 [DataBinding] Unexpected behavior from BindSpec converter and validator setters
|
The set methods that accept one validator/converter don't behave as expected. For example if setValidators(...) was called with 2 validators and then setValidator(...) was called it would only change the first validator stored internally. The validator that previously was set at index 1 in the array is still maintained by BindSpec. Also the setValidator(...) method always assumes that an array with at least a length of 1 exists. If setValidators(...) is called with an array of length zero and then a call is made to setValidator(...) an IndexOutOfBoundsException is thrown. Same problems would occur with setting it to null except of course a NPE will be thrown. When I get some time I'll try to apply a patch for this. The changes that I'll make will be that when any set is called it removes all previous values.
|
2006-04-06 12:32:54
| 1,144,340,000
|
verified fixed
|
2f716b5
| 1,150,730,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/BindSpec.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/BindSpecTests.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/BindingTestSuite.java
|
Eclipse_Platform_UI
|
3,760
| 112,045
|
Bug 112045 [CellEditors] ComboBoxCellEditor doesn't set items if creation of control is deferred
|
If the ComboBoxCellEditor is instantiated without creating the control the items are not set on the ComboBoxCellEditor on call to createControl(Composite parent). The following snippet displays the problem. public class ComboEditor { void run() { Display display = new Display(); Shell shell = new Shell(display); String[] items = new String[]{"Item 1", "Item 2", "Item 3"}; ComboBoxCellEditor editor = new ComboBoxCellEditor(); editor.setItems(items); editor.create(shell); //Uncomment to set items. // editor.setItems(items); editor.activate(); editor.getControl().setVisible(true); editor.getControl().setBounds(0, 0, 100, 20); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) display.sleep(); } display.dispose(); } public static void main(String[] args) { new ComboEditor().run(); } }
|
2005-10-09 01:06:50
| 1,128,830,000
|
verified fixed
|
dfd144f
| 1,150,730,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ComboBoxCellEditor.java
|
Eclipse_Platform_UI
|
3,761
| 137,425
|
Bug 137425 [DataBinding] ValidationError javadoc makes references to ValidationResult
|
It looks like ValidationError used to be named ValidationResult as the javadoc makes references to types that are now a part of ValidationError. Attaching patch...
|
2006-04-19 00:10:50
| 1,145,420,000
|
verified fixed
|
55c2f96
| 1,150,730,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/validation/ValidationError.java
|
Eclipse_Platform_UI
|
3,762
| 44,861
|
Bug 44861 [CellEditors] DialogCellEditor does not handle focusLost()
|
Make sure you have org.eclipse.ui.examples.propertysheet_2.1.0 and open any *.usr file. Select "Richard" from the outline view and select "eyecolor" from the properties view (notice the ... button). Now open the search dialog and notice the ... button is still there. If you select other text or combo properties, notice the editor has been deactivated.
|
2003-10-14 18:11:57
| 1,066,170,000
|
verified fixed
|
bb3983d
| 1,150,730,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/DialogCellEditor.java
|
Eclipse_Platform_UI
|
3,763
| 139,407
|
Bug 139407 [DataBinding] TestMasterDetail not updating when changing Person State
|
When running org.eclipse.jface.examples.databinding/src/org.eclipse.jface.examples.databinding.nestedselection.TestMasterDetail and editing a Person's State the master table isn't updated when the State's value changes. The reason for this is that the Person object isn't notifying listeners of changes.
|
2006-04-29 20:03:12
| 1,146,360,000
|
verified fixed
|
63e79c3
| 1,150,730,000
|
examples/org.eclipse.jface.examples.databinding/src/org/eclipse/jface/examples/databinding/HelloWorld.java examples/org.eclipse.jface.examples.databinding/src/org/eclipse/jface/examples/databinding/model/SimpleModel.java examples/org.eclipse.jface.examples.databinding/src/org/eclipse/jface/examples/databinding/model/SimpleOrder.java examples/org.eclipse.jface.examples.databinding/src/org/eclipse/jface/examples/databinding/model/SimplePerson.java examples/org.eclipse.jface.examples.databinding/src/org/eclipse/jface/examples/databinding/nestedselection/Model.java examples/org.eclipse.jface.examples.databinding/src/org/eclipse/jface/examples/databinding/nestedselection/Order.java examples/org.eclipse.jface.examples.databinding/src/org/eclipse/jface/examples/databinding/nestedselection/Person.java examples/org.eclipse.jface.examples.databinding/src/org/eclipse/jface/examples/databinding/nestedselection/TestMasterDetail.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/BindingTestSuite.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/examples/model/PersonTests.java
|
Eclipse_Platform_UI
|
3,764
| 146,435
|
Bug 146435 [DataBinding] Mocks InvocationHandler throws an exception when returning primitive type
|
The InvocationHandler in the Mocks class attempts to return a new type via Class.newInstance for primitives which throws an InstantiationException.
|
2006-06-11 18:20:06
| 1,150,060,000
|
verified fixed
|
fd070d1
| 1,150,730,000
|
tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/BindingTestSuite.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/util/Mocks.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/util/MocksTest.java
|
Eclipse_Platform_UI
|
3,765
| 147,545
|
Bug 147545 [DataBinding] When attempting to fire a stale event AbstractObservable throws ClassCastException
|
The code in AbstractObservable for the firing of stale events appears to be incomplete. When listeners are added they're added as type IStaleListener but when retrieved they're cast to IChangeListener. I'm assuming that code was copied from the change listener code but not completed. Attaching patch...
|
2006-06-16 19:43:28
| 1,150,500,000
|
verified fixed
|
09ae5bf
| 1,150,550,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/AbstractObservable.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/list/AbstractObservableList.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/mapping/BaseObservableMapping.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/BindingTestSuite.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/ObservableTest.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/internal/databinding/provisional/observable/AbstractObservableTest.java
|
Eclipse_Platform_UI
|
3,766
| 132,947
|
Bug 132947 [DataBinding] small code style problems in AbstractObservable
|
I read new code for JFace data bindings and found couple code style problems in AbstractObservable. Nothing special, but looks not ideal, as it should be Eclipse code. :-) 1. In "addChangeListener". Collection listenerList; if (changeListeners instanceof IChangeListener) { IChangeListener l = (IChangeListener) changeListeners; listenerList = new ArrayList(); listenerList.add(l); } else { listenerList = (Collection) changeListeners; } if (listenerList.size() > 16) { HashSet listenerSet = new HashSet(); listenerSet.addAll(listenerList); changeListeners = listenerList; } Here listenerList declared as collection and initialized with ArrayList. But couple lines below listenerSet declared not as Collection or even Set, but directly as HashSet. 2. In "removeChangeListener". Collection listenerList = (Collection) changeListeners; listenerList.remove(listener); if (listenerList.size() == 0) { changeListeners = null; if (!hasListeners()) { lastListenerRemoved(); } } I think that it is better use "listenerList.isEmpty()" instead of "listenerList.size() == 0". Here I have also two sub-questions: 2.1. may be check that remove() returns "true"? In theory it is possible that collection does not contains passed listener (because of bug in user code?), so rest of code is not required. 2.2. I am not sure, but may be it is good to check for single element is listenerList and rollback to direct listener as changeListeners? Well, most probably no, but just idea...
|
2006-03-23 01:34:39
| 1,143,100,000
|
verified fixed
|
df7d74b
| 1,150,510,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/internal/viewers/StructuredViewerObservableCollectionWithLabels.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/AbstractObservable.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/list/AbstractObservableList.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/list/ObservableList.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/mapping/BaseObservableMapping.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/set/ObservableSet.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/value/AbstractObservableValue.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/observable/value/AbstractVetoableValue.java
|
Eclipse_Platform_UI
|
3,767
| 137,877
|
Bug 137877 [DataBinding] StructuredViewerObservableValue javadoc and code cleanup
|
I started looking at this class to see what it was doing and noticed a potential problem if anyone was to extend this class and this snowballed into adding javadoc, cleaning up the code a bit, and writing tests. Changes made: * documented doGetValue() and the constructor to warn of subclassing issues. see explanation below... * changed doGetValue() from public to protected. I'm assuming since this is a template method it is only meant for the eyes of subclasses and other package classes. * removed the 'attribute' parameter from the constructor because the constructor wouldn't allow but one value for attribute and would throw an IAE if it wasn't correct. Every method was then checking this variable for the same value and because it was only set at construction and only one value was allowed it seemed redundant. * removed 'attribute' from the class and from every method because of the removal of it from the constructor. * added validation for constructor parameters doGetValue() is public and if someone was to extend this class and override doGetValue() this method would get invoked before their subclass was fully initialized because their constructor would not have ran yet. Because this class extends from AbstractObservableValue and doGetValue() is declared as protected it didn't seem like much could be done about changing this so I ended up documenting it thoroughly in the constructor javadoc and the javadoc for doGetValue(). The constructor signature change and the validation the constructor parameter are both nonpassive changes. I also was wanting to rename the class to StructuredViewerSingleSelectionObservableValue but didn't do so in order to be able to provide a patch that allowed for the easy viewing of the changes made. Because of the constructor change I had to change ViewersObservableFactory as well when constructing the object.
|
2006-04-21 01:03:42
| 1,145,600,000
|
verified fixed
|
5dbe246
| 1,150,430,000
|
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/internal/viewers/SelectionProviderSingleSelectionObservableValue.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/internal/viewers/StructuredViewerObservableValue.java bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/viewers/ViewersObservableFactory.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/BindingTestSuite.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/internal/databinding/internal/viewers/SelectionProviderSingleSelectionObservableValueTest.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/internal/databinding/provisional/viewers/ViewersObservableFactoryTest.java
|
Eclipse_Platform_UI
|
3,768
| 143,474
|
Bug 143474 [FieldAssist] Info popup in ContentProposalAdapter shows obsolete information
|
This problem occurs when the info popup dialog is already up. When I scroll through a list of content proposals in the content proposal popup dialog, if the current selection has extra information to show, the associated info popup dialog comes up. Then if I scroll to another selection which does not have any extra information to show, the info popup dialog does not go away. Instead, it keeps showing the context information from my last selection. Shouldn't the info popup be closed if the new selection has no additional information to show? Thanks.
|
2006-05-24 10:52:22
| 1,148,480,000
|
verified fixed
|
6dd2e93
| 1,150,420,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
3,769
| 147,377
|
Bug 147377 [Field Assist] - open proposal popup should close when there are no valid proposals left
| null |
2006-06-15 18:32:21
| 1,150,410,000
|
verified fixed
|
af27fa6
| 1,150,420,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
3,770
| 144,522
|
Bug 144522 [Field Assist] - should proposal popup ever open if empty?
| null |
2006-05-30 15:07:43
| 1,149,020,000
|
verified fixed
|
19894e0
| 1,150,410,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
3,771
| 142,172
|
Bug 142172 [Wizards] Small overhead in WizardDialog
|
Here is code of method WizardDialog.updateDescriptionMessage: private void updateDescriptionMessage() { pageDescription = currentPage.getDescription(); setMessage(currentPage.getDescription()); } As you can see, it access currentPage.getDescription() two times, but value of this method is already in field pageDescription.
|
2006-05-17 05:18:11
| 1,147,860,000
|
resolved fixed
|
e047b60
| 1,150,410,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/wizard/WizardDialog.java
|
Eclipse_Platform_UI
|
3,772
| 138,190
|
Bug 138190 [Wizards] Save As doesn't check validity of location
|
Build id: N20060424-0010 1) Create project "P1" containing file "a.txt" 2) Open the editor on a.txt 3) File > Save As 4) In the "File name" field, enter "c:\temp\a.txt" (I was somehow thinking I could save the file in the file system from here). 5) Click Ok. It creates a file /P1/temp/a.txt I would have expected an error in the wizard as soon as I entered the ":" character, which is not a valid character in file names on windows.
|
2006-04-24 10:20:41
| 1,145,890,000
|
resolved fixed
|
c53dac1
| 1,150,400,000
|
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/dialogs/SaveAsDialog.java bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/dialogs/WizardNewFileCreationPage.java
|
Eclipse_Platform_UI
|
3,773
| 147,305
|
Bug 147305 [Workbench] Fix detection of early event loop spinning in debug mode
|
Workbench.runUI uses currently checks for early spinning of the event loop if WorkbenchPlugin.DEBUG is true, but WorkbenchPlugin.DEBUG is only set to true later in the initialization of the Workbench. Should use WorkbenchPlugin.getDefault().isDebugging() instead.
|
2006-06-15 11:02:33
| 1,150,380,000
|
resolved fixed
|
37cad62
| 1,150,400,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Workbench.java
|
Eclipse_Platform_UI
|
3,774
| 130,915
|
Bug 130915 [Progress] 'X' button on completed task shows "Cancel Task" as tooltip
|
3.2 M5 In the Progress view, I had a completed sync job showing the gray X button, but its tooltip read "Cancel Task". I was expecting "Remove Task" or "Remove Completed Task".
|
2006-03-08 10:43:05
| 1,141,830,000
|
verified fixed
|
f670f7f
| 1,150,390,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressInfoItem.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressMessages.java
|
Eclipse_Platform_UI
|
3,775
| 131,851
|
Bug 131851 [Progress] 'User Operation is Waiting' progress dialog is not accessible
|
I20060217-1115 The 'User Operation is Waiting' progress dialog is not accessible. I found no way to give focus to the list of jobs nor to cancel a job. Tab and/or Up/Down keys should select jobs and Cancel and/or Delete should cancel the selected job. Steps to reproduce: Start checking out org.eclipse.swt from CVS. While the checkout progresses, select .classpath_win32 in the Package Explorer and press F2.
|
2006-03-14 19:09:09
| 1,142,380,000
|
verified fixed
|
35d15f7
| 1,150,380,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/DetailedProgressViewer.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressMonitorFocusJobDialog.java
|
Eclipse_Platform_UI
|
3,776
| 144,527
|
Bug 144527 [Wizards] WizardDialog should have the maxmize button
|
RC6 Many of our wizards show up quite scrunched initially in High Contrast mode. When they are expanded the size is quite good. We should set the maximize flag so that we get a maximize button on the dialog shell.
|
2006-05-30 15:44:56
| 1,149,020,000
|
resolved fixed
|
068e707
| 1,150,320,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/wizard/WizardDialog.java
|
Eclipse_Platform_UI
|
3,777
| 139,542
|
Bug 139542 [Progress] Infrastructure jobs should not be shown in System jobs mode
|
RC2 It turns out the more people show system jobs that originally thought. We should only show those for updating the problems view and the animation when an options file is set.
|
2006-05-01 12:35:09
| 1,146,500,000
|
verified fixed
|
0e7fbc2
| 1,150,310,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/misc/Policy.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressManager.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressManagerUtil.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressMonitorJobsDialog.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressViewUpdater.java
|
Eclipse_Platform_UI
|
3,778
| 129,755
|
Bug 129755 [Decorators] CompositeImageDescriptor: Problem on overlay with transparent areas in PNG
| null |
2006-02-28 06:11:58
| 1,141,130,000
|
verified fixed
|
e3dd797
| 1,150,300,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/resource/CompositeImageDescriptor.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/decorators/DecoratorOverlayIcon.java
|
Eclipse_Platform_UI
|
3,779
| 146,265
|
Bug 146265 [FieldAssist] Problems with vertical filled control
|
When using text with fill vertical, the text of the decorated field will not fill all the space. DecoratedField decoNormal = new DecoratedField(shell, SWT.BORDER, new TextControlCreator()); FieldDecoration fieldDeco = FieldDecorationRegistry.getDefault(). getFieldDecoration(FieldDecorationRegistry.DEC_CONTENT_PROPOSAL); decoNormal.addFieldDecoration(fieldDeco, SWT.TOP | SWT.LEFT, false); decoNormal.getLayoutControl().setLayoutData( new GridData(SWT.FILL, SWT.FILL, true, true) ); If i do this trick it will work but it is not a good practice i think : FormData fieldData = (FormData)decoVerticalFilled.getControl().getLayoutData(); fieldData.bottom = new FormAttachment(100, 0); decoVerticalFilled.getControl().setLayoutData(fieldData); Regards
|
2006-06-09 11:15:38
| 1,149,870,000
|
verified fixed
|
49690fc
| 1,150,220,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/DecoratedField.java
|
Eclipse_Platform_UI
|
3,780
| 146,750
|
Bug 146750 [DataBinding][CompositeTable] Crash when dragging scroll bar
|
Run CompositeTableTest Drag scroll bar down Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: -1, Size: 6 at java.util.LinkedList.entry(LinkedList.java:360) at java.util.LinkedList.get(LinkedList.java:303) at org.eclipse.jface.examples.databinding.compositetable.InternalCompositeTable.currentRow(InternalCompositeTable.java:1671) at org.eclipse.jface.examples.databinding.compositetable.InternalCompositeTable.fireRowDepartEvent(InternalCompositeTable.java:1511) at org.eclipse.jface.examples.databinding.compositetable.InternalCompositeTable.setTopRow(InternalCompositeTable.java:732) at org.eclipse.jface.examples.databinding.compositetable.InternalCompositeTable$2.widgetSelected(InternalCompositeTable.java:1239) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1074) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3158) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2838) at org.eclipse.jface.examples.databinding.compositetable.test.CompositeTableTest.main(CompositeTableTest.java:167)
|
2006-06-12 23:59:31
| 1,150,170,000
|
resolved fixed
|
31bdf15
| 1,150,170,000
|
examples/org.eclipse.jface.examples.databinding/src/org/eclipse/jface/examples/databinding/compositetable/InternalCompositeTable.java
|
Eclipse_Platform_UI
|
3,781
| 145,536
|
Bug 145536 [Progress] TVT3.2:TCT861: DA: US date displayed in error msg
|
OS: RHEL 3.1 Must fix or not a must fix: YES Build date: 060406 Component name = DTP Blocking: NO Language: da Bitmap Location: V:\defects\da\21.001210.jpg Tester Name: Elsebeth Flarup Problem Description: From the menu bar, go to Window -> Show View -> Other... Expand Connectivity Select Data Source Explorer. Click Ok In the view that appears, you should see a list of available connection profile categories. Click the New Connection Profile button from the Data Source Explorer view menu In the wizard, select one of the available database types. For this test, select Derby Embedded Database. Click Next. On the ?Create connection profile? wizard page, you should be able to specify a name and description for your new Derby connection profile and determine if it should start automatically when it is created and the next time the Data Source Explorer opens. Put ?TVTDerby? in the Name field. Put ?TVTDerby description? in the Description field. Click Next Select the ??? button beside the driver combo box near the top of the wizard page. Select the ?Derby Embedded? driver category and click ?Add?? Choose one of the available driver templates for Derby (for example, Derby Embedded JDBC Driver for Derby 10.0) and click OK Select derby.jar reference in Driver File(s) list and click ?Edit Jar/Zip.? Using the ?Select the file? dialog, find the location of the derby.jar file on your system and click OK. The path in the Driver file(s) list should update.. At this point, your driver is set up. If you want to change where the new Derby database will be created, you can modify the Connection URL value in the Properties portion of the dialog. Click OK on the Edit Driver Entry dialog to save your changes. On the Driver Definitions dialog, select your new driver and click OK. You may need to change the directory to the Derby database in the URL field. Change it to a drive a Linux directory. Test your profile to see if it connects. Click the Test Connection button. At this point I get an error (problem with the driver), and the error message displays the date and time in US English format instead of Danish. Should be "man jun 5" (as displayed by the OS) or the format returned by the JDK for the da_DK locale. This article was reassigned from Category:''TVT/Testing''.
|
2006-06-06 09:59:05
| 1,149,600,000
|
verified fixed
|
17f14ad
| 1,150,130,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ErrorInfo.java
|
Eclipse_Platform_UI
|
3,782
| 145,931
|
Bug 145931 [Dialogs] StatusDialog: when status is on same line as button bar, status is aggressively truncated
|
Version: 3.2.0 Build id: I20060602-1317 On my workstation, there remains plenty of space to expand the message. Don't know how easy it would be to get it to 'auto-adjust', but the result is a bit disappointing. [I'll attached a partial screen copy.]
|
2006-06-08 02:26:31
| 1,149,750,000
|
verified fixed
|
ff31417
| 1,149,790,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/TrayDialog.java
|
Eclipse_Platform_UI
|
3,783
| 144,241
|
Bug 144241 [Wizards] Help icon showing up twice in the new wizard
|
RC6 We have 2 help icons showing up in the new dialog currently - one of which is disabled.
|
2006-05-29 10:43:27
| 1,148,910,000
|
verified fixed
|
0929fbb
| 1,149,710,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchMessages.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/NewWizardNewPage.java
|
Eclipse_Platform_UI
|
3,784
| 139,254
|
Bug 139254 [Progress] Sleeping Jobs shown as running
|
3.2 20060428 We are currently showing sleeping jobs as running as we are: 1) Not using thier icon 2) Using the finished string when it is sleeping. We should use the sleeping string
|
2006-04-28 14:05:30
| 1,146,250,000
|
verified fixed
|
9ff9222
| 1,149,690,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressInfoItem.java
|
Eclipse_Platform_UI
|
3,785
| 142,817
|
Bug 142817 [Progress] No F1 help for progress view
|
Build: 3.2 RC5 Open the progress view. Press F1. There is no context help available.
|
2006-05-19 14:26:45
| 1,148,060,000
|
verified fixed
|
0575436
| 1,149,690,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/DetailedProgressViewer.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressView.java
|
Eclipse_Platform_UI
|
3,786
| 139,769
|
Bug 139769 [Progress] Builds show X instead of red square to cancel
|
RC2 Any reschedulable job (like the auto build) is showing up in the progress view as completed as it has the result from the previous build still. The condition to check if the job is completed should be if (infos[i].getJob().getState() != Job.NONE) not if (infos[i].getJob().getResult() == null)
|
2006-05-02 13:34:22
| 1,146,590,000
|
verified fixed
|
85f8d13
| 1,149,690,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/ProgressInfoItem.java
|
Eclipse_Platform_UI
|
3,787
| 140,861
|
Bug 140861 [Workbench] TVT3.2:TCT319: TVT - zh: Shortcut key problems in the menu.
|
OS : RHEL 3.1 Must fix or not a must fix: YES Build date: 0507 Blocking: NO Language: zh Bitmap Location: V:\defects\zh Tester Name: Echo Zhou Problem Description: The memonics are underscored first Chinese characters, which looks appear as redundant memonics. Procedure: 1. Start Eclipse 2. Select Window > Open Perspective, in the submenu a lot of memonics are underscored first Chinese characters. Please help to investigate. Thanks in advance for your help! Echo Zhou Same for T.Chinese. Re-attaching screen capture to match TCT number... Hello, Same problem for Korean build. Please remove the extra mnemonic. If those menus are supposed to have mnemonic key, please update Enlgish source files by adding like '&', so that we recognize and properly translate them. Thanks, Junghan This article was reassigned from Category:''TVT/Testing''.
|
2006-05-09 13:32:08
| 1,147,200,000
|
verified fixed
|
b299810
| 1,149,620,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/actions/OpenPerspectiveAction.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ShowInAction.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ShowViewAction.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/actions/NewWizardShortcutAction.java
|
Eclipse_Platform_UI
|
3,788
| 145,594
|
Bug 145594 Typo in javadoc: ResourceSelectionDialog.java
|
In the Javadoc for org.eclipse.ui.dialogs.ResourceSelectionDialog, the example says: dialog.setInitialSelections(selectedResources)); note the extra ')'. I noticed when trying to paste this example into my own code.
|
2006-06-06 14:27:55
| 1,149,620,000
|
resolved fixed
|
dd46faa
| 1,149,620,000
|
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/dialogs/ResourceSelectionDialog.java
|
Eclipse_Platform_UI
|
3,789
| 144,979
|
Bug 144979 Add entry to ISV What's New about TreeViewer
| null |
2006-06-01 16:48:05
| 1,149,190,000
|
verified fixed
|
60972fb
| 1,149,210,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ILazyTreeContentProvider.java
|
Eclipse_Platform_UI
|
3,790
| 138,138
|
Bug 138138 [WorkbenchLauncher] Improve documentation (Progressbar in splashscreen doesn't appear)
|
I made the product configuration and add a progressbar in the branding tab. The splashscreen appears, but without the progressbar.
|
2006-04-23 10:11:49
| 1,145,800,000
|
verified fixed
|
62827c7
| 1,149,200,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IWorkbenchPreferenceConstants.java
|
Eclipse_Platform_UI
|
3,791
| 126,061
|
Bug 126061 [Viewers] Need to document that virtual tables and trees ignore sorters and filters
| null |
2006-02-01 13:28:30
| 1,138,820,000
|
verified fixed
|
1471083
| 1,149,020,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewer.java
|
Eclipse_Platform_UI
|
3,792
| 126,874
|
Bug 126874 [Viewers] Apidoc for setting ITableColorProvider missing
|
I wanted to add some color to my table. First i found out about ITableColorProvider, but didnt know where to register it. After digging into the eclipse source code, i found out that org.eclipse.jface.viewers.TableViewer has a method named setLabelProvider with one argument IBaseLabelProvider. In the code, but not the javadoc, it says that you can also register ITableFontProvider and ITableColorProvider with it, assuming the instance implements these types, too. Please consider documentating this feature in the corresponding javadoc, as its part of the methods functionality and contract.
|
2006-02-08 03:53:34
| 1,139,390,000
|
verified fixed
|
440b76e
| 1,149,020,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewer.java
|
Eclipse_Platform_UI
|
3,793
| 144,225
|
Bug 144225 [FieldAssist] NullPointerException in ContentProposalAdapter$ContentProposalPopup.open()
|
I am using Eclipse 3.2RC6 and was playing around with the org.eclipse.jface.fieldassist package. I wanted to implement a simple auto-complete textfield with the ContentProposalAdapter class. But if the first letter which is entered in the textfield does not yield any proposals, the call to getSelectedProposal() in line 859 of ContentProposalAdapter.java returns null and therefore a NPE is thrown, rather than just not showing the popup at all. The following snippet shows this behaviour (just type any letter except "p"): import org.eclipse.jface.fieldassist.ContentProposalAdapter; import org.eclipse.jface.fieldassist.IContentProposal; import org.eclipse.jface.fieldassist.IContentProposalProvider; import org.eclipse.jface.fieldassist.TextContentAdapter; import org.eclipse.swt.SWT; import org.eclipse.swt.layout.FillLayout; import org.eclipse.swt.widgets.Display; import org.eclipse.swt.widgets.Shell; import org.eclipse.swt.widgets.Text; public class ExampleSnippet { public static void main(String[] args) { Display display = new Display(); Shell shell = new Shell(display); shell.setLayout(new FillLayout()); Text text = new Text(shell, SWT.NONE); ContentProposalAdapter adapter = new ContentProposalAdapter(text, new TextContentAdapter(), new TextProposalProvider(), null, null); adapter.setProposalAcceptanceStyle(ContentProposalAdapter.PROPOSAL_REPLACE); shell.setSize(200, text.getSize().y); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) display.sleep(); } display.dispose(); } } class TextProposalProvider implements IContentProposalProvider { private String str = "Proposal"; public IContentProposal[] getProposals(String contents, int position) { IContentProposal[] proposals; if (str.toLowerCase().startsWith(contents.toLowerCase())) { proposals = new IContentProposal[1]; proposals[0] = new IContentProposal() { public String getContent() { return str; } public int getCursorPosition() { return str.length(); } public String getDescription() { return null; } public String getLabel() { return null; } }; } else { proposals = new IContentProposal[0]; } return proposals; } }
|
2006-05-29 09:51:59
| 1,148,910,000
|
verified fixed
|
a324eda
| 1,149,020,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java
|
Eclipse_Platform_UI
|
3,794
| 144,207
|
Bug 144207 next / prev not working anymore in search view
|
RC6 Seems to be a regression since RC4. - create a new Java file with content below - in the Java editor use 'Ctrl + .' and 'Ctrl + ,' (Next / Previous) to toggle through the 2 errors in the file - select 'args', Invoke 'Search > Occurrences In File > Indentifier' - set focus to the search view (3 matches) and try to use 'Ctrl + .' 'Ctrl + ,' to go through the search results. -> does nothing in the search view but still toggles highlighting in the editor - same problem with the prev / next toolbar buttons of the search view Using the global menu actions, this works. I verified that this bug was not yet in RC4 (I20060512-1600) ----- A.java package pack; import java.util.List; import java.util.List2; public class A implements List { /** * @param args */ public static void main(String[] args) { System.out.println(args[0]); } }
|
2006-05-29 07:14:07
| 1,148,900,000
|
verified fixed
|
d132108
| 1,149,020,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/expressions/LegacyEditorActionBarExpression.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/expressions/LegacyEditorContributionExpression.java
|
Eclipse_Platform_UI
|
3,795
| 144,144
|
Bug 144144 Javadoc errors in N20060528-0010 build
|
/builds/N200605280010/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.jface/src/org/eclipse/jface/layout/GridDataFactory.java:136: warning - Tag @see: Class or Package not found: fillDefaults /builds/N200605280010/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.jface/src/org/eclipse/jface/layout/GridDataFactory.java:173: warning - Tag @see: Class or Package not found: swtDefaults /builds/N200605280010/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.ui.ide/src/org/eclipse/ui/ide/fileSystem/FileSystemContributor.java:27: warning - Tag @see: Class or Package not found: org.eclipse.ui.ide.filesystemSupport /builds/N200605280010/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.ui.ide/src/org/eclipse/ui/ide/fileSystem/FileSystemContributor.java:27: warning - Tag @see: Class or Package not found: org.eclipse.core.filesystem.filesystem
|
2006-05-28 21:56:41
| 1,148,870,000
|
verified fixed
|
2cd037e
| 1,148,910,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/layout/GridDataFactory.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/fileSystem/FileSystemContributor.java
|
Eclipse_Platform_UI
|
3,796
| 95,659
|
Bug 95659 [Workbench] Workbench#isRunning returns true when the event loop is not yet running
|
isRunning() returns the value of the boolean field runEventLoop, which is initialized to true upon creation of the Workbench instance. Therefore, PlatformUI#isWorkbenchRunning will return true as soon as the Workbench instance is created. It should probably return true only after the Workbench has been restored and/or initialized properly.
|
2005-05-17 16:50:24
| 1,116,360,000
|
resolved wontfix
|
adf20cc
| 1,148,400,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/PlatformUI.java
|
Eclipse_Platform_UI
|
3,797
| 92,564
|
Bug 92564 [Viewers] (doc only) incorrect use of html in javadoc of BackgroundContentProvider
|
Version: 3.1.0 Build id: I20050419-1200 The section that is explaining the information flow is not correctly defining the ordered list. Each item should be wrapped in a 'li', not an 'ol'. Index: BackgroundContentProvider.java =================================================================== RCS file: /home/eclipse/org.eclipse.jface/src/org/eclipse/jface/viewers/deferred/BackgroundContentProvider.java,v retrieving revision 1.4 diff -u -r1.4 BackgroundContentProvider.java --- BackgroundContentProvider.java 28 Mar 2005 14:57:36 -0000 1.4 +++ BackgroundContentProvider.java 25 Apr 2005 11:13:00 -0000 @@ -38,12 +38,12 @@ * <p> * Information flow is like this: * </p> - * <ol>IConcurrentModel sends unordered elements to BackgroundContentProvider (in a background thread)</ol> - * <ol>BackgroundContentProvider sorts, filters, and sends element/index pairs to - * ConcurrentTableUpdator (in a background thread)</ol> - * <ol>ConcurrentTableUpdator batches the updates and sends them to an AbstractVirtualTable - * (in the UI thread)</ol> - * <li> + * <ol> + * <li>IConcurrentModel sends unordered elements to BackgroundContentProvider (in a background thread)</li> + * <li>BackgroundContentProvider sorts, filters, and sends element/index pairs to + * ConcurrentTableUpdator (in a background thread)</li> + * <li>ConcurrentTableUpdator batches the updates and sends them to an AbstractVirtualTable + * (in the UI thread)</li> * </ol> * * <p>
|
2005-04-25 07:12:40
| 1,114,430,000
|
verified fixed
|
51991ed
| 1,148,400,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/deferred/BackgroundContentProvider.java
|
Eclipse_Platform_UI
|
3,798
| 142,498
|
Bug 142498 [WorkingSets] TVT3.2:TCT539: DA: Working Window Set in English
|
OS: RHEL 3.1 Must fix or not a must fix: YES Build date: 051606 Component name = EMFT Blocking: NO Language: da Bitmap Location: V:\defects\da Tester Name: Mette Djoerup (user ID: dantvt03) Problem Description: In the Package Explorer view, click the menu icon in the top right corner. A string is in English: Window Working Set. This string has been translated and is found in the eclipse\plugins\org.eclipse.ui.workbench\org\eclipse\ui\internal\messages.properties file. Mette (id dantvt03) If it has been translated and it was in the last build than it should be viewable to you. Ensure that you have added "-clean" when you start eclipse. To do this in linux (from your eclipse root directory): ./eclipse -clean Or if you are running from windows: Right click on your eclipse shortcut and add "-clean" to the end of your target path. Starting eclipse with the -clean option does not help. The string was probably never in the build. Mette The newest build is not ready but will be available later today. Check with the new driver then to see if the string is present. It not, please re-drop it with the rest of your files. Same in Norwegian version. Reopening to open a bug... it doesn't look like the string is externalized. This article was reassigned from Category:''TVT/Testing''.
|
2006-05-18 10:31:55
| 1,147,960,000
|
closed fixed
|
b323468
| 1,148,400,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/WorkbenchPage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/WorkingSetSelectionDialog.java
|
Eclipse_Platform_UI
|
3,799
| 142,564
|
Bug 142564 Eclipse hangs when deleting a "dirty" product file from a project
|
1. Start a new instance of Eclipse (you won't be able to exit cleanly from this scenario so don't have any unsaved work) 2. In a plugin project, add a new *.product file (File->New->Other->Plugin Dev->Product Configuration) 3. In the wizard, name the file foo.product, and select to create a file with basic settings (first radio button). Finish. 4. In the editor, type something in the "Product Name" box, just to make the file dirty. 5. Without saving, select the file in the package explorer, then press "Delete" (or right-click->Delete) 6. Eclipse politely asks "Are you sure you want to delete...?". Of course you are, so click "Yes". 7. It does something, then asks: '...' has been modified. Save changes? No, we don't want to save changes. Click "No". Result: Eclipse is hanging so badly it has to be shot down using an Anti Eclipse Missile (AEM, aka kill -9). Actually, while writing this report I noticed the hang occurs even before you answer the last dialog.
|
2006-05-18 14:40:41
| 1,147,980,000
|
verified fixed
|
d43c6b9
| 1,148,010,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/SaveablesList.java
|
Eclipse_Platform_UI
|
3,800
| 137,091
|
Bug 137091 [KeyBindings] Toggle Mark Occurrences shortcut is broken
|
As of some milestone after M3, SHIFT-ALT-O does not work at all.
|
2006-04-17 17:21:09
| 1,145,310,000
|
resolved fixed
|
45a0d45
| 1,147,970,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/SubActionBars.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorActionBars.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorManager.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorReference.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PartSite.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/expressions/LegacyEditorActionBarExpression.java
|
Eclipse_Platform_UI
|
3,801
| 142,264
|
Bug 142264 [Workbench] After closing all perspectives, Project Explorer will never show content
|
I closed all my perspective and then opened the Resource perspective. I then opened the Project Explorer but it was empty. Now, no matter what I do (i.e. restart, disable and reenable content), I cannot get the view to show any content.
|
2006-05-17 11:44:14
| 1,147,880,000
|
verified fixed
|
3672501
| 1,147,970,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/actions/OpenPerspectiveDialogAction.java
|
Eclipse_Platform_UI
|
3,802
| 136,724
|
Bug 136724 [CommonNavigator] Compile error decorations remain until the element is selected
|
Found in I20060413-0010 Construct a workspace with multiple/related projects that compile without errors (I found this using the org.eclipse.jface.tests.databinding and org.eclipse.jface.examples.databinding projects but any set should do). Open the Project Explorer Expand one of the projects ("A") so you can see classes Close a project that "A" depends on...you should see error decorators as expected Re-open the project. The error decorators remain until the tree element is selected by clicking on it (multi-select won't do it).
|
2006-04-13 15:02:22
| 1,144,950,000
|
verified fixed
|
571712f
| 1,147,800,000
|
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentServiceLabelProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorContentExtension.java
|
Eclipse_Platform_UI
|
3,803
| 141,612
|
Bug 141612 IWorkbenchWidget has incorrect copyright info
|
20060512 The copyright should say 2005,2006 and it is missing a since 3.2 tag
|
2006-05-12 15:17:49
| 1,147,460,000
|
verified fixed
|
843b0f1
| 1,147,670,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/menus/IWorkbenchWidget.java
|
Eclipse_Platform_UI
|
3,804
| 141,191
|
Bug 141191 [WorkbenchParts] ISaveablePart2 prompting does not happen when closing a perspective
| null |
2006-05-11 00:12:06
| 1,147,320,000
|
verified fixed
|
e4572a9
| 1,147,380,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IWorkbenchPage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchPage.java
|
Eclipse_Platform_UI
|
3,805
| 141,193
|
Bug 141193 [WorkbenchParts] Javadoc change: document limitations for implementers of ISaveablesSource
| null |
2006-05-11 00:22:18
| 1,147,320,000
|
verified fixed
|
8d19a73
| 1,147,330,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/ISaveablesSource.java
|
Eclipse_Platform_UI
|
3,806
| 141,192
|
Bug 141192 [Viewers] Javadoc change about multiple equal elements in StructuredViewer and AbstractTreeViewer
| null |
2006-05-11 00:17:20
| 1,147,320,000
|
verified fixed
|
2bbdbff
| 1,147,320,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractTreeViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/StructuredViewer.java
|
Eclipse_Platform_UI
|
3,807
| 138,283
|
Bug 138283 [KeyBindings] Action set with accelerator causes conflict
|
Build: 3.2 RC1a 1) Installed the attached plugin 2) Switch to the Java perspective 3) Type Ctrl+Shift+T -> Nothing happens. There is a conflict between the JDT's "Open Type" action, and the action set defined by the attached plugin. The conflict occurs even though the action set in question is not enabled in the Java perspective. Actions from a disabled action set should not be stealing key bindings from actions that do apply in that perspective. This occurs if you install the Eclipse Callisto release with JDT and BIRT. BIRT defines an action set with an action bound to Ctrl+Shift+T. This causes the JDT "Open Type" action to not be reachable by the Ctrl+Shift+T binding in the Java perspective.
|
2006-04-24 18:22:38
| 1,145,920,000
|
verified fixed
|
99903f7
| 1,147,290,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/bindings/BindingManager.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/BindingService.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/LegacyActionPersistence.java
|
Eclipse_Platform_UI
|
3,808
| 125,138
|
Bug 125138 [LinkedResources] cannot extend variable
|
Using I20060118-0800 Using the contextual menu upon a project that has at least one linked source folder: - Build Path/Configure Build Path; - Source tab; - select a linked source folder, Edit; - Variables; - define CURRENT_WORKSPACE pointing to the current workspace root: - New; - Name: CURRENT_WORKSPACE; - Folder...: select the workspace root, then OK; - OK; - Extend: gets a 'No entries available'. I may miss a point here, but I believe this not correct. I would expect to be able to select a subdirectory of my current workspace. Pointing the variable to a Java project root doesn't seem to help.
|
2006-01-25 05:02:36
| 1,138,180,000
|
verified fixed
|
d69681e
| 1,147,290,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/ide/dialogs/PathVariableSelectionDialog.java
|
Eclipse_Platform_UI
|
3,809
| 137,824
|
Bug 137824 [WorkbenchParts] Return ISaveablePart2.CANCEL from promptToSaveOnClose still closes the EditorPart
|
I have a EditorPart that implements ISaveablePart2 as shown below. When I return ISaveablePart2.CANCEL the EditorPart is still closed. This may be the result of SaveablesList.preCloseParts return a non-null result (PostCloseInfo) which contains my part in the partsClosing array. public int promptToSaveOnClose() { if (isDirty()) { boolean answer = MessageDialog.openQuestion(_shell, "Close Virtual Terminal", "The terminal emulator is still active. Would you like to close the editor?"); if (!answer) { return ISaveablePart2.CANCEL; } } return ISaveablePart2.NO; }
|
2006-04-20 15:09:48
| 1,145,560,000
|
closed fixed
|
2501c47
| 1,147,270,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/SaveablesList.java
|
Eclipse_Platform_UI
|
3,810
| 134,727
|
Bug 134727 [WorkbenchParts] Double save prompt with view that implements ISaveablePart
|
I have a view that implements ISaveablePart. Eclipse 3.1 prompted the user to save changes when closing the view. In 3.2M6, I get two prompts to save. In WorkbenchPage.hideView(IViewReference), persp.canCloseView(view) prompts the user to save changes. If the user clicks the No button, Perspective.canCloseView(IViewPart) returns true. Then, hideView gets the reference count (which is 1), gets the saveablesList, and calls savablesList.preCloseParts(...,true,...) which prompts the user to save a second time.
|
2006-04-04 08:26:08
| 1,144,150,000
|
verified fixed
|
abe625b
| 1,147,230,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Perspective.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchPage.java
|
Eclipse_Platform_UI
|
3,811
| 140,576
|
Bug 140576 [JFace] dialog has no icon or clipped error icon
|
1) for a Java Project select 'Configure Build Path' in context menu and goto tab 'Libraries' 2) edit Access Rules for a library (e.g. JRE System...) 3) see that the dialog and its children have no window icon
|
2006-05-08 10:34:50
| 1,147,100,000
|
verified fixed
|
04d295b
| 1,147,200,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/StatusDialog.java
|
Eclipse_Platform_UI
|
3,812
| 140,160
|
Bug 140160 [Field Assist] - JAVADOC ONLY- FieldDecorationRegistry API should specify that null dec description is allowed
| null |
2006-05-04 10:03:29
| 1,146,750,000
|
verified fixed
|
40fcc21
| 1,147,120,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/FieldDecorationRegistry.java
|
Eclipse_Platform_UI
|
3,813
| 139,700
|
Bug 139700 Long delay on package explorer selection changes in large workspace
|
Build: Eclipse 3.2 RC2 I created a workspace with every callisto project added (600 projects). Clicking around in the Navigator, I found a long delay responding to selection changes (2-3 seconds on a dual 3 Ghz machine with 1024 MB RAM). The culprit is CloseUnrelatedProjectsAction.getSelectedResources. The algorithm it uses for computing the set of "unrelated projects" is O(N^3) on the number of projects in the worst case (the worst case being where all N projects are tightly related to each other, as in the Callisto project case). This should be fixed for 3.2, either by improving the algorithm, or not updating the set of unrelated projects when the selection changes. It currently does this in order to update the enablement of the action (disabling the action when there are no open unrelated projects).
|
2006-05-02 10:49:54
| 1,146,580,000
|
verified fixed
|
f3899e4
| 1,146,680,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/actions/CloseUnrelatedProjectsAction.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/misc/DisjointSet.java
|
Eclipse_Platform_UI
|
3,814
| 139,511
|
Bug 139511 [CommonNavigator] getParent() fails in certain cases
|
In the implementation of getParents(), clients can sometimes fail to return the correct parent with the override cases taken into account. The attached patch fixes these issues, but should be reviewed by the Team Team to ensure that it does not cause any regressions for their cases.
|
2006-05-01 10:56:28
| 1,146,500,000
|
resolved fixed
|
760f9bf
| 1,146,680,000
|
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/actions/LinkEditorAction.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 bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/SafeDelegateTreeContentProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/StructuredViewerManager.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/filters/UpdateActiveExtensionsOperation.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/CommonNavigator.java
|
Eclipse_Platform_UI
|
3,815
| 133,749
|
Bug 133749 [Contributions] Create WatchExpression action show up twice in Variables View
|
* Show logical structure is on. * Expand map until you see key and value. * Select from variable "map" to "value" field. You need to multi-select to reproduce this. * You will see the "Create Watch Expression" action twice if you bring up the context menu. Testcase: TreeMap map = new TreeMap(); map.put("abc", "abc"); map.put("cbc", "abc"); map.put("dbc", "abc");
|
2006-03-28 18:10:09
| 1,143,590,000
|
verified fixed
|
1eb2c2a
| 1,146,680,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ObjectContributorManager.java
|
Eclipse_Platform_UI
|
3,816
| 138,823
|
Bug 138823 [MPE] Changes to MultiPageEditorPart causing endless loop
|
The following method was added in RC2... /** * If there is an adapter registered against the subclass of * MultiPageEditorPart return that. Otherwise, delegate to the internal * editor. * * @see org.eclipse.ui.part.WorkbenchPart#getAdapter(java.lang.Class) */ public Object getAdapter(Class adapter) { Object result = super.getAdapter(adapter); if (result == null && getActiveEditor() != null) { result = getActiveEditor().getAdapter(adapter); } return result; } We have subclasses that override this method and end up calling super.getAdapter(Class adapter). Problem is the activeEditor is one of our subclasses.... so an endless loop....
|
2006-04-26 23:59:41
| 1,146,110,000
|
resolved fixed
|
7485dd9
| 1,146,670,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/part/MultiPageEditorPart.java
|
Eclipse_Platform_UI
|
3,817
| 138,759
|
Bug 138759 [Dialogs] Compile errors against foundation 1.0: org.eclipse.jface
|
build n0426 I set org.eclipse.jface to compile against the Foundation 1.0 libraries and I got the following compile errors. They can be fixed by fully-qualifying the method reference. (either by "super" or "className.this") The method setImage is defined in an inherited type and an enclosing scope org.eclipse.jface/src/org/eclipse/jface/dialogs StatusDialog.java line 106 The method setImage is defined in an inherited type and an enclosing scope org.eclipse.jface/src/org/eclipse/jface/dialogs StatusDialog.java line 112
|
2006-04-26 17:05:12
| 1,146,090,000
|
verified fixed
|
c498296
| 1,146,670,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/StatusDialog.java
|
Eclipse_Platform_UI
|
3,818
| 139,385
|
Bug 139385 [Viewers] Viewer#setComparator(ViewerComparator) has no effect
|
Version: 3.2.0 Build id: I20060428-1315 Setting a Comparator in setComparator is actually not triggering any sorting in my viewer. It works when I call setComparator(ViewerSorter). Any ideas? Ben
|
2006-04-29 05:10:50
| 1,146,300,000
|
verified fixed
|
d65c8bc
| 1,146,600,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractListViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractTreeViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewer.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/AllTests.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ComparatorModelChange.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/IComparatorModelListener.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ListViewerComparatorTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/SimpleVirtualLazyTreeViewerTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/TableViewerComparatorTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/TreeViewerComparatorTest.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/jface/tests/viewers/ViewerComparatorTest.java
|
Eclipse_Platform_UI
|
3,819
| 139,067
|
Bug 139067 [IDE] Compile errors against Foundation 1.0: org.eclipse.ui.workbench
|
n0426 When compiling the org.eclipse.ui.workbench project against Foundation 1.0 class libraries we get the following compile errors due to use of JDK 1.4 APIs. There is also use of java.util.regrex classes. If this is appropriate, then the code which calls this should be guarded against running when the package is not available. The method valueOf(String) in the type Boolean is not applicable for the arguments (boolean) org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus MenuElement.java line 305 The method valueOf(String) in the type Boolean is not applicable for the arguments (boolean) org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus MenuElement.java line 305 The method valueOf(String) in the type Boolean is not applicable for the arguments (boolean) org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus SActionSet.java line 235 The method valueOf(String) in the type Boolean is not applicable for the arguments (boolean) org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus SActionSet.java line 235 The method valueOf(String) in the type Boolean is not applicable for the arguments (boolean) org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus SActionSet.java line 312 The method valueOf(String) in the type Boolean is not applicable for the arguments (boolean) org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus SActionSet.java line 312 The method valueOf(String) in the type Boolean is not applicable for the arguments (boolean) org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus SGroup.java line 152 The method valueOf(String) in the type Boolean is not applicable for the arguments (boolean) org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus SGroup.java line 153 ------------------------------------------------------------- There are also several errors where method references and/or field access needs to be fully qualified to remove ambiguity. The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 213 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 214 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 215 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 216 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 219 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 379 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 380 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 382 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 382 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 383 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 384 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 387 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 490 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 491 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 492 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 492 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 493 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 494 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 497 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 648 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 649 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 650 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 650 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 651 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 652 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 655 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 747 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 748 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 749 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 750 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 753 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 837 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 838 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 839 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 839 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 840 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 841 The field hashCode is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal ActionExpression.java line 844 The field workbench is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs ExportWizard.java line 49 The method getPresentation is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal FastViewPane.java line 98 The method getPresentation is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal FastViewPane.java line 103 The method getPresentation is defined in an inherited type and an enclosing scope org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal FastViewPane.java line 147
|
2006-04-27 16:53:06
| 1,146,170,000
|
verified fixed
|
fbfdc1c
| 1,146,580,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ActionExpression.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/FastViewPane.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/ExportWizard.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/MenuElement.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/SActionSet.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/menus/SGroup.java
|
Eclipse_Platform_UI
|
3,820
| 139,176
|
Bug 139176 Javadoc problems in ExternalActionManager
|
Build id: I20060427-0800 I was looking at the generated javadoc for ExternalActionManager. The class javadoc has this line, which should be removed: * This API is still under flux, and is expected to change in 3.1. The javadoc for ExternalActionManager.CommandCallback.isActive(String) just says: * Calling this method with an undefined command id will generate a log message.
|
2006-04-28 10:34:03
| 1,146,230,000
|
verified fixed
|
ad3437d
| 1,146,490,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/action/ExternalActionManager.java
|
Eclipse_Platform_UI
|
3,821
| 139,483
|
Bug 139483 IDEIdleHelper should be a system job
|
RC2 The IDEIdleHelper is not a system job so you periodically get a "Collecting garbage" job showing up in the ProgressView.
|
2006-05-01 08:27:01
| 1,146,490,000
|
verified fixed
|
0790e75
| 1,146,490,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEIdleHelper.java
|
Eclipse_Platform_UI
|
3,822
| 138,785
|
Bug 138785 [Workbench] ArrayIndexOutOfBounds in WorkbenchPage.ActivationList#bringToTop
|
I got this AIOOBE when running the UI test suites against HEAD. The problem is in this line: int newIndex = lastIndexOfContainer(targetContainer); if (ref == parts.get(newIndex)) { The method lastIndexOfContainer can return -1, in which case you'll get the AIIOBE on the next line. java.lang.ArrayIndexOutOfBoundsException at java.util.ArrayList.get(ArrayList.java:358) at org.eclipse.ui.internal.WorkbenchPage$ActivationList.bringToTop(WorkbenchPage.java:3814) at org.eclipse.ui.internal.WorkbenchPage.updateVisibility(WorkbenchPage.java:3300) at org.eclipse.ui.internal.WorkbenchPage.setPerspective(WorkbenchPage.java:3222) at org.eclipse.ui.internal.WorkbenchPage.busySetPerspective(WorkbenchPage.java:957) at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:941) at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:3340) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPage.setPerspective(WorkbenchPage.java:3338) at org.eclipse.ui.tests.api.IWorkbenchPageTest.testBug76285(IWorkbenchPageTest.java:2005) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) 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:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:481) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:347) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:57) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:105) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.pde.internal.junit.runtime.UITestApplication.run(UITestApplication.java:45) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-04-26 18:38:26
| 1,146,090,000
|
verified fixed
|
4f12eef
| 1,146,150,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchPage.java
|
Eclipse_Platform_UI
|
3,823
| 138,404
|
Bug 138404 [Problems] quick fix wizard opened with no options
| null |
2006-04-25 11:36:40
| 1,145,980,000
|
verified fixed
|
da900e1
| 1,146,150,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/ActionResolveMarker.java
|
Eclipse_Platform_UI
|
3,824
| 138,824
|
Bug 138824 [CommonNavigator] Remove obsolete API
| null |
2006-04-26 23:59:50
| 1,146,110,000
|
verified fixed
|
b324196
| 1,146,150,000
|
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorSaveablesService.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/SaveablesSourceHelper.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/extensions/NavigatorSaveablesProviderFactoryManager.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/INavigatorSaveablesService.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/ISaveablesSourceHelper.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/SaveablesProvider.java bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/SaveablesProviderFactory.java
|
Eclipse_Platform_UI
|
3,825
| 138,695
|
Bug 138695 [Jobs] UI jobs with "serial" scheduling rule creates many threads
|
N20060426-0010 The debugger attempts to minimize thread creation by serializing jobs via scheduling rules, for jobs run within a viewer, etc. It seems that UI jobs with the scheduling rule cause many threads to be created, whereas non-UI jobs with the same rule do not. Example code will be attached - sample plug-in with a view and actions. * "Action 1" in the context menu of the "Sample view" schedules 400 UI jobs with the scheduling rule, and eventually creates 100's of threads * "Action 2" creates 400 non-ui jobs with the same/similar rule, but only ends up creating about 20 worker threads The "serial" rule looks like this: public class SerialPerObjectRule implements ISchedulingRule { private Object fObject = null; public SerialPerObjectRule(Object lock) { fObject = lock; } /* (non-Javadoc) * @see org.eclipse.core.runtime.jobs.ISchedulingRule#contains(org.eclipse.core.runtime.jobs.ISchedulingRule) */ public boolean contains(ISchedulingRule rule) { return rule == this; } /* (non-Javadoc) * @see org.eclipse.core.runtime.jobs.ISchedulingRule#isConflicting(org.eclipse.core.runtime.jobs.ISchedulingRule) */ public boolean isConflicting(ISchedulingRule rule) { if (rule instanceof SerialPerObjectRule) { SerialPerObjectRule vup = (SerialPerObjectRule) rule; return fObject == vup.fObject; } return false; } }
|
2006-04-26 14:02:39
| 1,146,070,000
|
resolved fixed
|
2994bab
| 1,146,090,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/TestBug138695.java
|
Eclipse_Platform_UI
|
3,826
| 97,565
|
Bug 97565 [KeyBindings] preference page: AIOOBE trying to change key bindings
|
Steps to reproduce: 1) Go to General>Keys>Modify 2) Select Refactoring - Java for the category 3) Select "Move Member Type to New File" for the name 4) In the key sequence, select Tab 5) Type Ctrl + Shift + N 6) Change the name by selecting "Backspace" instead of Tab. 7) You should get the exception java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Native Method) at org.eclipse.jface.bindings.keys.KeySequenceText.insertStrokeAt(KeySequenceText.java:754) at org.eclipse.jface.bindings.keys.KeySequenceText.insert(KeySequenceText.java:719) at org.eclipse.ui.internal.keys.KeysPreferencePage$8.widgetSelected(KeysPreferencePage.java:778) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:844) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2929) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2562) at org.eclipse.jface.window.Window.runEventLoop(Window.java:809) at org.eclipse.jface.window.Window.open(Window.java:787) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:66) at org.eclipse.jface.action.Action.runWithEvent(Action.java:996) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:844) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2929) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2562) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1694) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1658) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:366) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:375) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:162) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948)
|
2005-05-31 12:21:57
| 1,117,560,000
|
verified fixed
|
d4aa612
| 1,146,080,000
|
bundles/org.eclipse.jface/src/org/eclipse/jface/bindings/keys/KeySequenceText.java
|
Eclipse_Platform_UI
|
3,827
| 138,400
|
Bug 138400 [Workbench] Problem deleting a perspective descriptor created from restore state
|
I am running into an issue with perspectives within our product. The issue is that the perspectives are created "dynamically", meaning that an xml file is used to describe layout. The xml is parsed and associated with a perspective id, the perspectivefactory code then has a mthod call which builds the layout based on the xml. All fine and good. Works great. The issue is that whnever the xml file is changed, I need to be able to have the perspective rebuild itself to reflect the new layout in the xml. This always works as long as perspective states are not saved. However, we must support perspective states to be saved. So the issue is occuring in the use case where I start the client, the perspective is created, shown etc. Then I make a change to the xml file without changing the active perspective. The client is shut down, then restarts and reloads the new changed xml. However, instead of my perspective updating, it is the perspective that was saved in the perspective state. Calling reset perspective doesn't do anything. It is also important to note that the perspective is created using the new addContribution method. So the extension is created every time the client starts up since these "dynamic extensions" are currently not persisted. After debugging extensively, I noticed that it is using the custom definition which is saved in the workbench preferences. So my initial thought was to delete the custom definition and see what happens. I tried that, and what happens now is I get an error trying to open the perspective. The code path goes fine until it gets here: IPerspectiveFactory factory = null; try { factory = persp.createFactory(); } catch (CoreException e) { throw new WorkbenchException(NLS.bind(WorkbenchMessages.Perspective_unableToLoad, persp.getId() )); } createFactory is always returning null. I think this is because the perspective descriptor being used here is the perspective descriptor created from the custom definition, so the descriptor does not have the configElement reference. // otherwise try to create the executable extension if (configElement != null) try { return (IPerspectiveFactory) configElement .createExecutableExtension(IWorkbenchRegistryConstants.ATT_CLASS); } catch (CoreException e) { // do nothing } return null; The workaround I have found that works is if I change the isPreDefined method in the PerspectiveDescriptor class to the followng: public boolean isPredefined() { return (getClassName() != null && configElement != null); } I'm not sure if this is the proper way to handle this. When would a saved persepective have a config element when it is restored? It always has a class name because the class name is saved in the xml that gets written to the preferences file.
|
2006-04-25 11:23:37
| 1,145,980,000
|
verified fixed
|
78fbd41
| 1,146,070,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/registry/PerspectiveDescriptor.java
|
Eclipse_Platform_UI
|
3,828
| 132,550
|
Bug 132550 [FastViews] BIDI:Fast Views become hidden when selected
|
Scenario: 1. Launch eclipse using -rtl attribute 2. Create a java file and java class and made some syntax error in purpose and save it. 3. Now select Window->Show view->problems Result: The problems view is displayed on the right side of workbench (on the navigator view). When trying to select some problem or to broaden the view width, the view is become hidden. Note: This bug occurs only in RTL orientation.
|
2006-03-20 10:40:15
| 1,142,870,000
|
closed fixed
|
7b92e63
| 1,146,070,000
|
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/FastViewPane.java
|
Eclipse_Platform_UI
|
3,829
| 138,645
|
Bug 138645 QuickFix dialog has no wizard graphic or menu icon
|
20060425 We need a wizard graphic and a menu icon for Quick fix
|
2006-04-26 10:51:15
| 1,146,060,000
|
verified fixed
|
7d6fbe8
| 1,146,070,000
|
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEInternalWorkbenchImages.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchAdvisor.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/ActionResolveMarker.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/views/markers/internal/MarkerResolutionDialog.java
|
Eclipse_Platform_UI
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.