| Summary: | [Intro] cant listen to IIntroPart life cycle events | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Mazen Faraj <mfaraj> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | Keywords: | helpwanted |
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Mazen Faraj
oops! I opened it against myself ! :-) looking into this a bit more, the TaskView takes an activated/deactivated cycle on start up and shutdown. Meaning, when you open Intro, you get intro activated, deactivated, Task view activated, deactivated, then Intro view activated again. Does this make sense? is this what the apis are expected to do? Probably not, but likely the case for 3.1... is this related? I used to (in an RCP app on 3.0.2) have a property listener listening in to the zoom property. Unfortunately, 3.1 took away addPropertyChangeListener from PartPane, and seems to be disallowing my use of the internal PartPane and friends... What's a good way then to achieve the following? Detect when the user closes/standby-s the welcome page, in order to launch a new wizard? (this is to avoid the user staring at a blank perspective...) Your best bet at this point would be to listen to part close events and after each one check to see if the intro is available via the standard Intro API. 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. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. |