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 |
|---|---|---|---|---|---|---|---|---|---|---|
461 | 333,893 |
Bug 333893 Shell with SWT.SHEET style doesn't take focus any more
| null |
2011-01-10 13:12:29
| 1,294,680,000 |
resolved fixed
|
7c365a9
| 1,294,690,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
462 | 331,310 |
Bug 331310 swtlib-64 is created and left behind in tmp directory in world writable mode (chmod 777). This is a security issue.
|
Build Identifier: SWT 3.5.0.v3550b Using Eclipse Memory Analyzer 1.0.1 I noticed that SWT is leaving behind temporary data in /tmp, namely the directory /tmp/swtlib-64 in our case. This directory is world writable and reported as security issue by our systems. The problematic code line is Runtime.getRuntime ().exec (new String []{"chmod", "777", path}).waitFor(); //$NON-NLS-1$ //$NON-NLS-2$ in org.eclipse.swt.internal.Library It is not trivial to resolve as the current approach assumes that the swtlib can be shared system wide (hence world writable flag is necessary). However, this assumption is challenged on security sensitive systems with multiple users. Code could be injected into the SWT libraries and would be executed with the rights of the user running any Eclipse product on the same system. Reproducible: Always Steps to Reproduce: 1. Check /tmp and remove potentially existing directory swtlib-64: txruf@passent1:/tmp/ [] ls swtlib-64 /bin/ls: swtlib-64: No such file or directory 2. Run an Eclipse product - e.g. Eclipse Memory Analyzer. 3. Check /tmp, it will contain swtlib-64 with world writable flag set: txruf@passent1:/tmp/ [] ll swtlib-64 total 196 drwxrwxrwx 2 txruf txruf 80 2010-11-29 10:47 . drwxrwxrwt 22 root root 700 2010-11-29 10:47 .. -rwxr-xr-x 1 txruf txruf 89120 2010-11-29 10:47 libswt-mozilla-gcc3-gtk-3550.so -rwxr-xr-x 1 txruf txruf 93192 2010-11-29 10:47 libswt-mozilla-gtk-3550.so 4. Different user replaces original library with modified version: tpdev@svwdpass16:/tmp/swtlib-64/ [rdbms10204] mv libswt-mozilla-gcc3-gtk-3550.so libswt-mozilla-gcc3-gtk-3550.so.original tpdev@svwdpass16:/tmp/swtlib-64/ [rdbms10204] touch libswt-mozilla-gcc3-gtk-3550.so tpdev@svwdpass16:/tmp/swtlib-64/ [rdbms10204] ll total 196 drwxrwxrwx 2 txruf txruf 100 2010-11-29 10:48 . drwxrwxrwt 22 root root 700 2010-11-29 10:48 .. -rw-r--r-- 1 tpdev tpdev 0 2010-11-29 10:48 libswt-mozilla-gcc3-gtk-3550.so -rwxr-xr-x 1 txruf txruf 89120 2010-11-29 10:47 libswt-mozilla-gcc3-gtk-3550.so.original -rwxr-xr-x 1 txruf txruf 93192 2010-11-29 10:47 libswt-mozilla-gtk-3550.so
|
2010-11-29 05:00:05
| 1,291,020,000 |
resolved fixed
|
0656dc6
| 1,294,440,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/common_j2se/org/eclipse/swt/internal/Library.java
|
SWT
|
463 | 333,500 |
Bug 333500 SWT Text control with SWT.MULTI style appears incorrectly when disabled
|
Build Identifier: 3.6 Helios Release Using Cocoa ws. The multiline text control appears differently from the single line one, when setEnabled is set to false. The cocoa multiline text control behaves exactly the same as the single line one, ideally so should the SWT control. Reproducible: Always Steps to Reproduce: 1. Run the SWT controls examples 2. On the SWT Text example tab select SWT.SINGLE and toggle enablement 3. Select SWT.MULTI and toggle enablement
|
2011-01-04 13:13:22
| 1,294,160,000 |
resolved fixed
|
73bece2
| 1,294,270,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Text.java
|
SWT
|
464 | 333,493 |
Bug 333493 disposed widget exception when closing editor with Browser with Ctrl+F4
|
- open an .html file in eclipse's Web Browser editor - close the editor with Ctrl+F4 - the exception below occurs: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.widgets.Widget.error(Widget.java:468) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340) at org.eclipse.swt.widgets.Widget.getData(Widget.java:554) at org.eclipse.swt.ole.win32.OleFrame.getMsgProc(OleFrame.java:224) at org.eclipse.swt.internal.win32.OS.PeekMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.PeekMessage(OS.java:3024) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3652) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
|
2011-01-04 11:23:34
| 1,294,160,000 |
resolved fixed
|
4737356
| 1,294,170,000 |
bundles/org.eclipse.swt/Eclipse SWT OLE Win32/win32/org/eclipse/swt/ole/win32/OleFrame.java
|
SWT
|
465 | 333,386 |
Bug 333386 Inconsistent behavior of Combo#setItems() on MacOSX Cocoa
| null |
2011-01-02 14:20:38
| 1,294,000,000 |
resolved fixed
|
adc1c99
| 1,294,160,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Combo.java
|
SWT
|
466 | 332,389 |
Bug 332389 Invalid memory access when using the new shell.getToolBar()
|
Build Identifier: 3.7M4 import org.eclipse.swt.*; import org.eclipse.swt.layout.*; import org.eclipse.swt.widgets.*; public class Main { public static void main(String[] args) { final Display display = Display.getDefault(); final Shell shell = new Shell(display, SWT.SHELL_TRIM); final ToolBar toolBar = shell.getToolBar(); new ToolItem(toolBar, 0).setText("toolbar item"); shell.setLayout(new GridLayout()); final Label label = new Label(shell, 0); label.setText("label"); label.setLayoutData(new GridData(GridData.FILL, GridData.FILL, true, true)); shell.pack(); shell.setMinimumSize(shell.getSize()); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) { display.sleep(); } } display.dispose(); } } I'm getting the error "Invalid memory access of location 0x0 rip=0x7fff8249b979" (the numbers can be different each time) when I launch the above sample on OS X 10.6.5 using Java 1.6.0_22 and org.eclipse.swt.cocoa.macosx.x86_64_3.7.0.v3716.jar Reproducible: Always Steps to Reproduce: 1. launch above sample
|
2010-12-12 06:57:22
| 1,292,160,000 |
resolved fixed
|
bc954da
| 1,294,160,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/id.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
467 | 332,282 |
Bug 332282 The styledtext caret position is incorrect when switch Orientation
|
Build Identifier: SWT3.4.2 switch styledtext Orientation, and resize styledtext size, the caret position is incorrect. Reproducible: Always Steps to Reproduce: 1. launch my sample code 2. press CTRL+G to swith Orientation from LTR to RTL 3. resize the shell Bug: if change size smaller, the caret is lost; if change size bigger, the caret is not at line end
|
2010-12-10 03:54:08
| 1,291,970,000 |
resolved fixed
|
084cf17
| 1,293,130,000 |
bundles/org.eclipse.swt/Eclipse SWT Custom Widgets/common/org/eclipse/swt/custom/StyledText.java
|
SWT
|
468 | 333,053 |
Bug 333053 Multiple compiler warnings in I20101221-1019
|
These errors show up on multiple platforms. 1. WARNING in /temp.folder/@dot.src/org/eclipse/swt/custom/SashForm.java (at line 112) public int getOrientation() { The method SashForm.getOrientation() does not override the inherited method from Control since it is private to a different package 2. WARNING in /temp.folder/@dot.src/org/eclipse/swt/custom/SashForm.java (at line 297) public void setOrientation(int orientation) { The method SashForm.setOrientation(int) does not override the inherited method from Control since it is private to a different package 1. WARNING in /temp.folder/@dot.src/org/eclipse/swt/custom/StyledText.java (at line 4472) public int getOrientation () { The method StyledText.getOrientation() does not override the inherited method from Control since it is private to a different package 2. WARNING in /temp.folder/@dot.src/org/eclipse/swt/custom/StyledText.java (at line 9238) public void setOrientation(int orientation) { The method StyledText.setOrientation(int) does not override the inherited method from Control since it is private to a different package
|
2010-12-21 22:14:42
| 1,292,990,000 |
resolved fixed
|
45c9259
| 1,293,030,000 |
bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Combo.java bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Composite.java bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Control.java bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Text.java
|
SWT
|
469 | 333,086 |
Bug 333086 javadoc warning in N20101221-2000 wrt SWT
|
/builds/N201012212000/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.swt/Eclipse SWT/common/org/eclipse/swt/SWT.java:749: warning - Tag @see: reference not found: org.eclipse.swt.widgets.SWT#GESTURE_MAGNIFY /builds/N201012212000/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.swt/Eclipse SWT/common/org/eclipse/swt/SWT.java:749: warning - Tag @see: reference not found: org.eclipse.swt.widgets.SWT#GESTURE_PAN /builds/N201012212000/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.swt/Eclipse SWT/common/org/eclipse/swt/SWT.java:749: warning - Tag @see: reference not found: org.eclipse.swt.widgets.SWT#GESTURE_ROTATE /builds/N201012212000/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.swt/Eclipse SWT/common/org/eclipse/swt/SWT.java:749: warning - Tag @see: reference not found: org.eclipse.swt.widgets.SWT#GESTURE_SWIPE /builds/N201012212000/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.swt/Eclipse SWT/common/org/eclipse/swt/events/GestureEvent.java:51: warning - Tag @link: can't find GESTURE_NONE in org.eclipse.swt.SWT 5 warnings
|
2010-12-22 08:30:37
| 1,293,020,000 |
resolved fixed
|
11b6b18
| 1,293,030,000 |
bundles/org.eclipse.swt/Eclipse SWT/common/org/eclipse/swt/SWT.java bundles/org.eclipse.swt/Eclipse SWT/common/org/eclipse/swt/events/GestureEvent.java
|
SWT
|
470 | 332,830 |
Bug 332830 Menu item text cropped
|
Build Identifier: M20100909-0800 Menu item text is cropped by keyboard shortcut when switched to windows classic theme. Its described as bug in windows and workaround is in source of org.eclipse.swt.widgets.Menu on line 1508, but does not work. Reproducible: Always Steps to Reproduce: 1. switch Windows 7 to widows classic theme 2. create menu with two items 3. first item has icon and AS_CHECKBOX style 4. second item has key shortcut and a longer text 5. second item text renders cropped
|
2010-12-17 04:55:41
| 1,292,580,000 |
resolved fixed
|
1641f76
| 1,292,960,000 |
bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/MenuItem.java
|
SWT
|
471 | 332,917 |
Bug 332917 XULRunner path may not work for SWT browser
|
Build Identifier: 3.4.2 If add -Dorg.eclipse.swt.browser.XULRunnerPath=${rcp.home}/rcp/eclipse/plugins/xulrunner in rcpinstall.properties. Because of the mix use of "/" and "\" in the XULRunnerpath, SWT browser is not able to find the XULRunner runtime. A simple test would be to create SWT browser instance with SWT.MOZILLA. This will lead to an exception in XPCOM. Suggested patch provided. Propose as an enhancement request. Reproducible: Always
|
2010-12-19 21:39:26
| 1,292,810,000 |
resolved fixed
|
443e45c
| 1,292,870,000 |
bundles/org.eclipse.swt/Eclipse SWT Mozilla/common/org/eclipse/swt/browser/Mozilla.java
|
SWT
|
472 | 332,887 |
Bug 332887 SWT Snippets use incorrect positioning
|
Quoting from Steve Northover's SWT book, section 4.2: "Very often, the location of the client area within the control is (0, 0), but this is not always the case. Figure 4.3 shows the client area of two group boxes from different platforms, with Windows on the left and GTK on the right. On Windows, the location of the client area is (3, 13). On GTK, it is (0, 0)". Therefore, portable SWT code should never position widgets relative to (0, 0) but relative to the parent's client area. While on most platforms, the assumption is true, it is not in Eclipse RAP. Unfortunately, a couple of the official SWT snippets show this bad practice, which causes incorrect layouting in RAP. An example is Snippet40: Shell shell = new Shell (display); Composite c1 = new Composite (shell, SWT.BORDER); c1.setSize (100, 100); Composite c2 = new Composite (shell, SWT.BORDER); c2.setBounds (100, 0, 100, 100); To be fully portable, this code should be rewritten to: Shell shell = new Shell (display); Rectangle clientArea = shell.getClientArea(); Composite c1 = new Composite (shell, SWT.BORDER); c1.setBounds (clientArea.x, clientArea.y, 100, 100); Composite c2 = new Composite (shell, SWT.BORDER); c2.setBounds (clientArea.x + 100, clientArea.y, 100, 100);
|
2010-12-18 05:51:59
| 1,292,670,000 |
resolved fixed
|
e016ba8
| 1,292,860,000 |
examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet40.java
|
SWT
|
473 | 332,709 |
Bug 332709 Use JNI add an window callback function to Shell, function can not be called.
|
Build Identifier: IES 3.6.1Carbon Version:3.6.1 Build id:M20100909-0800 For some reason,We had added an window callback function to Shell.We had implemented this by jni native c code.We passed Shell.handle to the jni functions and call carbon api HMInstallWindowContentCallback to add an callback function.In swt 3.5.2,the window callback works correctly but in 3.6.1, it won't be called. Reproducible: Always Steps to Reproduce: 1.New an Shell. 2.Use carbon api HMInstallWindowContentCallback to add a window callback function to the Shell. 3.The window callback function won't be called in carbon 3.6.1
|
2010-12-16 04:41:36
| 1,292,490,000 |
resolved fixed
|
588bdb7
| 1,292,860,000 |
bundles/org.eclipse.swt/Eclipse SWT/carbon/org/eclipse/swt/widgets/Control.java bundles/org.eclipse.swt/Eclipse SWT/carbon/org/eclipse/swt/widgets/Display.java
|
SWT
|
474 | 332,872 |
Bug 332872 Consistently resolve XOR-mode-painting related issues on MacOSX Carbon and Cocoa
|
XOR-painting mode is used in various places within GEF to show feedback (drag feedback, marquee selection feedback, guide snap feedback, etc.). As this functionality is not supported on MacOSX Carbon (GC#setXORMode() has been deprecated because of this) and as it does not seem to work "as expected" on MacOSX Cocoa (while I could not find any official information that it is not supported there), there are (and have been) quite a few bugzillas related to this. While for some of these workarounds have already been committed, there does not seem to be a consistent policy on how to deal with these issues in general.
|
2010-12-17 14:14:11
| 1,292,610,000 |
resolved fixed
|
7a19d8d
| 1,292,630,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/GC.java
|
SWT
|
475 | 210,451 |
Bug 210451 [GTK/Linux] Validation error dialog from launch configuration cannot be clicked on
|
Build ID: I20071120-0800 1. Open an 'Eclipse Application' launch configuration. 2. Unselect some plug-ins that are needed to launch what you are going to launch. 3. Click on 'Validate Plug-ins'. 4. Notice that the popped up dialog will not capture mouse click events. You cannot expand the tree, you cannot click the 'OK' button. 5. To get rid of it, you need to alt+tab to the 'Run' dialog, then press the ESC key to close them. This is on Linux/GTK+. I am on Gentoo Linux running gtk+ version 2.10.14. I cannot reproduce this on 3.3.1.1. Benny has reproduced this on 1108's N build but could not reproduce it on 1018's or 1024's.
|
2007-11-20 16:31:31
| 1,195,590,000 |
resolved fixed
|
d8c7ac1
| 1,292,600,000 |
bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Shell.java
|
SWT
|
476 | 332,599 |
Bug 332599 Inconsistent behavior when dragging and releasing mouse outside Canvas on MacOSX Cocoa
| null |
2010-12-15 02:42:04
| 1,292,400,000 |
resolved fixed
|
5d86edc
| 1,292,540,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Control.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java
|
SWT
|
477 | 332,700 |
Bug 332700 org.eclipse.swt.browser.IE.createSafeArray() does not work for cross process
|
Build Identifier: SWT 3.6.1 Due to a wrong flag in safeArrary was set, the safeArrary is not passed cross process successfully. safeArray.fFeatures = OS.FADF_FIXEDSIZE | OS.FADF_HAVEVARTYPE Actually the safeArray contain VT_UI1 but not VT_VARIANT, so the flag OS.FADF_HAVEVARTYPE should not be set up. Without the flag, the function work well for in-process and out-of-process COM communication. Reproducible: Always Steps to Reproduce: Run Snippet330 with SWT IE browser (in-process), and IBM XPD browser (support both in-process and out-of-process)
|
2010-12-15 22:50:07
| 1,292,470,000 |
resolved fixed
|
3a85f1d
| 1,292,520,000 |
bundles/org.eclipse.swt/Eclipse SWT Browser/win32/org/eclipse/swt/browser/IE.java
|
SWT
|
478 | 332,600 |
Bug 332600 [Mac][Combo]Combo Box Cursor Position is different in different platforms
|
Build Identifier: 3.6.2 1.Run ComboSample in atttachment: final Combo combo = new Combo(shell, SWT.DROP_DOWN | SWT.LEFT_TO_RIGHT); combo.setText("ABCDEFG....................................................."); Result: On Windows, the cursor is at the beginning of the text, which is the expected behavior. But on Mac OS X, the cursor is at the end of the text, it will be hard for use to read the string. See screenshot in attachment. Reproducible: Always
|
2010-12-15 02:52:33
| 1,292,400,000 |
resolved fixed
|
6b71adb
| 1,292,450,000 |
bundles/org.eclipse.swt/Eclipse SWT/carbon/org/eclipse/swt/widgets/Combo.java
|
SWT
|
479 | 332,003 |
Bug 332003 dropdown calendar of datetime widget doesn't hide
|
Build: Build id: I20101206-1800 Steps to reproduce: 1) Run the ControlExample 2) In the DateTime tab set the style to SWT.DATE and SWT.DROP_DOWN 3) Open the dropdown calendar 4) Switch to another application like firefox, textedit The dropdown calendar is still visible on top of the other application. Expected : the calendar should be hidden when we switch to another application. A related issue: The DateTime widget should get focus when we click on the dropdown button. Because this doesn't happen, the focus is on a different control and we can traverse between different controls while the dropdown calendar is still visible.
|
2010-12-07 06:49:11
| 1,291,720,000 |
resolved fixed
|
f215413
| 1,292,290,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/DateTime.java
|
SWT
|
480 | 332,083 |
Bug 332083 Invalid MouseHover event on MacOSX Cocoa
| null |
2010-12-07 15:21:53
| 1,291,750,000 |
resolved fixed
|
fc2ff70
| 1,292,290,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java
|
SWT
|
481 | 331,993 |
Bug 331993 Display#setCursorLocation(Point) does not cause MouseMove event on MacOSX Cocoa
| null |
2010-12-07 04:50:22
| 1,291,720,000 |
resolved fixed
|
1623cfc
| 1,292,290,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java
|
SWT
|
482 | 330,757 |
Bug 330757 Command+C (copy) in Browser (WebKit) beeps
|
HEAD Cocoa Command+C (copy) in the Browser widget beeps. Copying actually does work, but the beep already made me look for a workaround to get hold of that text...
|
2010-11-21 14:57:07
| 1,290,370,000 |
resolved fixed
|
fdd79a0
| 1,291,670,000 |
bundles/org.eclipse.swt/Eclipse SWT WebKit/cocoa/org/eclipse/swt/browser/WebKit.java
|
SWT
|
483 | 330,540 |
Bug 330540 Shell with SWT.TOOL style doesn't take focus any more
|
I20101116-0800 Cocoa A Shell with SWT.TOOL style doesn't take focus any more. This can be seen in the ControlExample and in the Key Assist dialog (Command+Shift+L).
|
2010-11-18 03:44:27
| 1,290,070,000 |
resolved fixed
|
61c261f
| 1,291,670,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
484 | 331,474 |
Bug 331474 Shell.getSize() returns incorrect height for SHEET | RESIZE style
|
Build Identifier: 3.7m3 Mac OSX 10.6.6, Cocoa 32 bit: Run example code below: Shell.getSize() should return a point with y = 300, but it is 278. This problem only occurs when both SHEET and RESIZE style is set. Reproducible: Always Steps to Reproduce: import org.eclipse.swt.SWT; import org.eclipse.swt.layout.FillLayout; import org.eclipse.swt.widgets.Button; import org.eclipse.swt.widgets.Display; import org.eclipse.swt.widgets.Event; import org.eclipse.swt.widgets.Listener; import org.eclipse.swt.widgets.Shell; public class TestSheetSize { public static void main(String[] args) { final Display display = new Display(); final Shell shell = new Shell(display); FillLayout layout = new FillLayout(); layout.marginWidth = 150; layout.marginHeight = 150; shell.setLayout(layout); Button button = new Button(shell, SWT.PUSH); button.setText("Push Me"); button.addListener(SWT.Selection, new Listener() { public void handleEvent(Event event) { final Shell popup = new Shell(shell, SWT.SHEET | SWT.RESIZE); popup.setSize(300, 300); display.asyncExec(new Runnable() { public void run() { System.out.println("Size = " + popup.getSize()); } }); popup.open(); } }); shell.pack(); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) display.sleep(); } display.dispose(); } }
|
2010-11-30 15:59:01
| 1,291,150,000 |
resolved fixed
|
3895288
| 1,291,660,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
485 | 331,453 |
Bug 331453 unicode nonprintable / zero width space completely bricks editors
|
Build Identifier: M20100909-0800 Eclipse is completely bricked (rendering artifacts and/or hang and many errors in error log) by pasting the unicode character U+200B (zero width space) in a Java editor. I will attach the stacktrace of the exception that is repeatedly put in the error log right after pasting this character in an Eclipse Java editor. Curiously, with a plain text file only the exception is spammed in the error log, but Eclipse seems to continue running normally. Major problems occur in the Java editor (and other language-specific editors). Reproducible: Always Steps to Reproduce: 1. Open eclipse & open a Java file 2. Paste the unicode character U+200B (zero width space) in the editor. Assuming bugzilla and the webserver support unicode properly I have included this invisible characters between the two x's: x​x 3. Observe that the error log is spammed full of ArrayIndexOutOfBoundsException; rendering of the editor window breaks and often (when pasting multiple times) rendering of other parts of Eclipse break too and/or it hangs indefinitely.
|
2010-11-30 11:35:57
| 1,291,130,000 |
resolved fixed
|
15691b2
| 1,291,650,000 |
bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/graphics/TextLayout.java
|
SWT
|
486 | 331,698 |
Bug 331698 Focus not restored properly when breadcrumb bar is used
| null |
2010-12-02 12:08:08
| 1,291,310,000 |
resolved fixed
|
e581061
| 1,291,320,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Control.java
|
SWT
|
487 | 331,676 |
Bug 331676 Test failures on Cocoa in N20101201-2000
| null |
2010-12-02 09:55:14
| 1,291,300,000 |
resolved fixed
|
3381200
| 1,291,310,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSWindow.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
488 | 327,560 |
Bug 327560 Failed to create Citrix Client v12
| null |
2010-10-12 10:23:59
| 1,286,890,000 |
resolved fixed
|
e256b8b
| 1,290,700,000 |
bundles/org.eclipse.swt/Eclipse SWT OLE Win32/win32/org/eclipse/swt/ole/win32/OleClientSite.java bundles/org.eclipse.swt/Eclipse SWT OLE Win32/win32/org/eclipse/swt/ole/win32/OleControlSite.java
|
SWT
|
489 | 319,893 |
Bug 319893 Shell's with SWT.NO_TRIM not minimized on Windows+M keystroke
| null |
2010-07-14 14:23:42
| 1,279,130,000 |
resolved fixed
|
c29adbe
| 1,290,200,000 |
bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Decorations.java
|
SWT
|
490 | 307,345 |
Bug 307345 [Browser][Mozilla][Mac]Can't use ctrl+f2 to move focus to the menu bar in Mozilla browser
| null |
2010-03-29 03:25:40
| 1,269,850,000 |
resolved fixed
|
05a8cbb
| 1,290,100,000 |
bundles/org.eclipse.swt/Eclipse SWT Mozilla/carbon/org/eclipse/swt/browser/MozillaDelegate.java bundles/org.eclipse.swt/Eclipse SWT PI/carbon/org/eclipse/swt/internal/carbon/OS.java
|
SWT
|
491 | 330,299 |
Bug 330299 Tree default selection event doesn't have item field set
|
Build Identifier: 3.7m3 Run example snippet below, select a tree item and press Enter - the 'item' field of the Event object is null. Reproducible: Always Steps to Reproduce: import org.eclipse.swt.SWT; import org.eclipse.swt.events.SelectionEvent; import org.eclipse.swt.events.SelectionListener; import org.eclipse.swt.layout.FillLayout; import org.eclipse.swt.widgets.Display; import org.eclipse.swt.widgets.Shell; import org.eclipse.swt.widgets.Tree; import org.eclipse.swt.widgets.TreeItem; public class TestTreeDefaultSelection { public static void main(String[] args) { Display display = new Display(); Shell shell = new Shell(display); shell.setLayout(new FillLayout()); final Tree tree = new Tree(shell, SWT.BORDER); for (int i = 0; i < 4; i++) { TreeItem iItem = new TreeItem(tree, 0); iItem.setText("TreeItem (0) -" + i); for (int j = 0; j < 4; j++) { TreeItem jItem = new TreeItem(iItem, 0); jItem.setText("TreeItem (1) -" + j); for (int k = 0; k < 4; k++) { TreeItem kItem = new TreeItem(jItem, 0); kItem.setText("TreeItem (2) -" + k); } } } tree.addSelectionListener(new SelectionListener() { public void widgetDefaultSelected(SelectionEvent e) { System.out.println("Item Default: " + e.item); } public void widgetSelected(SelectionEvent e) { System.out.println("Item Selected: " + e.item); } }); shell.setSize(200, 200); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) display.sleep(); } display.dispose(); } }
|
2010-11-15 18:01:48
| 1,289,860,000 |
resolved fixed
|
41f1797
| 1,289,930,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Table.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Tree.java
|
SWT
|
492 | 329,058 |
Bug 329058 BrowserFunction should map java null to JS null, not to undefined
| null |
2010-10-29 11:45:48
| 1,288,370,000 |
resolved fixed
|
07b4e14
| 1,289,860,000 |
bundles/org.eclipse.swt/Eclipse SWT Browser/common/org/eclipse/swt/browser/BrowserFunction.java bundles/org.eclipse.swt/Eclipse SWT Browser/win32/org/eclipse/swt/browser/WebSite.java bundles/org.eclipse.swt/Eclipse SWT Mozilla/common/org/eclipse/swt/browser/External.java bundles/org.eclipse.swt/Eclipse SWT OLE Win32/win32/org/eclipse/swt/ole/win32/Variant.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT WebKit/cocoa/org/eclipse/swt/browser/WebKit.java
|
SWT
|
493 | 330,268 |
Bug 330268 Display.post() logs out current session if no mouse button specified only on 10.6.5(?)
|
Discovered during a JUnit test run: this piece of code event = new Event(); event.type = SWT.MouseDown; display.post(event); // missing button will kill all processes and restart the Finder on 10.6.5!
|
2010-11-15 12:22:58
| 1,289,840,000 |
resolved fixed
|
9f0ad20
| 1,289,840,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java
|
SWT
|
494 | 329,814 |
Bug 329814 Compiler warnings in N20101108-2000 build
|
1. WARNING in /temp.folder/@dot.src/org/eclipse/swt/internal/image/JPEGDecoder.java (at line 2303) int ci, access_rows; The value of the local variable access_rows is not used 2. WARNING in /temp.folder/@dot.src/org/eclipse/swt/internal/image/JPEGDecoder.java (at line 3824) int ci, block_row, block_rows, access_rows; The value of the local variable access_rows is not used 1. WARNING in /temp.folder/@dot.src/org/eclipse/swt/internal/theme/ComboDrawData.java (at line 50) int y_border = ythickness + focus_padding; The value of the local variable y_border is not used 2. WARNING in /temp.folder/@dot.src/org/eclipse/swt/internal/theme/ComboDrawData.java (at line 112) int y_border = ythickness + focus_padding; The value of the local variable y_border is not used 1. WARNING in _64/temp.folder/@dot.src/org/eclipse/swt/graphics/Cursor.java (at line 378) for (int i = 3, ap=0; i < srcData.length; i+=4, ap++) { The value of the local variable ap is not used All platforms should be validated.
|
2010-11-09 10:24:29
| 1,289,320,000 |
verified fixed
|
a6de467
| 1,289,500,000 |
bundles/org.eclipse.swt/Eclipse SWT Theme/gtk/org/eclipse/swt/internal/theme/ComboDrawData.java
|
SWT
|
495 | 329,916 |
Bug 329916 TableItem drawSelection
|
TableItem drawSelection calculates the proper starting x coord for drawing a focus rectangle but doesn't end up using the computed value.
|
2010-11-10 10:46:26
| 1,289,400,000 |
resolved fixed
|
77a383d
| 1,289,400,000 |
bundles/org.eclipse.swt/Eclipse SWT/emulated/treetable/org/eclipse/swt/widgets/TableItem.java
|
SWT
|
496 | 328,909 |
Bug 328909 Setting foreground color in EraseItem listener has no effect
|
Build Identifier: 3.7m2 See example below. The selected row should be drawn in red, but in 3.7m2 (unlike 3.6.1) the text is drawn in white, making the line appear 'blank'. Note that this bug affects the JFace features that allow the user to select a cell in the table (eg. FocusCellOwnerDrawHighlighter). Reproducible: Always Steps to Reproduce: import org.eclipse.swt.SWT; import org.eclipse.swt.graphics.Color; import org.eclipse.swt.layout.FillLayout; import org.eclipse.swt.widgets.Display; import org.eclipse.swt.widgets.Event; import org.eclipse.swt.widgets.Listener; import org.eclipse.swt.widgets.Shell; import org.eclipse.swt.widgets.Table; import org.eclipse.swt.widgets.TableColumn; import org.eclipse.swt.widgets.TableItem; public class EraseItemExample { public static void main(String[] args) { Display display = new Display(); Shell shell = new Shell(display); shell.setLayout(new FillLayout()); final Color red = display.getSystemColor(SWT.COLOR_RED); final Table table = new Table(shell, SWT.FULL_SELECTION); table.setHeaderVisible(true); new TableColumn(table, SWT.NONE).setWidth(100); new TableColumn(table, SWT.NONE).setWidth(100); new TableColumn(table, SWT.NONE).setWidth(100); for (int i = 0; i < 5; i++) { TableItem item = new TableItem(table, SWT.NONE); item.setText(0, "item " + i + " col 0"); item.setText(1, "item " + i + " col 1"); item.setText(2, "item " + i + " col 2"); } table.pack(); table.addListener(SWT.EraseItem, new Listener() { public void handleEvent(Event event) { if ((event.detail & SWT.SELECTED) != 0) { event.gc.setForeground(red); event.detail &= ~SWT.SELECTED; } } }); shell.setSize(400, 300); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) display.sleep(); } display.dispose(); } }
|
2010-10-28 04:14:17
| 1,288,250,000 |
resolved fixed
|
97de0fe
| 1,289,290,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Table.java
|
SWT
|
497 | 324,102 |
Bug 324102 Backspace key, delete key and tab stop working when my application is minimized
|
I have a swt form. I a swt browser control displaying a silverlight application. I have focus in a textbox. I minimize the swt form. I maximize the swt form. My textbox in the silverlight application still has focus. I can type letters. Backspace no longer works. I hit delete and focus is set to a tabstrip control on my swt form instead of the next textbox. Please feel free to contact us with what additional information is needed.
|
2010-08-31 11:24:23
| 1,283,270,000 |
resolved fixed
|
d093cc6
| 1,289,250,000 |
bundles/org.eclipse.swt/Eclipse SWT OLE Win32/win32/org/eclipse/swt/ole/win32/OleControlSite.java
|
SWT
|
498 | 322,525 |
Bug 322525 computeSize() wrong for DateTime with SWT.DATE style (Hebrew calendar)
|
1) Change the locale to Hebrew on Windows 7 (or Vista) and change to calendar type to Hebrew. 2) Run the ControlExample, select the DateTime tab and check the SWT.DATE style. Note that the preferred size of the widget is wrong.
|
2010-08-12 09:17:34
| 1,281,620,000 |
resolved fixed
|
14c0e18
| 1,289,250,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/win32/org/eclipse/swt/internal/win32/OS.java bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/DateTime.java
|
SWT
|
499 | 327,332 |
Bug 327332 Tree should not show hand pointer by default on Windows 7
| null |
2010-10-08 09:14:11
| 1,286,540,000 |
resolved fixed
|
466951f
| 1,289,240,000 |
bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Tree.java
|
SWT
|
500 | 329,576 |
Bug 329576 Toolbar buttons highlight background on Cocoa
|
In 3.x and 4.1, pressing a toolbar button on Cocoa will cause the button image to darken and the entire button to highlight which is rather jarring. This should be changed to only have the image on the button darken.
|
2010-11-05 14:18:23
| 1,288,980,000 |
resolved fixed
|
95bda0d
| 1,288,990,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/ToolItem.java
|
SWT
|
501 | 227,638 |
Bug 227638 Tree with SWT.VIRTUAL not working
|
The WPF TreeView widget does not virutalize its items like ListView can/does. We use OnRender to send our SetData event that tells the user to populate the SWT TreeItem or TableItem. Because WPF TreeView widget does not use a virtualized panel to layout it's children, all of the the children are rendered at the same time, regardless of whether they are visible or not.
|
2008-04-17 15:51:09
| 1,208,460,000 |
resolved wontfix
|
e72e908
| 1,288,720,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSDatePicker.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/DateTime.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
502 | 328,654 |
Bug 328654 HTMLTransfer broken from Firefox --> SWT [Carbon]
| null |
2010-10-25 16:35:19
| 1,288,040,000 |
resolved fixed
|
1d84e95
| 1,288,630,000 |
bundles/org.eclipse.swt/Eclipse SWT Drag and Drop/carbon/org/eclipse/swt/dnd/HTMLTransfer.java
|
SWT
|
503 | 329,181 |
Bug 329181 Shell with RESIZE and SHEET style does not pack properly
|
Build Identifier: 3.7m2 On Mac (cocoa) if the shell includes both the SWT.RESIZE and SWT.SHEET styles then calling pack() will leave the window too short. If either of these styles is excluded then pack works correctly. See example below. Reproducible: Always Steps to Reproduce: import org.eclipse.swt.SWT; import org.eclipse.swt.layout.FillLayout; import org.eclipse.swt.layout.GridLayout; import org.eclipse.swt.widgets.Button; import org.eclipse.swt.widgets.Display; import org.eclipse.swt.widgets.Event; import org.eclipse.swt.widgets.Listener; import org.eclipse.swt.widgets.Shell; public class TestSheet { public static void main(String[] args) { final Display display = new Display(); final Shell shell = new Shell(display); FillLayout layout = new FillLayout(); layout.marginWidth = 50; layout.marginHeight = 50; shell.setLayout(layout); Button button = new Button(shell, SWT.PUSH); button.setText("Push Me"); button.addListener(SWT.Selection, new Listener() { public void handleEvent(Event event) { Shell popup = new Shell(shell, SWT.DIALOG_TRIM | SWT.SHEET | SWT.RESIZE); popup.setLayout(new GridLayout()); for (int i = 1; i < 6; i++) { new Button(popup, SWT.PUSH).setText("Button " + i); } popup.pack(); popup.open(); } }); shell.pack(); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) display.sleep(); } display.dispose(); } }
|
2010-11-01 06:10:16
| 1,288,610,000 |
resolved fixed
|
5c3ad82
| 1,288,630,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
504 | 328,945 |
Bug 328945 [SWT_AWT] Application freeze
| null |
2010-10-28 12:56:52
| 1,288,290,000 |
resolved fixed
|
f2838c7
| 1,288,630,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
505 | 328,864 |
Bug 328864 textcelleditor text control lost focus after setfocus on cocoa when text is empty
| null |
2010-10-27 13:27:49
| 1,288,200,000 |
resolved fixed
|
ff9455a
| 1,288,630,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSObject.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/List.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Table.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Widget.java
|
SWT
|
506 | 328,706 |
Bug 328706 Tooltip on Link shows href
| null |
2010-10-26 09:31:39
| 1,288,100,000 |
resolved fixed
|
4b69a6c
| 1,288,630,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Link.java
|
SWT
|
507 | 328,950 |
Bug 328950 SWT test failures on Windows 7
| null |
2010-10-28 13:40:45
| 1,288,290,000 |
resolved fixed
|
d3bb18f
| 1,288,620,000 |
bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/DateTime.java
|
SWT
|
508 | 328,053 |
Bug 328053 [Browser] After clicking certain links, mouse/key events are not sent anymore
|
Build Identifier: SWT N20101017-2000 When adding input events to trigger certain actions, they stop working after a link calling a JS action is clicked. This was tested with a recent nightly build and 3.6, both have the issue. I only tried with IE. For some users, this can be very problematic. Reproducible: Always Steps to Reproduce: 1. Create a Browser with mouse/key listeners. 2. invoke a link in the form <a href="javascript:void(0)"> or <a href="javascript:alert('a text')"> 3. Click/type in the browser: events are not sent anymore.
|
2010-10-18 13:03:20
| 1,287,420,000 |
resolved fixed
|
7e44ea5
| 1,288,620,000 |
bundles/org.eclipse.swt/Eclipse SWT Browser/win32/org/eclipse/swt/browser/IE.java
|
SWT
|
509 | 328,794 |
Bug 328794 Remove unused variable in 'org.eclipse.swt.examples'
|
HEAD. Remove unused variable in 'org.eclipse.swt.examples'.
|
2010-10-27 03:40:45
| 1,288,170,000 |
resolved fixed
|
211fece
| 1,288,190,000 |
examples/org.eclipse.swt.examples/src/org/eclipse/swt/examples/accessibility/CTableItem.java
|
SWT
|
510 | 328,740 |
Bug 328740 Tooltips are not visible any more on Cocoa
| null |
2010-10-26 12:46:27
| 1,288,110,000 |
verified fixed
|
0ebb8d0
| 1,288,120,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java
|
SWT
|
511 | 300,620 |
Bug 300620 Command+. does not work any more in Trees
|
Broken in I20100119-0800 and 3.5 Cocoa, works in 3.4.2 Carbon. Command+. does not work any more in Trees. I just get an OS beep, and the KeyDown event for Command+. is missing. In Eclipse, this is e.g. visible in the Search view, where Command+. should step to the next match. The reverse (Command+Shift+.) still works. In the Java Editor, Command+. still works (jumps to next annotation).
|
2010-01-24 14:47:11
| 1,264,360,000 |
resolved fixed
|
ca77f02
| 1,288,030,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSResponder.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Control.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Widget.java
|
SWT
|
512 | 150,870 |
Bug 150870 GTK+ Printer getDPI returns 72 x 72
| null |
2006-07-17 16:49:31
| 1,153,170,000 |
resolved fixed
|
cc65e22
| 1,288,030,000 |
bundles/org.eclipse.swt/Eclipse SWT Printing/gtk/org/eclipse/swt/printing/Printer.java bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/graphics/Device.java bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/graphics/Font.java bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Display.java
|
SWT
|
513 | 328,396 |
Bug 328396 MouseDown not delivered until drag started if a DragDetect listener is attached
| null |
2010-10-21 15:21:09
| 1,287,690,000 |
resolved fixed
|
fd6c96f
| 1,287,790,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Control.java
|
SWT
|
514 | 324,236 |
Bug 324236 [Browser-Mozilla] Links and JS actions opening a new window do not work
|
Build Identifier: SWT 3.7M1 When a page contains a link that uses a target="_blank" to open a new window, that link does not work. This seems to only happen with XULRunner on Mac (32 bit mode, XULRunner 1.9.2.8) Reproducible: Always Steps to Reproduce: 1. Take Snippet 270 2. Change browser styles to MOZILLA 3. Browser.setText(x) where x contains links with target="_blank"
|
2010-09-01 15:07:56
| 1,283,370,000 |
resolved fixed
|
96b5921
| 1,287,690,000 |
bundles/org.eclipse.swt/Eclipse SWT Mozilla/common/org/eclipse/swt/browser/Mozilla.java
|
SWT
|
515 | 328,290 |
Bug 328290 Need some way to intercept 'fixfocus'
| null |
2010-10-20 16:15:30
| 1,287,610,000 |
resolved fixed
|
550e8a8
| 1,287,670,000 |
bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Button.java bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Composite.java bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Control.java bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Display.java
|
SWT
|
516 | 305,672 |
Bug 305672 whole OS freezes when tree using owner draw renders BORDER_DOT rectangle around long line
|
Build Identifier: 20100218-1602 When using regular expression and a long line (> 10k) is matched the computer freezes when eclipse tries to display it in the search view. A hard restart is required. The problem is not with the long line itself but the long matched region. The OS freezes at the moment of expanding the found match - just after the search completes. I have stumbled upon the issue by searching in a project containing minified JS files. One of the files by chance matched the regular expression. This is a major issue since the user can't recover and it is not limited to eclipse only as the whole OS locks up. Tried it in Windows 2000, XP, Vista on different computers, happens even in Virtual PC. VMWare 6.5 locks as well but recovers after a couple of minutes. Reproducible: Always Steps to Reproduce: 1.Create a file containing a single long line (15K) 2.Open File Search 3.Type ".*" in "Containing text" 4.Check regular expression checkbox 5.Type the file name for filter in "File name patterns"(the long file should be first match) 5.Click search
|
2010-03-12 09:02:41
| 1,268,400,000 |
resolved fixed
|
18f5504
| 1,287,600,000 |
bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/graphics/TextLayout.java
|
SWT
|
517 | 327,362 |
Bug 327362 setUrl() call navigates to about:blank prior to real url breaks IEWebHistory
|
Build Identifier: Eclipse 3.6.1 setUrl() API navigates to about:blank first before goes to real url. This breaks WebHistory if application calls setUrl("about:blank") first follow by another call setUrl("another url"). This only failed on IE based WebBrowser. Propose fix: IE.java setUrl() Change if (_getUrl().length() == 0 ) { to if (_getUrl().length() == 0 && ABOUT_BLANK.equalsIgnoreCase(url)) { Reproducible: Always
|
2010-10-08 14:54:52
| 1,286,560,000 |
resolved fixed
|
d42dbd7
| 1,287,430,000 |
bundles/org.eclipse.swt/Eclipse SWT Browser/win32/org/eclipse/swt/browser/IE.java
|
SWT
|
518 | 327,995 |
Bug 327995 [SWT_AWT] SWT_AWT.new_Shell(display, Canvas) crashes the application with "Invalid memory access"
|
Build Identifier: SWT N20101016-2000 When a window of a web browser is opening, we create a new Swing JFrame and add a Canvas which will contain the new web browser. Calling new_Shell(xx) crashes the application. This means that all window opening causes the issue, so this impacts web browsing, HTML editors relying on popup windows, etc. Reproducible: Always Steps to Reproduce: 1. See attached test case
|
2010-10-17 14:52:50
| 1,287,340,000 |
resolved fixed
|
73d95a7
| 1,287,420,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java
|
SWT
|
519 | 326,861 |
Bug 326861 Composite#setLayoutDeferred missing a checkWidget call
|
If Composite#setLayoutDeferred is called from a non-UI thread, it does not throw a ERROR_THREAD_INVALID_ACCESS although the documentation says so. The method should include a checkWidget() call, right?
|
2010-10-03 07:13:42
| 1,286,100,000 |
resolved fixed
|
5535a72
| 1,287,420,000 |
bundles/org.eclipse.swt/Eclipse SWT/carbon/org/eclipse/swt/widgets/Composite.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Composite.java bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Composite.java bundles/org.eclipse.swt/Eclipse SWT/motif/org/eclipse/swt/widgets/Composite.java bundles/org.eclipse.swt/Eclipse SWT/photon/org/eclipse/swt/widgets/Composite.java bundles/org.eclipse.swt/Eclipse SWT/qt/org/eclipse/swt/widgets/Composite.java bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Composite.java bundles/org.eclipse.swt/Eclipse SWT/wpf/org/eclipse/swt/widgets/Composite.java
|
SWT
|
520 | 327,974 |
Bug 327974 Path.getPathData() returns points as integers and not floats
|
Build Identifier: 20100917-0705 Path.getPathData() effectively returns an array of points that are all integers. This seems strange, since it accepted a list of points specified as floats. The problem is that the list in will not match the list out so when using Draw2D ScaledGraphics to make a larger path, it applies a transform based on the scaling factor and the list and type of points provided by PathData. The problem is most evident in xy graphs (charts) where a continuous function draws a smooth curve on the screen but a jagged one on any other device, since it's losing precision in its coordinates. The solution is simple in theory. 'Fix' getPathData() to return a list of floats (or modify PathData or Path to provide an alternate access to a float-based list of plot points. I can think of no workaround. Reproducible: Always
|
2010-10-16 07:42:14
| 1,287,230,000 |
resolved fixed
|
dfec304
| 1,287,420,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/Path.java
|
SWT
|
521 | 324,254 |
Bug 324254 [Mac] E3.x's CocoaUIEnhancer and e4's CocoaUIHandler needlessly disable the Services menu
|
E3.x's CocoaUIEnhancer and e4's CocoaUIHandler (which is a lightly modified CocoaUIEnhancer) disable the MacOS X "Services" menu. It's a bit annoying when you're used to being able to invoke a service through a keyboard shortcut. I've tried running with the disabling code removed and haven't noticed any immediate issues. I'd like to make this permanent. Does anybody remember the rationale for disabling the "Services" menu?
|
2010-09-01 18:29:05
| 1,283,380,000 |
resolved fixed
|
898a0d4
| 1,287,190,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSObject.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSResponder.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Canvas.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Widget.java
|
SWT
|
522 | 326,672 |
Bug 326672 org.eclipse.swt.graphics.TextStyle.hashCode() contains "hash ^= hash;"
|
Build Identifier: M20090917-0800 TextStyle.hashCode() contains, among other lines, the following: if (underline) hash ^= hash; if (strikeout) hash ^= hash; which would set hash = 0 This may have been done on purpose Reproducible: Always Steps to Reproduce: invoke TextStyle.hashCode() for a StyleRange that has field 'underline' set
|
2010-09-30 10:17:37
| 1,285,860,000 |
resolved fixed
|
024fc94
| 1,287,000,000 |
bundles/org.eclipse.swt/Eclipse SWT/common/org/eclipse/swt/graphics/TextStyle.java
|
SWT
|
523 | 316,712 |
Bug 316712 [widgets] Clicking in empty space can cause clicks in views
|
1. Open the Java perspective, or any other perspective where there's a view on the left (e.g. Package Exlorer), and no open views to the right of it. 2. Click once within the view on the left. 3. In the empty space to the right, quickly right-click then left-click. 4. This registers as a double-click within the view on the left. The vertical position of the registered double-click will be the same as the vertical position of the mouse. -- Configuration Details -- Product: Eclipse 1.3.0.20100609-1425 (org.eclipse.epp.package.jee.product) Installed Features: org.eclipse.platform 3.6.0.v20100602-9gF78GpqFt6trOGhL5t0nJy5fyGHKrwNY
|
2010-06-13 21:48:05
| 1,276,480,000 |
resolved fixed
|
9c7d16b
| 1,286,930,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Control.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Table.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Tree.java
|
SWT
|
524 | 327,113 |
Bug 327113 SWT 3.6 StyledText.addWordMovementListener() contain mistake
|
Build Identifier: M20090211-1700 public void addWordMovementListener(MovementListener movementListener) { ........checkWidget(); ........if (listener == null) SWT.error(SWT.ERROR_NULL_ARGUMENT); ............^^^^^^^^ --------- this is mistake, correct version: movementListener ........addListener(WordNext, new StyledTextListener(movementListener)); ........addListener(WordPrevious, new StyledTextListener(movementListener)); } Reproducible: Always
|
2010-10-06 10:40:21
| 1,286,380,000 |
resolved fixed
|
48bb2b2
| 1,286,920,000 |
bundles/org.eclipse.swt/Eclipse SWT Custom Widgets/common/org/eclipse/swt/custom/StyledText.java
|
SWT
|
525 | 327,365 |
Bug 327365 Need methods in internal Cocoa classes
|
I'm trying to make use of NSApplication.arrangeInFront & NSWindow.setRepresentedFilename for few mac tweaks. It would be great to have those methods in the SWT Cocoa internal classes (without them I'm unable to proceed). These methods are not directly used in SWT, so there is no reason for SWT to add them. Thats why I decided to bribe with a beer for the person who adds these :-)
|
2010-10-08 16:30:25
| 1,286,570,000 |
resolved fixed
|
05cd5d9
| 1,286,900,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSApplication.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSWindow.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java
|
SWT
|
526 | 326,479 |
Bug 326479 Display.getAppMenuBar() removes all existing menus
| null |
2010-09-29 01:10:33
| 1,285,740,000 |
resolved fixed
|
6eee86b
| 1,286,310,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java
|
SWT
|
527 | 326,200 |
Bug 326200 Disabled button in status bar becames enabled by itself; then handling fails with NotEnabledException
|
Build Identifier: 3.6, 20100617-1415 A command was added to status bar: <extension point="org.eclipse.ui.menus"> <menuContribution locationURI="toolbar:org.eclipse.ui.trim.status?after=HEAD_GROUP"> <toolbar id="..."> <command ...> ... Handler is enabled and disabled depending on application state; the command and button are enabled/disabled correctly when state is changed. When certain actions are performed in eclipse, e.g. when a file is opened in editor, the button suddenly becomes enabled. When user clicks the buton, an exception is logged: Failed to execute item com.klocwork.inforceeclipse.errorhandling.statusBarSyncNotification org.eclipse.core.commands.NotEnabledException: Trying to execute the disabled command <id> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:469) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) ... Yes, the command and handler are still disabled. I tried to debug it, and it appears that the WorkbenchWindow.run() method first tries to disable toolbar (not separate buttons), and then enables toolbar back after operation is complete. The cocoa implementation of ToolBar.setEnabled(false) simply disables all buttons, and then ToolBar.setEnabled(true) enables all buttons, even if they were disabled before (see ToolBar.enableWidget). Other implementations (e.g. GTK) of ToolBar.setEnabled keep enabled state of buttons separately. I believe this must be fixed in SWT; but also can be fixed in WorkbenchWindow - wondow can restore buttons' state based on commands state. Reproducible: Always
|
2010-09-24 17:18:24
| 1,285,360,000 |
resolved fixed
|
0c7ea34
| 1,285,630,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/ToolBar.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/ToolItem.java
|
SWT
|
528 | 307,302 |
Bug 307302 [SWT_AWT] SWT interfers with application menu
|
Build Identifier: 3.6M6 An AWT/Swing user interface may or may not decide to use the screen menu bar. The various configuration tweaks are: 1. Setting the "apple.laf.useScreenMenuBar" system property to "true". 2. Setting the "com.apple.mrj.application.apple.menu.about.name" system property to whatever name. 3. Invoking "com.apple.eawt.Application.getApplication().addApplicationListener(listener)" to hook to the various application menu items. 4. com.apple.eawt.Application.getApplication().setEnabledPreferencesMenu(true); Adding an SWT control must not interfer with the menus that appear in that bar, which is not the case currently. This is a showstopper for some of my users. SWT should detect that AWT is in the picture and not touch the application menu. Reproducible: Always Steps to Reproduce: 1. Create an AWT/Swing application. 2. Configures the application menu bar through Mac-specific system properties and APIs. 3. Embed an SWT control => menus are not the ones expected.
|
2010-03-28 05:55:07
| 1,269,770,000 |
resolved fixed
|
be95492
| 1,285,620,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSMenuItem.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT WebKit/cocoa/org/eclipse/swt/browser/WebKit.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
529 | 298,698 |
Bug 298698 Form Feed (\f) and VT make StyledText go crazy
| null |
2010-01-01 06:50:54
| 1,262,350,000 |
resolved fixed
|
e889534
| 1,285,110,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/GC.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/Path.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/TextLayout.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Link.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Text.java
|
SWT
|
530 | 297,511 |
Bug 297511 [widgets] nicer truncation of Table/Tree items
|
Table/TreeItems that are too long for their columns currently get truncated at the column bound. Other OSX apps tend to use "..." in this case, either at the "end" of the string (eg.- iTunes), or in the middle (eg.- Finder). Perhaps swt's custom Table/Tree data cell should do something similar.
|
2009-12-10 12:20:28
| 1,260,470,000 |
resolved fixed
|
758b181
| 1,285,070,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Table.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Tree.java
|
SWT
|
531 | 284,028 |
Bug 284028 [Widgets] New API for a single menu bar per application/Display
|
Some time ago, Steve N. and I discussed the idea of the SWT supporting a single menu bar per application, much like native applications on the Mac. Because Menus are currently associated with Shells, this leads to a couple of problems. -- Any window opened on top of the active Shell (modal dialogs, Find dialog, etc.) causes the menu bar to disappear. -- An application with no windows open has no menu bar, except for the Apple and application menu. Closing the last window of an application normally does not end the application on the Mac, so you need some way to let the user open a new document or perform some other operation. The first problem can be worked around because you can create a menu bar every time you open a window and adjust it as needed. The second problem has no workaround. I have seen some solutions that rely on an offscreen window that becomes active when all other windows are closed, but this breaks down with the arrival of Expose because the user could potentially select it. It's also a performance improvement because adding and removing NSMenus from the menu bar is an expensive operation. A cross-platform way to handle this would be a new method Display.setMenuBar(), that would establish a 'menu of last resort' that gets used if the active Shell does not display a menu bar. This would let the current Shell-based API coexist with the new in that Shells could continue to create menu bars that take higher priority over the default menu bar.
|
2009-07-20 12:29:42
| 1,248,110,000 |
resolved fixed
|
8b52c07
| 1,285,020,000 |
bundles/org.eclipse.swt/Eclipse SWT/carbon/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Menu.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/MenuItem.java bundles/org.eclipse.swt/Eclipse SWT/common/org/eclipse/swt/SWT.java bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/motif/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/photon/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/qt/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/wpf/org/eclipse/swt/widgets/Display.java
|
SWT
|
532 | 325,687 |
Bug 325687 Unit test failures in colors
|
test_ConstructorLorg_eclipse_swt_graphics_DeviceLorg_eclipse_swt_graphics_ImageData Failure :a: expected:<RGB {248, 16, 15}> but was:<RGB {255, 0, 0}> junit.framework.AssertionFailedError: :a: expected:<RGB {248, 16, 15}> but was:<RGB {255, 0, 0}> at org.eclipse.swt.tests.junit.Test_org_eclipse_swt_graphics_Image.test_ConstructorLorg_eclipse_swt_graphics_DeviceLorg_eclipse_swt_graphics_ImageData(Test_org_eclipse_swt_graphics_Image.java:189) at org.eclipse.swt.tests.junit.Test_org_eclipse_swt_graphics_Image.runTest(Test_org_eclipse_swt_graphics_Image.java:644) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:376) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:209) at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35) at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:621) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:576) at org.eclipse.equinox.launcher.Main.run(Main.java:1409) at org.eclipse.equinox.launcher.Main.main(Main.java:1385) at org.eclipse.core.launcher.Main.main(Main.java:34) test_ConstructorLorg_eclipse_swt_graphics_DeviceLorg_eclipse_swt_graphics_ImageDataLorg_eclipse_swt_graphics_ImageData Failure :a: expected:<RGB {248, 16, 15}> but was:<RGB {255, 0, 0}> junit.framework.AssertionFailedError: :a: expected:<RGB {248, 16, 15}> but was:<RGB {255, 0, 0}> at org.eclipse.swt.tests.junit.Test_org_eclipse_swt_graphics_Image.test_ConstructorLorg_eclipse_swt_graphics_DeviceLorg_eclipse_swt_graphics_ImageDataLorg_eclipse_swt_graphics_ImageData(Test_org_eclipse_swt_graphics_Image.java:257) at org.eclipse.swt.tests.junit.Test_org_eclipse_swt_graphics_Image.runTest(Test_org_eclipse_swt_graphics_Image.java:645) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:376) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:209) at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35) at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:621) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:576) at org.eclipse.equinox.launcher.Main.run(Main.java:1409) at org.eclipse.equinox.launcher.Main.main(Main.java:1385) at org.eclipse.core.launcher.Main.main(Main.java:34) Failure rgb.equals(colorRGB) junit.framework.AssertionFailedError: rgb.equals(colorRGB) at org.eclipse.swt.tests.junit.Test_org_eclipse_swt_graphics_Image.getImageData2(Test_org_eclipse_swt_graphics_Image.java:710) at org.eclipse.swt.tests.junit.Test_org_eclipse_swt_graphics_Image.test_getImageData(Test_org_eclipse_swt_graphics_Image.java:496) at org.eclipse.swt.tests.junit.Test_org_eclipse_swt_graphics_Image.runTest(Test_org_eclipse_swt_graphics_Image.java:652) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:376) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:209) at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35) at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:621) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:576) at org.eclipse.equinox.launcher.Main.run(Main.java:1409) at org.eclipse.equinox.launcher.Main.main(Main.java:1385) at org.eclipse.core.launcher.Main.main(Main.java:34)
|
2010-09-18 16:15:19
| 1,284,840,000 |
resolved fixed
|
af2e4c6
| 1,285,010,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSColor.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/GC.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/Image.java
|
SWT
|
533 | 325,153 |
Bug 325153 Inconsistent use of NSColorSpaces in Cocoa SWT
| null |
2010-09-13 14:58:45
| 1,284,400,000 |
resolved fixed
|
2e0136c
| 1,284,770,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSColor.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSColorSpace.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/Cursor.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/GC.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/Image.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/Pattern.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/TextLayout.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/ColorDialog.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Combo.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Control.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/DateTime.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/DirectoryDialog.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/FontDialog.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Group.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Link.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Spinner.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Table.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/TaskItem.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Text.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/ToolItem.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Tree.java
|
SWT
|
534 | 325,607 |
Bug 325607 Eclipse crashed - once again
|
Build Identifier: 3.6 I've lost count how many time I have filed a bug like this, and I don't even know if my eclipse crashes always because of the same reason. I know that this is starting to get on my nerves. I see that this is related to Safari and might not be fixable by the swt team. In that case I wonder if there a switch that lets me use FF/gecko instead. Reproducible: Sometimes
|
2010-09-17 11:06:58
| 1,284,740,000 |
resolved fixed
|
f5d1319
| 1,284,760,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
535 | 324,345 |
Bug 324345 [SWT_AWT] SWT.MouseMove events not being delivered to embedded Shell
|
Build Identifier: SWT 3.7M1 When embedding a Browser in an AWT application (but other controls may have the same issue), cursor behavior is messed up between AWT and SWT. Here are several things I noticed: 1. When an AWT control has the focus, the cursor does not change when hovering the SWT controls. 2. When a text field of a XULRunner browser is focused (caret), hovering an AWT component does not always change the cursor (generally the first time only). 3. When a text field of a Safari browser is focused (caret), hovering other DOM elements do not change the cursor, this until we hover an AWT component or click elsewhere. Reproducible: Always Steps to Reproduce: 1. Open an SWT_AWT application containing a browser and an AWT control with a defined cursor. 2. Give focus to the SWT control and see what happens when you hover the AWT component, and vice versa.
|
2010-09-02 15:33:09
| 1,283,460,000 |
resolved fixed
|
df518e1
| 1,284,760,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
536 | 325,383 |
Bug 325383 StyledText has problems with layout in the presence of ligatures
|
[3.6.0 and 3.6.1] Create a mini snippet with just a StyledText in a shell: StyledText styledText = new StyledText(shell, SWT.V_SCROLL | SWT.H_SCROLL); Enter the following characters and observe where the cursor moves after each character: abcdeffg Note that after entering the second 'f' the cursor is in the wrong position. Happens for the ligature 'fi' as well.
|
2010-09-15 15:02:29
| 1,284,580,000 |
resolved fixed
|
1d12a52
| 1,284,650,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/graphics/TextLayout.java
|
SWT
|
537 | 325,012 |
Bug 325012 Colors returned by Mac Color Dialog get shifted based on calibrated color space
|
Build Identifier: I20100608-0911 The color dialog on Mac takes in an RGB value and generates an NSColor using device colorspace, then the user manipulates the values manually. The NSColor is then transformed using the calibrated colorspace and then converted into an RGB object. That conversion leads to a shifting of values. In cases where the user is using the eyedropper, this is probably the correct way to handle things, but if the user is manually entering HSB/RGB values then we may want to retain the value exactly. Reproducible: Always Steps to Reproduce: 1. Open a color dialog 2. Enter in 190, 0, 19 in HSB 3. Returned RGB value gets mapped to 190,0,14 for me when passed back into next open of color dialog.
|
2010-09-10 17:06:50
| 1,284,150,000 |
resolved fixed
|
dd9b785
| 1,284,400,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/ColorDialog.java
|
SWT
|
538 | 289,868 |
Bug 289868 [10.6][Widgets] Properties View properties label disappears when selected
| null |
2009-09-18 11:36:28
| 1,253,290,000 |
resolved fixed
|
ec10911
| 1,284,110,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Table.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Tree.java
|
SWT
|
539 | 276,346 |
Bug 276346 TableEditor positioning wrong on cocoa
| null |
2009-05-14 12:47:27
| 1,242,320,000 |
resolved fixed
|
c1b8d32
| 1,284,110,000 |
bundles/org.eclipse.swt/Eclipse SWT Custom Widgets/common/org/eclipse/swt/custom/TableEditor.java
|
SWT
|
540 | 324,892 |
Bug 324892 Wrong constant values for some IA2 events
| null |
2010-09-09 14:58:37
| 1,284,060,000 |
resolved fixed
|
1055529
| 1,284,060,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/win32/org/eclipse/swt/internal/ole/win32/COM.java
|
SWT
|
541 | 324,497 |
Bug 324497 [Widgets] NullPointerException at org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex
|
Build Identifier: I20100608-0911 java.lang.NullPointerException at org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:117) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5216) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1025) at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1021) at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2240) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:1943) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2008) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5040) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4582) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:4659) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:115) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3274) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) Reproducible: Sometimes Steps to Reproduce: Haven't been able to associate this with a particular activity, but happens occasionally.
|
2010-09-03 17:35:04
| 1,283,550,000 |
resolved fixed
|
5d38390
| 1,283,890,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Link.java
|
SWT
|
542 | 321,754 |
Bug 321754 SWT.TOOL window doesn't show minimize button when specified
|
Steps: 1. Run this code. 2. Note that the minimize button isn't enabled, even though SWT.SHELL_TRIM is set. -------------------------------------------------- package snippets; import org.eclipse.swt.*; import org.eclipse.swt.events.*; import org.eclipse.swt.graphics.*; import org.eclipse.swt.layout.*; import org.eclipse.swt.widgets.*; public class ToolWindowExample { public static void main(String[] args) { Display display = new Display(); final Shell shell = new Shell(display); shell.setLayout(new GridLayout(1, false)); Button button = new Button(shell, SWT.PUSH); button.setText("Click me"); button.addSelectionListener(new SelectionAdapter() { public void widgetSelected(SelectionEvent e) { Shell shell2 = new Shell(SWT.TOOL | SWT.RESIZE | SWT.SHELL_TRIM); shell2.setLayout(new GridLayout(1, false)); shell2.setText("Palette"); Label l = new Label(shell2, SWT.LEFT); l.setText("This is a SWT.TOOL Shell"); Point origin = shell.getLocation(); origin.x += 100; origin.y += 100; shell2.pack(); shell2.open(); } }); shell.pack(); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) display.sleep(); } display.dispose(); } }
|
2010-08-04 12:15:54
| 1,280,940,000 |
resolved fixed
|
5a55475
| 1,283,450,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Shell.java
|
SWT
|
543 | 318,830 |
Bug 318830 Text.setText fails during FocusOut event listener (SWT.SINGLE, and when followed by access to the Text)
|
Build Identifier: swt-I20100608-0911-cocoa-macosx-x86_64 When setText is done in a FocusOut event listener, it sometimes fails to change the Text. This happens when setText is followed by getCharCount, computeSize, getText, and possibly any method that accesses the Text content. If the FocusOut event is caused by switching to a different application (rather than to a different widget), setText works. If setText is NOT followed by another Text method, it works. I have traced setText and getText down to NSCell.setTitle(NSString) and NSCell.title(). The NSCell is the same in both calls. However, when setText fails, the NSString returned by title() is the unchanged value, not the value just set with setTitle(string). Sample snippet contains two Texts. On FocusIn the first Text is set to "Hello"; on FocusOut to "Goodbye". Clicking to the second Text demonstrates that setText fails to change the area's content. Commenting out subsequent access to the Text, or losing focus by app switch shows the that setText succeeds in changing the content. I am rating as a major bug because it prevents implementing an auto-complete text field that is essential to our project. Reproducible: Always Steps to Reproduce: 1. Run the example. 2. See that clicking to the second Text does not change the first one, but switching apps does. 3. Remove call to getCharCount() in the FocusOut listener. 4. See that setText now succeeds in both situations.
|
2010-07-04 22:29:57
| 1,278,300,000 |
resolved fixed
|
47941f7
| 1,283,380,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Text.java
|
SWT
|
544 | 322,966 |
Bug 322966 Button.computeSize() may change the button size
| null |
2010-08-17 18:56:28
| 1,282,090,000 |
resolved fixed
|
f564bd0
| 1,283,210,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Button.java
|
SWT
|
545 | 323,995 |
Bug 323995 [Accessibility] StyledText selection incorrect after caret moved event
|
Eclipse 3.6.1 RC2. One of the JAWS developers sent me an email saying IAccessibleText::selection in StyledText was incorrect after he received a "caret moved" event. It turns out that this is because JAWS runs in-process, and StyledText does indeed send "caret moved" before finalizing the selection. When testing with AccProbe running out-of-process, this discrepancy went unnoticed, because the selection is finalized before an out-of-process client can ask for it.
|
2010-08-30 12:38:24
| 1,283,190,000 |
resolved fixed
|
e949ec7
| 1,283,190,000 |
bundles/org.eclipse.swt/Eclipse SWT Custom Widgets/common/org/eclipse/swt/custom/StyledText.java
|
SWT
|
546 | 323,763 |
Bug 323763 Eclipse 3.7 M1 crashes as it is starting up - detected by Java Runtime Environment
| null |
2010-08-26 17:51:59
| 1,282,860,000 |
resolved fixed
|
84396e1
| 1,282,930,000 |
bundles/org.eclipse.swt/Eclipse SWT WebKit/gtk/org/eclipse/swt/browser/WebKit.java bundles/org.eclipse.swt/Eclipse SWT WebKit/gtk/org/eclipse/swt/internal/webkit/WebKitGTK.java
|
SWT
|
547 | 321,974 |
Bug 321974 False presentation of a control contributed through the org.eclipse.ui.menu extension point
|
Build Identifier: 20100617-1415 Hello Eclipse-Team, I have found the following bug. By using the implemented extension point named org.eclipse.ui.menus I have added a custom control. The visual presentation of this control in my toolbar under windows vista as well as ubuntu 10.04 is fine (see screenshots). Under MAC OS X 10.6 the visual presentation seems not to be correct. Obviously there is a mismatch with the position of the control. For better understanding I have added 3 screenshots and an example project. Any suggestions or workarounds would be very helpful. Kind regards, Adam Reproducible: Always Steps to Reproduce: 1. import toolbar_control.zip 2. Start project 3. See bug :)
|
2010-08-06 07:43:52
| 1,281,100,000 |
resolved fixed
|
bfa7f22
| 1,282,930,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/ToolBar.java
|
SWT
|
548 | 323,535 |
Bug 323535 Checkbox Table Column header not quite wide enough
|
Run ControlExample. Go to Table tab and click CHECK and Header Visible *in that order*. Notice that the first column header (for Name) has a 1-pixel sliver of white along the left-hand side. (Note that if you check Header Visible and then CHECK, the column header size is correct).
|
2010-08-24 15:15:01
| 1,282,680,000 |
resolved fixed
|
328eb09
| 1,282,680,000 |
bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Table.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Tree.java
|
SWT
|
549 | 320,064 |
Bug 320064 StyledText and CCombo should also use preceding CLabel as accessible name
|
Currently, StyledText and CCombo will look to see if a Label precedes them in the z-order (i.e. the Label must be a sibling, and it must be created immediately before the StyledText or CCombo), and if so, then the Label text can be used for the StyledText or CCombo's default accessible name.
|
2010-07-16 00:47:21
| 1,279,260,000 |
resolved fixed
|
7015d5f
| 1,282,660,000 |
bundles/org.eclipse.swt/Eclipse SWT Custom Widgets/common/org/eclipse/swt/custom/CCombo.java bundles/org.eclipse.swt/Eclipse SWT Custom Widgets/common/org/eclipse/swt/custom/StyledText.java
|
SWT
|
550 | 317,872 |
Bug 317872 cocoa icon problem
| null |
2010-06-24 14:35:39
| 1,277,400,000 |
resolved fixed
|
3208192
| 1,282,600,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSImage.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java
|
SWT
|
551 | 320,066 |
Bug 320066 DROP_DOWN ToolItems need accessible name
|
The JFace ToolBarManager adds an accessible listener to automatically use a graphic ToolItem's tooltip text as its accessible name. This does not work for split buttons (aka ToolItems with DROP_DOWN style). To see this, run inspect32.exe and tab or arrow through the Eclipse tool bar. The tool items with a drop down menu will have role "split button" but they will not have a name.
|
2010-07-16 01:49:50
| 1,279,260,000 |
resolved fixed
|
378e7c0
| 1,282,600,000 |
bundles/org.eclipse.swt/Eclipse SWT Accessibility/win32/org/eclipse/swt/accessibility/Accessible.java
|
SWT
|
552 | 323,373 |
Bug 323373 StyledTextRenderer.hasLink() uses invalid indexing if no ranges array is defined
|
Build Identifier: I20100608-0911 I have implemented a org.eclipse.swt.custom.LineStyleListener to style my text (links, different colors), and for each line there can be 0-N StyleRanges. If I do not specify the LineStyleEvent.ranges array, then changing the mouse cursor when the mouse cursor is over a link doesn't always work correctly. I think the problem is in the method org.eclipse.swt.custom.StyledTextRenderer.hasLink(int): ... for (int i = 0; i < styles.length; i++) { if (styles[i].start <= offset && offset < styles[i].start + styles[i].length && styles[i >> 1].underline && styles[i >> 1].underlineStyle == SWT.UNDERLINE_LINK) { return true; } } ... And more specifically in the latter two cases where the array 'styles' is indexed ("styles[i >> 1]"). I think those should be replaced with "styles[i]". If I define the LineStyleEvent.ranges array then mouse cursor is changed correctly. Reproducible: Always
|
2010-08-23 06:04:23
| 1,282,560,000 |
resolved fixed
|
53ee32a
| 1,282,580,000 |
bundles/org.eclipse.swt/Eclipse SWT Custom Widgets/common/org/eclipse/swt/custom/StyledTextRenderer.java
|
SWT
|
553 | 317,163 |
Bug 317163 Browser.java dispatching to platform specific implementation has room for improvment
|
Currently the Browser class has a gigantic "if" to detect the Browser class of choice that connects the actual platform specific Browser implementation: if ((style & SWT.MOZILLA) != 0) { className = "org.eclipse.swt.browser.Mozilla"; //$NON-NLS-1$ } else { if ("win32".equals (platform) || "wpf".equals (platform)) { //$NON-NLS-1$ $NON-NLS-2$ className = "org.eclipse.swt.browser.IE"; //$NON-NLS-1$ } else if ("motif".equals (platform)) { //$NON-NLS-1$ className = "org.eclipse.swt.browser.Mozilla"; //$NON-NLS-1$ } else if ("gtk".equals (platform)) { //$NON-NLS-1$ className = "org.eclipse.swt.browser.Mozilla"; //$NON-NLS-1$ } else if ("carbon".equals (platform) || "cocoa".equals (platform)) { //$NON-NLS-1$ className = "org.eclipse.swt.browser.Safari"; //$NON-NLS-1$ } else if ("photon".equals (platform)) { //$NON-NLS-1$ className = "org.eclipse.swt.browser.Voyager"; //$NON-NLS-1$ } else { dispose (); SWT.error (SWT.ERROR_NO_HANDLES); } } This design makes it unbearable hard for new platforms to add their implementation (and its a pretty bad design anyway). Also using strings and reflection to find a class is the second bad idea that I see here. I propose to use a class BrowserFactory with a single static method createBrowser() which returns an instance of of WebBrowser and then every platform can easily implement its own version of BrowserFactory to retrieve the implementation.
|
2010-06-17 08:15:46
| 1,276,780,000 |
resolved fixed
|
06f06dd
| 1,282,330,000 |
bundles/org.eclipse.swt/Eclipse SWT Browser/carbon/org/eclipse/swt/browser/BrowserFactory.java bundles/org.eclipse.swt/Eclipse SWT Browser/cocoa/org/eclipse/swt/browser/BrowserFactory.java bundles/org.eclipse.swt/Eclipse SWT Browser/common/org/eclipse/swt/browser/Browser.java bundles/org.eclipse.swt/Eclipse SWT Browser/common/org/eclipse/swt/browser/WebBrowser.java bundles/org.eclipse.swt/Eclipse SWT Browser/forms/org/eclipse/swt/browser/BrowserFactory.java bundles/org.eclipse.swt/Eclipse SWT Browser/forms/org/eclipse/swt/browser/IE.java bundles/org.eclipse.swt/Eclipse SWT Browser/gtk/org/eclipse/swt/browser/BrowserFactory.java bundles/org.eclipse.swt/Eclipse SWT Browser/motif/org/eclipse/swt/browser/BrowserFactory.java bundles/org.eclipse.swt/Eclipse SWT Browser/photon/org/eclipse/swt/browser/BrowserFactory.java bundles/org.eclipse.swt/Eclipse SWT Browser/photon/org/eclipse/swt/browser/Voyager.java bundles/org.eclipse.swt/Eclipse SWT Browser/win32/org/eclipse/swt/browser/BrowserFactory.java bundles/org.eclipse.swt/Eclipse SWT Browser/win32/org/eclipse/swt/browser/IE.java bundles/org.eclipse.swt/Eclipse SWT Browser/wpf/org/eclipse/swt/browser/BrowserFactory.java bundles/org.eclipse.swt/Eclipse SWT Browser/wpf/org/eclipse/swt/browser/IE.java bundles/org.eclipse.swt/Eclipse SWT Mozilla/common/org/eclipse/swt/browser/Mozilla.java bundles/org.eclipse.swt/Eclipse SWT WebKit/carbon/org/eclipse/swt/browser/WebKit.java bundles/org.eclipse.swt/Eclipse SWT WebKit/cocoa/org/eclipse/swt/browser/WebKit.java bundles/org.eclipse.swt/Eclipse SWT WebKit/gtk/org/eclipse/swt/browser/WebKit.java
|
SWT
|
554 | 323,219 |
Bug 323219 Spinner.setDigits triggers a SWT.Selection Event on Linux and not on Windows
|
Build Identifier: 20100218-1602 In Windows, calling setDigits() on a spinner does not fire any event. This is not the case on Linux. The attached JUnit test highlights the bug, this event should not be triggered when calling setDigits(). This makes our product working differently in Windows and Linux. Reproducible: Always Steps to Reproduce: 1.Create a spinner. 2.Call setDigits(XX) 3.On Windows, the event is not fired. What is fine. 4.On Linux, the event is fired. Here is the bug.
|
2010-08-20 05:05:42
| 1,282,300,000 |
resolved fixed
|
7e2de3f
| 1,282,320,000 |
bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Spinner.java
|
SWT
|
555 | 323,092 |
Bug 323092 ScrollBar SelectionEvent detail field not being set correctly at end of a drag
| null |
2010-08-18 18:23:59
| 1,282,170,000 |
resolved fixed
|
f0db433
| 1,282,320,000 |
bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/ScrollBar.java
|
SWT
|
556 | 323,056 |
Bug 323056 [Accessibility] get_hyperlink returns incorrect address for accessible
| null |
2010-08-18 11:49:36
| 1,282,150,000 |
resolved fixed
|
efc7ad7
| 1,282,150,000 |
bundles/org.eclipse.swt/Eclipse SWT Accessibility/win32/org/eclipse/swt/accessibility/Accessible.java
|
SWT
|
557 | 303,454 |
Bug 303454 [table] [SWT.CHECK] SWT.CHECK on a table does not behave consistently
|
A table with SWT.CHECK does not render the column label correctly. On a macosx/carbon, the first column header("foo") appears on the second column which is not the checkbox. On gtk and even win32, the column "foo" is the same as column as the checkbox. Testcase: public class Main { public static void main(String[] args) { Display display = new Display(); Shell shell = new Shell(display); shell.setLayout(new GridLayout(1, false)); Table table = new Table(shell, SWT.SINGLE | SWT.BORDER | SWT.FULL_SELECTION | SWT.HIDE_SELECTION | SWT.H_SCROLL | SWT.CHECK); table.setLayoutData(new GridData(SWT.FILL, SWT.FILL, true, true)); table.setLinesVisible(true); table.setHeaderVisible(true); TableColumn tableColumn = new TableColumn(table, SWT.LEAD); tableColumn.setText("foo"); TableColumn tableColumn2 = new TableColumn(table, SWT.LEAD); tableColumn2.setText("bar"); TableColumn tableColumn3 = new TableColumn(table, SWT.LEAD); tableColumn3.setText("baz"); new TableItem(table, SWT.NONE).setText(new String[]{ "cell-1-1", "cell-1-2", "cell-1-3"}); new TableItem(table, SWT.NONE).setText(new String[]{ "cell-2-1", "cell-2-2", "cell-2-3"}); for (int i = 0; i < table.getColumnCount(); i++) { table.getColumn(i).pack(); } shell.pack(); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) display.sleep(); } display.dispose(); } }
|
2010-02-22 01:45:42
| 1,266,820,000 |
resolved fixed
|
95f8ac5
| 1,282,080,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/NSScrollView.java bundles/org.eclipse.swt/Eclipse SWT PI/cocoa/org/eclipse/swt/internal/cocoa/OS.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Table.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Tree.java bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Widget.java
|
SWT
|
558 | 322,438 |
Bug 322438 [Browser-Webkit] Mouse events have wrong button values (0,1,2 instead of 1,2,3)
|
Build Identifier: SWT 3.6 When we add a mouse listener to a Browser with Webkit rendering, we receive events with wrong values for the button field. Normal values are 1, 2 and 3 but we receive 0, 1 and 2. Reproducible: Always Steps to Reproduce: 1. Create a Browser. 2. Add a mouse listener that prints e.button
|
2010-08-11 17:24:45
| 1,281,560,000 |
resolved fixed
|
3fcd225
| 1,282,070,000 |
bundles/org.eclipse.swt/Eclipse SWT WebKit/gtk/org/eclipse/swt/browser/WebKit.java
|
SWT
|
559 | 312,960 |
Bug 312960 org.eclipse.swt.custom.PopupList - should be able to set the SWT.H_SCROLL style on the List widget
|
Build Identifier: M20080911-1700 When using org.eclipse.swt.custom.PopupList, their is no method or argument in the constructor to set the style of the List widget. More importantly I can't set the SWT.H_SCROLL style on the List widget, it only has SWT.V_SCROLL. This bug is blocking a core feature in our product where the customer cannot see the list of values if the values are very long. Even the tooltip doesn't wrap. Reproducible: Always Steps to Reproduce: 1. Look in the constructor of org.eclipse.swt.custom.PopupList 2. Notice when it instantiates the List widget it hardcodes the style with no SWT.H_SCROLL
|
2010-05-14 14:42:05
| 1,273,860,000 |
resolved fixed
|
1a019b8
| 1,281,940,000 |
bundles/org.eclipse.swt/Eclipse SWT Custom Widgets/common/org/eclipse/swt/custom/PopupList.java
|
SWT
|
560 | 322,222 |
Bug 322222 [Widgets] segfault in pango_layout_new when closing a dialog
| null |
2010-08-10 08:54:52
| 1,281,440,000 |
resolved fixed
|
5b6a9aa
| 1,281,730,000 |
bundles/org.eclipse.swt/Eclipse SWT PI/gtk/org/eclipse/swt/internal/gtk/OS.java bundles/org.eclipse.swt/Eclipse SWT/gtk/org/eclipse/swt/widgets/Display.java
|
SWT
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.