Bugzilla – Full Text Bug Listing
| Summary: | Activate event events are not fired for controls | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Tim Buschtoens <tbuschto> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | 2.0 M3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Today I looked at the client-side code (Shell.js) and the problem is the following. Event is fired *only* if Shell.js#_isRelevantActivateEvent returns true. This method works fine for composites (when activate listener is attached to a composite), but not for a simple controls like buttons. For buttons in Shell.js#_isRelevantActivateEvent listeningWidget === widget and this method *always* returns false. One possible solution is to add additional condition in the if statement for exactly this case: listeningWidget === widget. I've checked all RAP releases from 1.1 to 1.5 and this issue is valid for all of them - no regression. Fixed in master with the changes for bug 390419. |
The follwing does not work in RWT: button.addListener( SWT.Activate, new Listener() { public void handleEvent( Event event ) { button.setText( "Active" ); } } ); The client does not send any activation events to the server. It works fine SWT. I'm not sure when this bug was introduced.