If you are saving the diagrams compressed (the default), gunzip them:
cat diagram.dia | gunzip -c > diagram2.dia
Now search through the diagram, and see if there are any occurences of the
words Inf or NaN. If there are, change them to some other value, as these
should not be written to the save files.
There are also a few bugs in the gdk bezier curve renderer which may be
causing the problem. If you can, grab the file app/render_gdk.c from CVS
and compile dia with that.
Alternatively, grab the latest CVS version of dia. There are a few
diagrams that crashed with dia-0.83 that don't with the latest CVS, so it
may be worth trying it.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Wed, 16 Feb 2000 [EMAIL PROTECTED] wrote:
> Excellent program, gentlemen!! I love it and intend to continue to use it
> big time.
>
> I've already read down the list and have seen that this problem has cropped
> up with other users. Here is my version - I've tried all suggestions I've
> seen on the list.
>
> After creating and printing a couple of flowcharts (individually), I saved
> them. I attempted to reopen them to edit and reprint them, crasho goes dia.
> No warnings, etc. I can't seem to get dia to reopen these files again at
> all (or even keep running after attempting to reopen them).
>
> Originally, I thought this was a rev. 0.80 problem (had the rpm originally),
> so I revved up to 0.82 via source tarball. Same problem. Then I revved up
> libxml as suggested to 1.8.6 (via rpm). My current Dia is rev. 0.83
> compiled from the mdk source rpm. Same problem at 0.83.
>
> My system is a 92MB RAM i586 200 MHz RH6.1 standard box (with updates per
> RedHat) and as noted, I've upgraded to libxml-1.8.6. The saved files look
> fine if you open them in text editor. Typical xml-like stuff.
>
> Any hints? Would anyone care to take a look at my saved diagrams and see if
> they can reproduce this problem? Note, these are not tiny flowcharts, but
> they're also not huge 30 page jobs, either. I tried saving a couple of tiny
> flowcharts and these do not show the problem - it's only when I get around 1
> page of saved flowchart that I start to see problems.
>
> William F. Helke
>
