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.
[nb-beta4] New class wizard, step 4, Create Fields: 1. create new field 2. set initial value to 0 and push Next (but do not press enter to affirm initial value) 3. push Back: initial value is not set.
Behavior of [200111160100] on JDK1.4 is also strange: 2. set initial value to 0 and push Next. "0" is affirmed and selected. User has to push Next again.
fixed in trunk
VERIFIED
I'm afraid, I've found another testcase :-( New class wizard, step 4, Create Fields: 1. create new field field0 2. create new field field1 3. set initial value of field1 to "0" (but do not press enter to affirm) 3. Using mouse select field0. 4. Select field1 again -> inital value is not set to "0"
Another problem with PropertyPanel in Java wizard Fields panel is that it steals focus from field list when navigating in the list by keyboard. I expect that focus is moved in PropertyPanel.setModel call. I think call of this method should not change focus owner.
I think I won't be fixed in release 3.3.x. To fix these problems correctly, PropertyPanel has to be rewritten from scratch. Changing milestone to 3.4 and assigning to issues@openide
PropertyPanel belongs to property editors area. Please reassign back if I'm wrong.
No, it doesn't (in openide only package org.openide.explorer.propertysheet.editors)
Ok, it's ours, how happy we are :-)
passing to property sheet guys.
Bad success :-( a fix of this issue looks uneasy for me. The heart of problem is tn the method focusLost is new value set in block invokeLater() but in meantime new property model (including noted text field) is set --> the not stored values are lost. Fortunately an impact on a user and frequency is small.
reassigning to the new subcomponent owner
*** Issue 30525 has been marked as a duplicate of this issue. ***
A major portion of PropertyPanel will be rewritten with the property sheet rewrite (so it uses the rendering/editor infrastructure from the new JTable property sheet). I'd like to defer work on this until then - probably the rewrite will cure the problem. I'm adding this issue to the property sheet rewrite umbrella issue.
Changing to block PropertyPanel rewrite umbrella issue - rewriting PropertyPanel to use the new propertysheet's infrastructure will come after integration of the new property sheet.
Fixed on the property panel rewrite branch, and backed by a unit test.
Property panel rewrite branch merged.
verified