Yes I agree, those are rather input sub-types. In the long run I will certainly want to change this and I'm currently testing better patterns for front-end architecture (modularity, components, better separation of concerns), but it will probably require rewriting 75% of the front-end (JS) code (which is kind of an organized mess atm), so not for now yet.
As for the setting type change, yes I noticed that & it's already fixed in my local version. It was newly introduced in 0.5 as a result of template simplification. Basically I've modularized the views (HTML) & backend API (PHP); now there's only the JS left. You can fix it with this patch:
custom_settings_0.5_patch_typechange.zip (Size: 1.59 KB / Downloads: 4) (simply extract to plugins folder).
As for the setting type change, yes I noticed that & it's already fixed in my local version. It was newly introduced in 0.5 as a result of template simplification. Basically I've modularized the views (HTML) & backend API (PHP); now there's only the JS left. You can fix it with this patch:
custom_settings_0.5_patch_typechange.zip (Size: 1.59 KB / Downloads: 4) (simply extract to plugins folder).