"Greg M. Johnson" wrote:
> > The ability to copy the message window is apparently not working in 0.5> for Windows.
I also frequently have problems with it, seems that the ability gets lost when
the program is running for longer time.
Christoph
--
Christoph Hormann <chr### [at] gmxde>
Homepage: http://www.schunter.etc.tu-bs.de/~chris/
From: Pabs
Subject: Re: Copy pane not working for messages in 0.5
Date: 24 Oct 2000 22:07:09
Message: <39F64097.92D6C737@hotmail.com>
Christoph Hormann wrote:
> "Greg M. Johnson" wrote:> > The ability to copy the message window is apparently not working in 0.5> > for Windows.> I also frequently have problems with it, seems that the ability gets lost when> the program is running for longer time.
I investigated this phenomenon a while ago (can't remember which group it was in
prob p.w) & found that it is to do with the number of lines that the message
window can contain.
Say u do render 18-24 times in one session the copy pane thing won't work & the
horizontal scroll bar will die.
If u add say 50 lines of debug messages to each render then these things will
happen much earlier.
It manifests in the official version 3.1g as well.
--
Bye
Pabs
From: Greg M Johnson
Subject: Re: Copy pane not working for messages in 0.5
Date: 26 Oct 2000 08:05:38
Message: <39F81CC9.70BA0829@my-dejanews.com>
Pabs wrote:
> If u add say 50 lines of debug messages to each render then these things will> happen much earlier.> It manifests in the official version 3.1g as well.
Yes that was the scenario. I needed to see all those lines for my "debugging". If
it were just a word or two who'd really need to copy it?
From: Pabs
Subject: Re: Copy pane not working for messages in 0.5
Date: 26 Oct 2000 21:28:09
Message: <39F8D9D8.9107AB7B@hotmail.com>
"Greg M. Johnson" wrote:
> Pabs wrote:> > If u add say 50 lines of debug messages to each render then these things will> > happen much earlier.> > It manifests in the official version 3.1g as well.>> Yes that was the scenario. I needed to see all those lines for my "debugging". If> it were just a word or two who'd really need to copy it?
The most fustrating thing about this is not being able to see error messages that are
too long for one line.
The obvious way to get around it (until a bugfix is forthcoming) is to close POVWin &
reopen it unless you need the undo data, in which case you might save several versions
of the file.
Another good thing for 3.5 would be the ability to remember the undo history for open
files between sessions.
--
Bye
Pabs
de>
Homepage: http://www.schunter.etc.tu-bs.de/~chris/