View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017314 | Scribus | Styles | public | 2024-11-19 06:42 | 2024-11-19 18:47 |
| Reporter | utnik | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Product Version | 1.7.0.svn | ||||
| Summary | 0017314: scribus should (at least) warn when a style with inherited features is imported without its parent. | ||||
| Description | when i import a style from an existing .sla file, it imports only the features which are defined specific for this style and the name of the parent style (if there is one). but i don't see the cascade layers in the import window or any other warning when the imported style wont't be complete. | ||||
| Steps To Reproduce | - import a style which is based on another one from an existing .sla file (without importing its parent style) - apply the style to some text → the inherited features are missing | ||||
| Additional Information | there may be different sane solutions: - scribus detects the entry: 'PARENT=XX' and warns the user if the XX-style is not selected for the import - scribus detects the inherited features through the whole cascade and completes the style for the export (might be too complex…) - a minimal approach could be to show a hierarchical tree of styles in the import window. i.e. indented to mark the cascade as in the style manager | ||||
| Tags | No tags attached. | ||||
| Patch | No | ||||
|
|
good idea. a further idea: in the case the base style is not imported, it might be possible to ask the user to pick an existing style and "reparent" the style (apply the formatting that is specific to the imported style on top of the existing one: as an example the style "red" might still apply the color red, but on top of a different font) |
