Generate roof plugin

[sjb007]

623 KB (638,192 bytes)
SHA256: E97BB8647D61BC78D8F48DBE2EC9A5ADD9EF92CC57C18EB20A558042F758380B

I've tried removing all my other plugins to see if it is a conflict, but it still didn't work.
I've tried both MediaFire and SourceForge versions. Still didn't work.

Only thing I can think of that is left is my SH3D is version: 7.0j (a patched version from Emmanual as I recall) on Windows 10.

[sjb007]

Ah. I see I'm a couple of patch releases behind. I'll update and report back.

[sjb007]

Nope. I'm now on the newest 7.0.2. No plugins apart from the roof generator. I have no Tools menu at all, and the libraries in the about dialog is not showing anything.

[Puybaret]

Sorry Dorin, but it doesn't work on my side too, with the log reporting this:

Code: Select all

Invalid plug-in jar:file:/Users/manu/Library/Application%20Support/eTeks/Sweet%20Home%203D/plugins/GenerateRoof.sh3p!/generateroof%2FApplicationPlugin.properties:
Can't find resource for bundle java.util.PropertyResourceBundle, key name

Probably, an issue in a properties file (if you don't use English, it may not happen).

[sjb007]

I'll post a theory. In the previous version all the properties were in a default unlocalised poperty file. In this version many of the values were moved into an en_US property file. I'm a Brit, so my localisation is en_GB. Usually applications fall back to en_US, but it seems you are not doing this, so for anyone not using en_US, fr, it, or zh_CN, the plugin will not work. Another option would be to rename the property file to just be en, not en_US.

[sjb007]

Confirmed!

I copied the en_US to an en file rezipped and it started working. I strongly advise you to have a fallback to en_US in the code.

[dorin]

OK!
New version 3.1.1

Try to fix a bug which prevent loading plugin on some OS with global language settings other than en_US.
Hope this time will work for everyone.

Also on Source Forge

[Puybaret]

Thanks, it works now.
The [font=courier new]ApplicationPlugin.properties[/font] file is the default properties file for all languages and should contain all the properties you may use in the plug-in.
If you want to specify some different values for some properties like translation or special values for the English in the USA for example, you can create additional properties files with other suffixes like [font=courier new]_fr[/font] or [font=courier new]en_US[/font], but you should not add new properties in these files.

[sjb007]

Yup. For me too.

[KelvinUceta]

Wow Dorin,

Didn't tried it yet but will use it for sure!

Great.