Most of the changes made have been discussed on the list. If you are
seeing more warnings than before, that is mostly because we turned on a
few more warning flags to help find bugs.
The reason for there being a lot of changes is that I have been
implementing a new properties API for objects. This has caused a number
of changes to a few objects (I haven't done all objects yet).
The current CVS version of dia is quite stable to use though. Due to a
number of bug fixes in the GDK renderer, it is actually more stable than
0.83.
Maybe we should release what we have at the moment even though there are a
number of half finished features present. The list of new features would
be something like:
- proper fit to page functionality for printing (and fit to multiple
pages).
- fixed some problems that caused crashes in previous versions when
loading certain files.
- toolbox uses wrap box, so button relayout when you resize the toolbox.
- New shapes in circuit and network sheets. A number of new sheets by
Cyrille.
There are a few others as well. The only downside is that the properties
interface is likely to change a bit more before it is ready, so if we make
a release now, we would not want others writing new objects with the props
interface yet.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Tue, 22 Feb 2000, segg wrote:
> James Henstridge wrote:
> >
> > I forgot to add that if you are seeing segfaults in dia-0.83, try the
> > latest CVS version (if you can access CVS). It has fixes for a number of
> > segfaults in 0.83.
> >
> > James.
>
> My current version is also very unstable, with segfaults.
>
> Suggestion, send cvs commit message to the mailing list.
> Even send "diff -u" files of every night compile.
> Some of the last week update where not compiling here.
>
> I am lost with what is going on.
> The update seams to says that every files have being modified
> at least two time in the last week.
> Unnescessary amount of warning about function without prototype???
>
> Are you doing a major overall change, making cvs an alpha version,
> allowing major contributors to follow current state.
>
> My reaction, given them the time to put in place this new option.
> Do not send bug report until change in cvs update is lower.
>
> The necessary information for me is probably lost in the noise
> of other readings or informations.
>
> Try to see those comments like positive inputs that may need to be
> address. If times, ressources and efforts balance the effectiveness.
>
> Gilles J. Seguin
>
