Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 282295 - UIProcess: remaining processes in Statusline after finishing
Summary: UIProcess: remaining processes in Statusline after finishing
Status: RESOLVED FIXED
Alias: None
Product: Riena
Classification: RT
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.2.0.M1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-02 10:41 EDT by Stefan Flick CLA
Modified: 2011-05-19 03:50 EDT (History)
1 user (show)

See Also:

Attachments
Fixes NPE in NavigationListener and cleans statusbar if context gets disposed in updateUI or finalUpdateUI (6.77 KB, patch)
2009-08-03 09:02 EDT, Steffen Kriese CLA 		christian.campo: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Flick CLA 2009-07-02 10:41:07 EDT 
When starting a UIProcess with the related navigation node as the UIProcess context (other object will not work at all) and you start dispose the node from inside the finalUpdateUI() method, the UIProcess is still visualized inside the status line.
Comment 1 Frank Borkowsky CLA 2009-07-02 12:04:34 EDT 
The processes also remain in the statusline when throwing an exception in the finalUpdateUI method. 

See SWT ExampleApplication -> Playground -> Exception Test -> throw NullPointerException in UIProcesss (finalUpdateUI)
Comment 2 Steffen Kriese CLA 2009-08-03 09:02:00 EDT 
Created attachment 143263 [details]
Fixes NPE in NavigationListener and cleans statusbar if context gets disposed in updateUI or finalUpdateUI
Comment 3 Christian Campo CLA 2009-08-04 03:10:49 EDT 
patch committed with some slight modifications, ExceptionHandlerService is called for exceptions that are catched, dependency between ridgets and navigation that was introduced in the patch was not committed but another solution was found.