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

Bug 390800

Summary: Unable to edit data in Data Sets View
Product: [Technology] Jubula Reporter: Zeb Ford-Reitz <zeb.ford-reitz>
Component: UIAssignee: Achim Loerke <Achim.Loerke>
Status: CLOSED FIXED QA Contact: Oliver Goetz <Oliver.Goetz>
Severity: blocker    
Priority: P2    
Version: 1.2.1   
Target Milestone: Kepler   
Hardware: Macintosh   
OS: Mac OS X   
Whiteboard:
Bug Depends on: 388574    
Bug Blocks:    
Attachments:
Description Flags
Log snippet containing NPE stacktrace. none

Description Zeb Ford-Reitz CLA 2012-10-01 04:49:03 EDT
Created attachment 221709 [details]
Log snippet containing NPE stacktrace.

When activating a cell editor in the Data Sets View, an Unexpected Error dialog appears (due to a NullPointerException). This completely prevents editing the data, as the cell editor is no longer active. I've attached a stack trace of the error.

This error occurs in OS X 10.8.2 (Mountain Lion). It is not reproducible on OS X 10.7.4.

Cell editors in the Properties View seem to function correctly.
Comment 1 Zeb Ford-Reitz CLA 2012-10-01 04:51:36 EDT
It looks like WindowBuilder has a similar problem (http://www.eclipse.org/forums/index.php/m/899288/#msg_899288), which, for them at least, is apparently caused by bug 388574.
Comment 2 Zeb Ford-Reitz CLA 2012-10-01 04:53:16 EDT
Achim, can you take a look at this? I don't have access to a Mountain Lion install at the moment.
Comment 3 Achim Loerke CLA 2012-10-01 05:51:47 EDT
This is caused by bug 388574 which triggers a focus out event on Mountain Lion during editor creation.

As a workaround I've moved the addFocusListener() call after the editor creation.
Comment 4 Achim Loerke CLA 2012-10-01 06:09:59 EDT
fixed in Jubula master d991b72d723a91006e3a21ef9c1e2a695a1f8f16
Comment 5 Zeb Ford-Reitz CLA 2012-10-01 07:02:03 EDT
also applied changeset to gd_6.1 branch
Comment 6 Zeb Ford-Reitz CLA 2012-10-02 05:31:45 EDT
Passed manual test in the same environment in which the bug was discovered (OS X 10.8.2).