<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Would still be better to draw two pages than 40-90 performance wise. It could make it<br><br>> To: scribus@lists.scribus.info<br>> From: jluc@no-log.org<br>> Date: Thu, 9 Oct 2014 09:02:08 +0200<br>> Subject: Re: [scribus] Keep master page logic when modifying page order<br>> <br>> Le 09/10/2014 08:06, Jog Lie a écrit :<br>> > By the way,<br>> > Scribus lack an event system which would signal when a page is visible or not.<br>> > With such an event system, we could bind some action into scripter and be much more effective at modifying the scribus behavior.<br>> > 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.<br>> <br>> The OwnPage attribute could be a step into that direction.<br>> <br>> Not strictly related to visibility, but it could state what pages an item belongs to<br>> and that would restrict the candidates to visibility related actions.<br>> But<br>> - a large item can belong to more than one page<br>> - as of today, there are situations where OwnPage is not the page an item<br>> belongs to (for example in some 'group' situations<br>> and in situations where the Y position is more than 1 page high)<br>> <br>> JL<br>> <br>> <br>> ___<br>> Scribus Mailing List: scribus@lists.scribus.net<br>> Edit your options or unsubscribe:<br>> http://lists.scribus.net/mailman/listinfo/scribus<br>> See also:<br>> http://wiki.scribus.net<br>> http://forums.scribus.net<br> </div></body>
</html>