Would still be better to draw two pages than 40-90 performance wise. It could make it
> To: scribus at lists.scribus.info > From: jluc at no-log.org > Date: Thu, 9 Oct 2014 09:02:08 +0200 > Subject: Re: [scribus] Keep master page logic when modifying page order > > Le 09/10/2014 08:06, Jog Lie a ?crit : > > By the way, > > Scribus lack an event system which would signal when a page is visible or > > not. > > With such an event system, we could bind some action into scripter and be > > much more effective at modifying the scribus behavior. > > There is a lack for page visibility api as well. It is non sense to draw > > the whole document if we don't even see it. <-> BIG performance boost. > > The OwnPage attribute could be a step into that direction. > > Not strictly related to visibility, but it could state what pages an item > belongs to > and that would restrict the candidates to visibility related actions. > But > - a large item can belong to more than one page > - as of today, there are situations where OwnPage is not the page an item > belongs to (for example in some 'group' situations > and in situations where the Y position is more than 1 page high) > > JL > > > ___ > Scribus Mailing List: scribus at lists.scribus.net > Edit your options or unsubscribe: > http://lists.scribus.net/mailman/listinfo/scribus > See also: > http://wiki.scribus.net > http://forums.scribus.net -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.scribus.net/pipermail/scribus/attachments/20141009/ad5fd888/attachment.html>
