On Wed, 11 Apr 2001 22:13:18 -0500, āJoe Hezinaā <joshez@yahoo.com>
wrote:
10 crashes in hour??
Yeah, they are manipulation lots of images and big background.
Iāll make sure that they have full window dragging, but Iām get
the feeling it already is. Thanks for the tip.
They often get crash just editing resources.
Iām in PhAB all day long and get crash only when I do something that I know
not to do (and do it anyway), like the above mentioned opening new app. w/o
closing the previous, etc. Otherwise it is actually pretty solid, Iād say,
lot better with Patch B release, and Iām quite happy with it.
There is one thing - the Patch A crashed a lot when full window dragging was
enabled in PhAB. I disabled that (outline dragging) and since then I donāt
have the ādragg-and-crashā problem. Perhaps something to try.
Joe
āMario Charestā <> mcharest@nozinformatic.com> > wrote in message
news:> 3ad35788.20871641@inn.qnx.com> ā¦
They get 10 crashes an hour hereā¦
Itās real bad, close to unuasable. Strange cause I would
have expect QSSL to show more interest in fixing this.
On Mon, 9 Apr 2001 22:44:28 -0500, āJoe Hezinaā <> joshez@yahoo.com
wrote:
I reported some and have some more >
One for now: If you go to open PhAB application without closing the one
loaded first, there is good chance the PhAB will crash.
What really bugs me is the one I reported before - you can not print the
module tree. PhAB will crash every time you try. It is bad one - Iād love
to
have the tree printed out ā¦
Joe
āMario Charestā <mcharest@antispam_zinformatic.com> wrote in message
news:9at293$5m4$> 1@inn.qnx.com> ā¦
Got some phab core dump. The guy behing me got two in the same day.
He
two crash seems unrelated as far as what he was doing. Once it happen
while
dragging,
the other time it was editing resources (font size).
This was NOT though phindows as everybody doing PhAb is now working
directly on a machine.
People here seems to have lots of trouble with phab. No one takes the
time
to gather info to help QSSL fix the problem >
\