Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 314164

Summary:	Remove IFocusable from package org.eclipse.e4.workbench.ui.behaviors
Product:	[Eclipse Project] e4	Reporter:	Sebastian Schneider <laluz>
Component:	UI	Assignee:	Project Inbox <e4.ui-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	bokowski, emoffatt, pwebster, remy.suen, tom.schindl
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Sebastian Schneider

2010-05-24 16:48:23 EDT

Build Identifier: 

see http://www.eclipse.org/forums/index.php?t=msg&th=168702&start=0&

Reproducible: Always

Comment 1 Paul Webster

2010-05-25 09:44:24 EDT

So what was the e4 equivalent of setFocus()?  I don't believe it's partActivated(part == myPart).

PW

Comment 2 Remy Suen

2010-05-25 09:52:27 EDT

(In reply to comment #1)
> So what was the e4 equivalent of setFocus()?  I don't believe it's
> partActivated(part == myPart).

There isn't one yet. We need a new annotation like @Focus or something similar to @Persist for handling this case. The renderer should invoke the annotated when the part has been activated.

Comment 3 Sebastian Schneider

2010-05-25 10:12:38 EDT

(In reply to comment #2)
> (In reply to comment #1)
> > So what was the e4 equivalent of setFocus()?  I don't believe it's
> > partActivated(part == myPart).
> 
> There isn't one yet. We need a new annotation like @Focus or something similar
> to @Persist for handling this case. The renderer should invoke the annotated
> when the part has been activated.

I'd like to support Remy's proposal of @Focus, which is consistent with other annotations like the mentioned @Persist, or @Execute, etc.

Comment 4 Remy Suen

2010-05-25 10:45:13 EDT

Please move this discussion to bug 310199.

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