JDK-8103469 : Handling of incorrect values by the inspector could be improved
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: tools-scenebuilder
  • Affected Version: 7u6
  • Priority: P3
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2012-08-01
  • Updated: 2015-06-16
  • Resolved: 2013-04-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Resolved
Related Reports
Blocks :  
JDK-8122107 - InspectorPanel: Incorrect handling of some values
Duplicate :  
JDK-8103256 - Inspector Editors Error Checking
Relates :  
JDK-8103394 - An error message should be displayed when an invalid value is entered in the inspector
Description
Today, when a user enters a property value, the inspector check its validity, and set back the previous value if the entered value is invalid.
This is problematic, since SB erase data entered by a user.
The worst case is for "complex" values such as Style. 
e.g drop a Button, and from Properties section, enter "-fx-background-color," (syntax error : ',' instead of ';'). This is a CSS syntax error, the value is erased, and an error message appears in the message panel.

We also have the case of incorrect values, accepted by the API. For instance, negative height or width. This is accepted by the Fx API, but have unexpected effect (see DTL-4991). SB should warn the user in this case.
Comments
Duplicate of DTL-5714
17-04-2013
After discussion with Eric and Mo, we think this advanced error handling cannot be done in the 1.1 timeframe. For 1.1, we propose to only display an error message when there is an invalid value, replaced by the previous correct value. I'll create a new Jira for this (see Link).
03-08-2012