Hi Yves, Thank you for filing that issue. I have updated it.
Here is a suggestion for #2: Editing of these properties could be done in a way similar to the editing of Styles. Styles (in the JavaFX CSS section of the Properties accordion on the right side of Scene Builder) are edited with (I think) a Style Name TextField and a Style Value TextField. When you want to add an additional Style, you click the + and another row is added. Properties could be edited in a similar way, with a Property Key TextField and a Property Value TextField with a + button to add additional key-value pairs. Should I create a new issue for this? Thanks, Neil From: Yves JOAN <yves.j...@oracle.com> To: ngalarn...@abinitio.com, openjfx-dev@openjdk.java.net Date: 01/29/2014 02:38 AM Subject: Re: Scene Builder support for read-only Map Properties Hi Neil, I created https://javafx-jira.kenai.com/browse/DTL-6374 " Cannot load a layout using read-only map properties syntax" to track the loading issue. On question #2 may be it's worth having another JIRA: what kind of editing support would like to see ? Thanks Yves On 28/01/14 20:49, ngalarn...@abinitio.com wrote: Hello, When I use the read-only Map Property FXML syntax (described here: http://docs.oracle.com/javafx/2/api/javafx/fxml/doc-files/introduction_to_fxml.html#read_only_map_property_elements ), it seems to work, but causes the latest Scene Builder (2.0-b11) to not start. 2 questions: 1) Will read-only Map Properties be able to be round-tripped in Scene Builder sometime soon? 2) Will Scene Builder add editing support for these properties (perhaps similar to the support for editing Styles)? Thank you, Neil NOTICE from Ab Initio: This email (including any attachments) may contain information that is subject to confidentiality obligations or is legally privileged, and sender does not waive confidentiality or privilege. If received in error, please notify the sender, delete this email, and make no further use, disclosure, or distribution. NOTICE from Ab Initio: This email (including any attachments) may contain information that is subject to confidentiality obligations or is legally privileged, and sender does not waive confidentiality or privilege. If received in error, please notify the sender, delete this email, and make no further use, disclosure, or distribution.
