| SWT Table error on Windows 2000 Pro [message #454318] |
Wed, 20 April 2005 06:13  |
Eclipse User |
|
|
|
Hi all
We have got a really strange problem. We have to client with windows
2000 professional and servicepack 4 that seems to configured exactly the
same. We use Eclipse Version: 3.0.1 and Build id: 200409161125.
In the implementation we use a TableViewer and both a ContentProvider
and a LabelProvider. We also set standard SWT colors on some rows in the
table (not using a ColorProvider, but directly in the Table using
setForeground()).
On the first client it works fine. On the other we get the error below,
when loading a table (using TableViewer.setInput()).
The big mystery is why the error only occurs on one of the two clients?
Any suggestions on the problem, a fix or workaround are are very welcome.
Best regards
Lars, Procard Aps, Denmark.
-----------------------------------------
java.lang.ArrayIndexOutOfBoundsException: 5
at org.eclipse.swt.widgets.Table._getItem(Table.java:96)
at org.eclipse.swt.widgets.Table.wmNotifyChild(Table.java:3187)
at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:4002)
at org.eclipse.swt.widgets.Composite.WM_NOTIFY(Composite.java:7 22)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3019 )
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3338 )
at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:139 7)
at org.eclipse.swt.widgets.Table.callWindowProc(Table.java:137)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3050 )
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3338 )
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:14 73)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2429)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:668 )
at org.eclipse.jface.window.Window.open(Window.java:648)
at
dk.procard.eclub.main.MainWindow.openApplication(MainWindow. java:1116)
at dk.procard.eclub.main.MainWindowCTR.create(MainWindowCTR.jav a:38)
at
dk.procard.eclub.control.MainControl.startApplication(MainCo ntrol.java:580)
at dk.procard.eclub.control.MainControl.main(MainControl.java:7 04)
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 com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Snippet:
------------------------------------------
|
|
|
|
|
| Re: SWT Table error on Windows 2000 Pro [message #454592 is a reply to message #454586] |
Mon, 25 April 2005 07:48  |
| Eclipse User |
|
|
|
The files are the same: version 5.81.4916.400
Any other suggestions?
Lars wrote:
> Thanks Steve, we will look into that ...
>
> */Lars
>
> Steve Northover wrote:
>
>> Is the verions of comctl32.dll different between the machines for some
>> reason? Find the file using the Windows Explorer and check the
>> properties
>> on both machines. There should be a version tab. It should be something
>> like 5.82.2800.1106 but whatever it is, it should be the same on both
>> machines.
>>
>> "Lars" <lars@eclub2.procard.dk> wrote in message
>> news:d45a3n$jmr$1@news.eclipse.org...
>>
>>> Hi all
>>>
>>> We have got a really strange problem. We have to client with windows
>>> 2000 professional and servicepack 4 that seems to configured exactly the
>>> same. We use Eclipse Version: 3.0.1 and Build id: 200409161125.
>>>
>>> In the implementation we use a TableViewer and both a ContentProvider
>>> and a LabelProvider. We also set standard SWT colors on some rows in the
>>> table (not using a ColorProvider, but directly in the Table using
>>> setForeground()).
>>>
>>> On the first client it works fine. On the other we get the error below,
>>> when loading a table (using TableViewer.setInput()).
>>>
>>> The big mystery is why the error only occurs on one of the two clients?
>>> Any suggestions on the problem, a fix or workaround are are very
>>> welcome.
>>>
>>> Best regards
>>> Lars, Procard Aps, Denmark.
>>>
>>> -----------------------------------------
>>> java.lang.ArrayIndexOutOfBoundsException: 5
>>> at org.eclipse.swt.widgets.Table._getItem(Table.java:96)
>>> at org.eclipse.swt.widgets.Table.wmNotifyChild(Table.java:3187)
>>> at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:4002)
>>> at org.eclipse.swt.widgets.Composite.WM_NOTIFY(Composite.java:7 22)
>>> at org.eclipse.swt.widgets.Control.windowProc(Control.java:3019 )
>>> at org.eclipse.swt.widgets.Display.windowProc(Display.java:3338 )
>>> at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
>>> at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:139 7)
>>> at org.eclipse.swt.widgets.Table.callWindowProc(Table.java:137)
>>> at org.eclipse.swt.widgets.Control.windowProc(Control.java:3050 )
>>> at org.eclipse.swt.widgets.Display.windowProc(Display.java:3338 )
>>> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
>>> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:14 73)
>>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2429)
>>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:668 )
>>> at org.eclipse.jface.window.Window.open(Window.java:648)
>>> at
>>> dk.procard.eclub.main.MainWindow.openApplication(MainWindow. java:1116)
>>> at dk.procard.eclub.main.MainWindowCTR.create(MainWindowCTR.jav a:38)
>>> at
>>>
>>
>> dk.procard.eclub.control.MainControl.startApplication(MainCo ntrol.java:580)
>>
>>
>>> at dk.procard.eclub.control.MainControl.main(MainControl.java:7 04)
>>> 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 com.sun.javaws.Launcher.executeApplication(Unknown Source)
>>> at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
>>> at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
>>> at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
>>> at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
>>> at com.sun.javaws.Launcher.run(Unknown Source)
>>> at java.lang.Thread.run(Unknown Source)
>>>
>>> Snippet:
>>> ------------------------------------------
>>
>>
>>
>>
|
|
|
Powered by
FUDForum. Page generated in 0.04190 seconds
Home