This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Property Sheet: Focus lost after keyboard entry | ||
---|---|---|---|
Product: | platform | Reporter: | bht <bht> |
Component: | Explorer | Assignee: | _ tboudreau <tboudreau> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows 95/98 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 31896 | ||
Bug Blocks: |
Description
bht
2003-10-03 09:04:07 UTC
Reassigning this issue to myself. Reproduced on WinXP. Fix is probably to call requestFocusInWindow on stopCellEditing(). Not sure yet where focus is ending up - possibly on null. The core problems are that 1. Swing doesn't define well where focus should go when a focused component is removed from a container - what should happen is that the FocusTraversalPolicy of the container should be used, but that's not what does happen. The easy answer to this is "well, don't remove components that have focus, silly!" but that's exactly the behavior of a JTable (or for that matter a JTree's rename field). 2. The old NetBeans window system does strange things with using focus to track the activated TopComponent, and injects additional focus events into the flow - where, in a standalone app, focus goes from Component A to Component B, in NetBeans focus goes from Component A to null to Component B. That's fixed in the new window system but I'll still need to do something here. Fixed on property panel rewrite branch Property panel rewrite branch merged. closed |