View Issue Details

IDProjectCategoryView StatusLast Update
0000403ScribusStylespublic2005-04-16 09:02
Reportermalex Assigned Tofschmid  
Status closedResolutionfixed 
Platformi386OSLinuxOS Version2.6
Product Version1.3.0cvs 
Fixed in Version1.2.2cvs 
Summary0000403: Edit>Edit Styles>Append does not allow to choose the style to import like template append does.
DescriptionThere should be consistency between the ways of importing styles and templates from older documents. Right now it is possible to choose template to import, but not style. All the custom styles from the old document are imported automatically once the file to open is selected.
Steps To ReproduceCreate several custom styles.
Save styles.
Create a new document.
Edit>Edit Styles>Append, choose the previous document.
Result: All styles are appended.
TagsNo tags attached.


related to 0001710 feedback A way to manage stylesheets when inserting a page from another document 
child of 0003837 acknowledged Metabug: Master pages/Page templates 



2004-04-14 21:18

administrator   ~0001067

Will not change this behaviour since i'm planning to implement nested Style so
importing only a single Style would be dangerous to loose the Style the imported
Style depends on.


2004-04-15 16:34

administrator   ~0001080

Nested styles is a great idea. However, different style trees should still be imported independently. So, we can close this bug now if you will make sure that that tree import independence will be available. Do you have any objections to that?


So, if I import Style2.2.1 then only the tree starting with Style2 root is imported, but not Style1 tree. This is my point for this bug and for your future implementation if that's the way you are planning it.


2004-04-15 16:37

administrator   ~0001082

Yes, only selected trees should be able to be imported, and in the current case, single styles. It makes sense to leave this for the moment though.


2004-04-15 16:42

administrator   ~0001084

Like I said, if Franz implements the new nested styles in the way that Craig and I agree on than this bug is not worth spending time on right now. Franz, please verify your stance on this and close the bug for good. Thank you.


2005-04-08 07:31

viewer   ~0004158

bumping to 1.3 as this is on the roadmap


2005-04-12 09:53

administrator   ~0004233

Resolving that Bug now, as the primary issue is fixed now, all other things should go into the related Bugs.

Issue History

Date Modified Username Field Change
2004-04-01 17:23 malex New Issue
2004-04-14 21:18 fschmid Status new => resolved
2004-04-14 21:18 fschmid Resolution open => won't fix
2004-04-14 21:18 fschmid Assigned To => fschmid
2004-04-14 21:18 fschmid Note Added: 0001067
2004-04-15 16:34 malex Status resolved => feedback
2004-04-15 16:34 malex Resolution won't fix => reopened
2004-04-15 16:34 malex Note Added: 0001080
2004-04-15 16:37 cbradney Note Added: 0001082
2004-04-15 16:42 malex Note Added: 0001084
2005-02-22 07:38 plinnell Relationship added related to 0001710
2005-04-08 07:31 plinnell Note Added: 0004158
2005-04-08 07:31 plinnell Product Version 1.1.6 => 1.3.0cvs
2005-04-12 09:53 fschmid Status feedback => resolved
2005-04-12 09:53 fschmid Resolution reopened => fixed
2005-04-12 09:53 fschmid Note Added: 0004233
2005-04-12 09:57 fschmid Status resolved => confirmed
2005-04-12 09:57 fschmid Status confirmed => resolved
2005-04-12 09:57 fschmid Fixed in Version => 1.2.2cvs
2005-04-16 09:02 cbradney Status resolved => closed
2006-05-18 19:32 christoph_s Relationship added child of 0003837