Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362563 - @Focus setFocus() called twice
Summary: @Focus setFocus() called twice
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-01 08:33 EDT by Karl Weber CLA
Modified: 2019-11-14 03:11 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Weber CLA 2011-11-01 08:33:14 EDT
Build Identifier: M20110912-1510

Under certain conditions setFocus is called twice.

When I have two MParts in an MPartStack and the size of the MPartStack is large enough so that one can see both CTabItems displayed, then setFocus() of an MPart is called twice when I change the selection.

When the size of the MPartStack is so small that only one CTabItem is displayed together with the small button displaying ">>" and the number of "hidden" CTabItems as index, then when I change the selection through the ">>" button, setFocus is called only once.

When setFocus is called twice, this happens


    * Through StackRenderer.ActivateJob.run()
    * Through Composite.setFocus of the Composite created in ContributedPartRenderer.createWidget. It is called through the MouseListener added to the CTabFolder in hookControllerLogic.

When setFocus is called only once, it happens through StackRenderer.ActivateJob.run().

Reproducible: Always

Steps to Reproduce:
Should be obvious from the description of the bug.
Comment 1 Lars Vogel CLA 2019-11-14 03:11:09 EST
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.