Scheme entries that include colons in their codes do not display or save correctly #20
Description
PSICAT uses a colon to delimit the scheme ID and scheme entry code in the String used to identify a scheme entry.
SchemeEditor automatically creates the code for a new entry by making all characters lowercase and replacing spaces with commas. Colons are left as-is, so an entry named "Texture: Porous" would result in the code "texture:,porous". This breaks logic to split scheme ID and entry code, which assumes only one colon.
Workaround is to manually edit generated codes in SchemeEditor, removing colons.
The straightforward fix is to omit colons on automatic code generation.