Bug 13498 - Combo sends selectionChanged when it should not
Summary: Combo sends selectionChanged when it should not
Status: RESOLVED DUPLICATE of bug 94784
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux-Motif
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 13171
  Show dependency tree
 
Reported: 2002-04-11 08:09 EDT by Dani Megert CLA
Modified: 2005-05-12 10:45 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2002-04-11 08:09:09 EDT 
Build: I20020409
The problem only appears on Linux and it is not always happening.

Description: Combo sends selectionChanged when losing focus if text has been
changed.

Test Case:
1. Open Search Dialog - File Search
2. Search for *.java files (enter "*.java" - press Search)
3. Open Search Dialog - File Search
   - the first combo should contain "*.java"
4. Enter some text into the "Containing text:" Combo
5. Now add "x" after "*.java" (in the first Combo)
5. Press TAB
==> a selectionChanged event is fired and the fields are reset to the values
that belong to "*.java".
NOTE: The fields are only reset in build 20020409 because a workaround now
prevents this from happening. HoweverThe selectionEvent can be seen in the
debugger (add a breakpoint in TextSearchPage.handleWidgetSelected.

No selection event is sent under WindowsNT.
The strange thing is that other Combos don't do this under Linux. There must be
some special case either with grouping or listeners.
Comment 1 Mike Wilson CLA 2002-04-11 09:47:59 EDT 
Not sure what's going on here.
Comment 2 Grant Gayed CLA 2002-08-13 16:22:38 EDT 
I can't duplicate this now (ie.- hitting a breakpoint set in 
TextSearchPage.handleWidgetSelected by pressing tab), I think as a result of 
the File Search page widgets being changed in the last few months.  Can you 
still reproduce this problem in 2.0?
Comment 3 Dani Megert CLA 2002-08-14 03:03:31 EDT 
Can't be reproduce with 2.0: the behavior was unacceptable for 2.0 and therefore
 had to be fix somehow (see comments in 13171). You have to use the indicated
build (I20020409) under Linux to see the bug.
Comment 4 Steve Northover CLA 2005-03-29 21:15:55 EST 
Grant, if this no longer happens, please close this bug report.
Comment 5 Dani Megert CLA 2005-03-30 04:12:35 EST 
In order to verify please use the client code used in I20020409.
Comment 6 Dani Megert CLA 2005-03-30 05:10:49 EST 
Just to clarify: I did not check whether the bug is still there.
Comment 7 Grant Gayed CLA 2005-05-12 10:45:30 EDT 

*** This bug has been marked as a duplicate of 94784 ***