| Summary: | @GroupUpdates on selection only seems to work on the first workbench window | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Remy Suen <remy.suen> | ||||||
| Component: | Runtime | Assignee: | Oleg Besedin <ob1.eclipse> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | ob1.eclipse | ||||||
| Version: | 4.1 | ||||||||
| Target Milestone: | 4.2 M1 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Remy Suen
Created attachment 193384 [details]
SelectionService patch v1
1. Launch an inner with the patch applied to SelectionService (should apply cleanly to v1.20).
2. Select stuff in the 'Problems' view, both @Inject methods are being called.
3. Window > New Window
4. Repeat step 2 for this new workbench window. The @GroupUpdates method does not get called.
Created attachment 198152 [details]
Patch
Seems to be a side effect of an uninject event for a different object on the same context.
(In reply to comment #2) > Seems to be a side effect of an uninject event for a different object on the > same context. It sounds like this bug would happen even for cases where @GroupUpdates is not used then, is this correct? (In reply to comment #3) > It sounds like this bug would happen even for cases where @GroupUpdates is not > used then, is this correct? No, I don't think so. The problem is in setting "cachedEvent" type to null while, in reality, the event has not being processed. The "cachedEvent" is only used for grouped updates. Patch applied to CVS Head. |