[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: KSpread: Style Storage
From:       Stefan Nikolaus <stefan.nikolaus () kdemail ! net>
Date:       2006-06-22 11:10:54
Message-ID: 200606221310.58007.stefan.nikolaus () kdemail ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 22 June 2006 09:45, Stefan Nikolaus wrote:
> On Thursday 22 June 2006 09:34, Stefan Nikolaus wrote:
> > On Wednesday 21 June 2006 20:46, Robert Knight wrote:
> > > I think splitting the style up is essential because style regions will
> > > overlap.
> >
> > Related question: how should named styles be handled with the splitted
> > attribute approach?
>
> Ah, forget it. Creating a container with the name and pointers to the
> associated substyles will do.

Jumping back and forth: This is not as easy as it seems at the first quick 
look.
Consider the following scenario: You assign a named style to a region. It's 
splitted and its attributes get inserted into the tree, each with a 'time id' 
attached. Followed by some direct cell style changes. If you now alter the 
named style, e.g. define an additional attribute, you have to know to which 
region the named style is applied and you have to insert the new attribute 
with the correct 'time id'.
So, keeping track of the substyles with the regions, they are applied to, and 
with the 'time id' will be necessary.

Bye,
Stefan

[Attachment #5 (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]