Lots of goodness in the readme. Looking forward to checking it all out, but I
already noticed something (not knew, just bringing it up):

1. Run PgS
2. Ensure Document palette is open
3. Open a document -- it's structure is shown in the document palette
4. Open a second document -- (blank window) it's structure is shown in the
document palette
5. Switch to the first document using menu Window/Show Window/doc 1 -- the
document palette still shows the second document

Trying to use the document palette to select a chapter causes PgS to crash. It
appears to be tied to the current document, but fails to update the list and
so has an invalid chapter reference.

Tim Doty

Using Suse 10.0 for Athlon 64 with 1mb ram, 10gb swap (once Scribus went wild
and I interrupted after maybe a gb or more of swap was filled).
Somehow I had several browsers and other programs in /etc/preloads.d --no idea
how they got there. I had noticed in System Monitor (in the panel) that
almost all memory was tied up, mostly in "cached." Having no idea the
significance of what I was doing, I deleted a couple and found they still
worked when selected. I discovered it saved some memory. I ended up killing
all of the preloads and saved lots of memory.
I say this because it seems to relate to the action of PageStream 5.0.3.4
beta, which so far seems to be a very solid version! I tried your steps
below and had NO PROBLEM.
However, for several versions now, including this version earlier, I was
unable to load two files without the "blank page" you mentioned. I don't use
the Document Palette, but I would try to delete the blank window by selecting
the "x" and the OTHER window would close. It seems that focus was messed up.
But since Deron is looking to redoing the interface, I figure it would be
best to wait.
But since I got rid of all the preloads, the two windows both show and the
focus problem is not a problem, and it seems the Document Pallette is not a
problem either--as long as the page shows up!
One other comment: I have never seen PageStream use swap. It seems it will
crash before using swap. That might be related to speed decisions--I don't
know.
On Tue August 29 2006 6:51 am, Tim Doty wrote:
> 1. Run PgS
> 2. Ensure Document palette is open
> 3. Open a document -- it's structure is shown in the document palette
> 4. Open a second document -- (blank window) it's structure is shown in the
> document palette
> 5. Switch to the first document using menu Window/Show Window/doc 1 -- the
> document palette still shows the second document

--
No Jesus, No life. Know Jesus, Know life!  The beginning of Wisdom is
 the Fear of the Lord. The wages of sin is death, but the gift of God is
 eternal life through Jesus Christ our Lord!http://Quest4Life.net/glsmith/
http://MSGen.net/http://Quest4Life.net/http://JustForSomeone.com/

Hi Gary,

First of all, thanks for testing it out on your setup.

The preloads is trading memory for speed. Removing a preload will cause those
applications to load slower when first started, but that's all. (Well, if you
never ran the application there would be the additional difference of loaded
libraries I suppose, but that would cease being an issue as soon as you ran
one of those applications).

Technically PageStream doesn't use swap -- no program does. The OS manages
what is paged into swap (and paged out -- which it must for an application to
run). But it is all one big memory space. PgS linux has some memory leaks
which can occur in a runaway situation consuming all memory. From memory one
way to cause this is to use and edit tables (e.g., add/remove rows and
columns).

To the question at hand I find it interesting that you did not see the problem
as it is very repeatable here. I wonder what behavior other people observe.
Anyone else on this list try the steps I gave in 5.0.3.4?

Tim Doty

On Friday 08 September 2006 22:42, Gary Lee Smith wrote:
> Using Suse 10.0 for Athlon 64 with 1mb ram, 10gb swap (once Scribus went
> wild and I interrupted after maybe a gb or more of swap was filled).
> Somehow I had several browsers and other programs in /etc/preloads.d --no
> idea how they got there. I had noticed in System Monitor (in the panel)
> that almost all memory was tied up, mostly in "cached." Having no idea the
> significance of what I was doing, I deleted a couple and found they still
> worked when selected. I discovered it saved some memory. I ended up
> killing all of the preloads and saved lots of memory.
> I say this because it seems to relate to the action of PageStream 5.0.3.4
> beta, which so far seems to be a very solid version! I tried your steps
> below and had NO PROBLEM.
> However, for several versions now, including this version earlier, I was
> unable to load two files without the "blank page" you mentioned. I don't
> use the Document Palette, but I would try to delete the blank window by
> selecting the "x" and the OTHER window would close. It seems that focus
> was messed up. But since Deron is looking to redoing the interface, I
> figure it would be best to wait.
> But since I got rid of all the preloads, the two windows both show and the
> focus problem is not a problem, and it seems the Document Pallette is not a
> problem either--as long as the page shows up!
> One other comment: I have never seen PageStream use swap. It seems it
> will crash before using swap. That might be related to speed decisions--I
> don't know.
>
> On Tue August 29 2006 6:51 am, Tim Doty wrote:
> > 1. Run PgS
> > 2. Ensure Document palette is open
> > 3. Open a document -- it's structure is shown in the document palette
> > 4. Open a second document -- (blank window) it's structure is shown in
> > the document palette
> > 5. Switch to the first document using menu Window/Show Window/doc 1 --
> > the document palette still shows the second document