Details of how this has been implemented (Taken from Parsys notification):
Formal Reply
JADE2018 introduced the idea of layouts for the Hierarchy browser. Layouts that are assigned to a particular schema and as the default layout for all schemas are now saved in the Jade user preferences ini file (User preferences dialog miscellaneous export preferences button).
Loading a user preference ini file will load any contained layouts if the schema of the layout is present or if the layout is the default.
The loaded layouts will replace any defined layout for the same schema or for the default layout.
Layouts for a schema not present will be ignored. Existing layouts where there is no such layout in the ini file will be retained.
Loaded layouts will only be installed when the OK button is clicked after the ini file has been read.
Loaded layouts will not be applied to any open window. The user must choose the required layout using the View menu facilities.
I don't have a current need for schema specific layouts...
However, if this needs to be preserved, a collection of layouts definitions could be part of user preferences (maybe even define a default), and then specific layouts applied manually to different schemas
Presumably you'd want this to become a part of your user preferences? In which case, would you be happy with the schema specific layouts being de-implemented? (as user preferences shouldn't contain schema/environment specific details).
Blake De'Ath
Details of how this has been implemented (Taken from Parsys notification):
Formal Reply
JADE2018 introduced the idea of layouts for the Hierarchy browser. Layouts that are assigned to a particular schema and as the default layout for all schemas are now saved in the Jade user preferences ini file (User preferences dialog miscellaneous export preferences button).
Loading a user preference ini file will load any contained layouts if the schema of the layout is present or if the layout is the default.
The loaded layouts will replace any defined layout for the same schema or for the default layout.
Layouts for a schema not present will be ignored. Existing layouts where there is no such layout in the ini file will be retained.
Loaded layouts will only be installed when the OK button is clicked after the ini file has been read.
Loaded layouts will not be applied to any open window. The user must choose the required layout using the View menu facilities.
I don't have a current need for schema specific layouts...
However, if this needs to be preserved, a collection of layouts definitions could be part of user preferences (maybe even define a default), and then specific layouts applied manually to different schemas
Presumably you'd want this to become a part of your user preferences? In which case, would you be happy with the schema specific layouts being de-implemented? (as user preferences shouldn't contain schema/environment specific details).