Community
Participate
Working Groups
Create a new feature using the wizard. Open the feature.xml, go into the information tab and you will notice that the default value of the "section" field is truncated.
Moving to SWT for comment - this is an old problem related to CCombo that refuses to go away. Here is the scenario: 1) Create a new Feature project. Use any name and accept all the defaults. 2) When the feature manifest editor opens, go to the 'Information' page. Notice now the text in the read-only combo is truncated at the beginning. The actual implementation for this section is in the following class: org.eclipse.pde.internal.ui.editor.feature.InfoSection The CCombo control is created in 'createContents' and the items are set in 'initializeSectionCombo'.
*** Bug 39342 has been marked as a duplicate of this bug. ***
Opened a wsa.prereq.workbench defect# 258934 for this problem. Basically the starting characters are chopped off when selecting an entry. It has been my observation that the problem happens only when the selection of an entry happens after the shell has been opened and the layout has been performed. If the selection has been done before the layout, then everything works fine.
*** Bug 151714 has been marked as a duplicate of this bug. ***
I cannot recreate the problem using the steps that Dejan has given. The 'Information' page has changed and no longer contains a CCombo.
Grant, running the code from bug 151714 (a duplicate) does not show the problem for me in Eclipse 3.3 M6. I am on XP, does the problem happen for you on Windows 2000?
I'll test it out on my W2K machine.
Created attachment 62145 [details] Snapshot of CCombo test The problem appears to happen for W2K only.
Sri, I will look into the problem on Windows 2000. Meanwhile, can you confirm that "wsa.prereq.workbench defect# 258934" works on XP but fails on 2000?
Here is what is happening: When CCombo calls selectAll() on the text control inside, the i-beam is placed at the end of the text. Windows scrolls to show the i-beam and when the text control is small, it scrolls to the left. Then, the CCombo is resized to be bigger (such that the scrolled text could be shown without scrolling) and the text is not scrolled because text does not scroll on resize. I have no idea how to fix this so CANTFIX for 3.3. I'm waiting for a brainwave.
Any plans to fix this in 3.4?
If there is no plan to fix this, why is it still open?
Reading this
The problem only happens on Windows 2000. We WONTFIX this.
This problem reproduces on Windows XP as well, when the the theme is "Windows Classic" - most people I know use it, though they are all technicians and probably prefer its simpler look... There is a quite good workaround: CCombo combo = new CCombo(outer, SWT.READ_ONLY | SWT.BORDER) { @Override public void select(int index) { super.select(index); setSelection(new Point(0, 0)); } }; combo.addSelectionListener(new SelectionAdapter() { @Override public void widgetSelected(SelectionEvent e) { combo.setSelection(new Point(0, 0)); } }); combo.addFocusListener(new FocusAdapter() { @Override public void focusLost(FocusEvent e) { combo.setSelection(new Point(0, 0)); } }); But first you have to remove the "final" keyword from CCombo.java and compile SWT for yourself (see https://bugs.eclipse.org/235968, Fixed > 080714). Viliam
If SWT officially supports XP running the Classic theme, shouldn't this bug be re-opened?
I was able to replicate the problem with Windowx XP using the Classic theme.
This is open for more than 2,5 years and not yet solved??? I am still running into that ugly bug on WinXP with Eclipse 3.4 and since subclassing is not allowed I cannot fix it without recompiling all SWT. Can someone please fix it or give a solution to it?
Additional note. The described fix above works only when also overriding checkSubclass(): CCombo rc = new CCombo(parent, SWT.FLAT) { @Override public void select(int index) { super.select(index); setSelection(new Point(0, 0)); } protected void checkSubclass () {} }; However, it is nasty to use this workaround :(
Seeing this issue on Windows 7 running Indigo and this worked for us: _combo.getShell().getDisplay().asyncExec(new Runnable() { @Override public void run() { _combo.setSelection(new Point(0, 0)); int len = _combo.getItem(ii).length(); _combo.setSelection(new Point(len, len)); } });
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
