Emmanuel Puybaret

i didn´t check your code but maybe you could add a HomeFurnitureGroup instance containing the different cabinets to solve the problem. You can also group multiple actions in one compound undoable action calling beginUpdate / endUpdate methods (see HomeController class for examples).

Instead of removing the property shelfBoxes#364, could you leave it, remove the two trailing blanks and try if it works? Thanks for your patience...

It´s probably because of the trailing blanks (see IllegalArgumentException thrown in DefaultFurnitureCatalog.js (sourceforge.net). Removing them should fix the issue. The split method works differently in Java and JavaScript and there should be an additionnal call to trim before split to avoid this issue.

They should show up on a print of the 2D plan. They will not appear on a 3D print. I usually take screen shots of the 2D plan (usually zoomed in to the area I'm interested in) and then print the screen shot. This ensures that what-you-see-is-what-you-get. gary

Thanks for trying the not very intuitive tool PropertiesToJson and reporting this issue. Could you check if the value of the property shelfBoxes#364 in .json file is the same as shelfBoxes#364 in .properties file?

Door plugin

Ticket moved from /p/sweethome3d/d-models/734/

As plug-in developers generally do, source code is included in the plug-in itself and I just checked that .java files are present along with .class files in CabinetMaker plug-in. On my side, I noticed an issue in French translation and maybe other languages : _fr.properties files are not ISO-8859-1 encoded as they should be, and the French accuented letters are not always correct. It would be nice to fix it.