Community
Participate
Working Groups
This problem was detected by WSED test. We are using the first Eclipse 2.0.1 drop we received. Everything was fine the build before moving to 2.0.1. The problem started with our first build on 2.0.1. The 2.0.1 build is the first one sent to RTP which WSAD built on. We (WSED) then built on top of WSAD. We have not had a chance to try the lasted 2.0.1 drop because we need to wait for WSAD to get a good build on it. We expect to move to the newer drop within a day or two. On some machines when trying to drop down the list in the CCombo in a Table or TableTree, the list flashes. The user can not select an option. We extracted the CCombo.java files from 2.0 and 2.0.1 and see there are changes in the class, including changes to a method called dropdown(). We need this fixed in the 2.0.1 code stream because we are getting ready to ship on 2.0.1. There is a workaround, but it is not obvious to the customer. If you select the cell instead of the down arrow, the list shows fine. This is not an acceptable workaround because most customers would not think of trying to do this. This is not a problem on all our machines. We can not figure out why it works fine on some machines, but not others. We have detected at least 3 Thinkpads that it fails on (2 T23s and 1 T20). It works fine on other workstations and Thinkpads, including other T23s.
The code was changed because of bug report 21829. The code was changed so that if the list has entries wider than the combined text and button width then the list will be as wide as its widest entry and the right side of the list will be aligned with the right side of the button. I am investigating the code change.
Have you been able to identify any difference between the machines that work and the ones that don't? Are they all running Windows 2000? Does the problem occur with the CCombo in the Tasks view (create a task and edit the priority)?
All three machines which have the problem are Win 2000. However it works on other machines, same model, some O/S. The problem only occurs within a Table or TableTree Conrol, so it would not happen on the properties of a task. I am assuming you mean bring up the task's properties to edit the priority when you say "edit the priority"??? We will try to do some more debugging to see if we can narrow down why things are working differently on the different machines.
The Tasks View has a Table and if you double click in the "!" column, a CCombo pops up allowing you to toggle between High, Normal and Low priority. This only works for tasks you create (not tasks generated by the compiler etc). How are you testing the problem - do you have your own view that uses a CCombo? Is it possible to get a snippet of the code used to implement the editor?
Veronika, OK, I understand now. Yes, the priority on the task list is an execellent test example. It works for me no problem, but I went to one of the machines that has the problem in our code, and that machine also has the problem on the task list. So, this probably means you can not recreate the problem. We have rebuilt the jar file with some println's in CCombo to trace the some values. We plan to run it on a good machine and a bad machine to see if there is anything that seems weird that may help. Maybe you could have others in your area try the task list priority test to see if by chance they have the problem??? Thanks!!!
Veronika, I think we found the smoking gun. I believe it depends on a Mouse setting in the control panel. Go to the Mouse properties on the control panel. Select the Motion tab. In the Snap to default group, if the Move pointer to the default button in dialog boxes is checked, the problem happens. If it is not checked, the problem does not happen. I have not been able to verify this will all three bad machines, because 2 are not here, but I can recreate the problem now by clicking this setting. We just moved to the latest 2.0.1, and I have not been able to recreate the problem yet on that driver. I don't think anyone else has this build installed yet. We need to get you more info on this.
We had another bug with respect to "Snap to default group" Mouse move and the fix for that has fixed this problem too. I was able to reproduce this problem with Eclipse 2.0.1 build I20020814 and the problem was fixed in build I20020821. Marking problem fixed for 2.0.1.
Veronika, Thanks for your time!!! I am glad that there is a good explanation for while it was fixed. I just wish we had not found it for a day or two until we got to the newer driver. It would have saved some headaches for all of us.
