in 29 Mar 2000, Lars Clausen wrote:
> On Wed, 29 Mar 2000, [EMAIL PROTECTED] wrote:
>
> > On 29 Mar 2000, Lars Clausen wrote:
> >
> >>
> >> In todays CVS Newsreport, we look at todays newest features in Dia. The
> >> Bezierlines are getting an overhaul, with a different creation scheme
> >> and guidelines that actually disappear when the line is not selected. A
> >> spokesman says 'This required some lower-level changes, such as adding a
> >> pen_up field to renderer and a toggle_guide render_op.
> >
> > Why did you have to export the pen_up field? It doesn't need to be read
> > from anywhere else, so it could go into the renderer implementation
> > (RendererGdk).
> >
> > Also, I'm not sure if this is the right way to do this. I think it would
> > be better if the object itself could somehow see it it was selected. Then
> > all the drawing logic goes into the object, and no modifications to the
> > renderer is needed.
>
> I was planning to have it in the other renderers, too. The idea is to have
> the objects know less about the renderers. Right now, the guide lines are
> drawn only for interactive renderers. I prefer to have the object tell the
> renderer 'This is a guide line', and the renderer decides what to do with
> it.
I have loose plans of making a general canvas to replace the Gnome Canvas
(about a million well-known gnome people wants Dia to use the Gnome
Canvas, but I don't). Dia would then be ported to this canvas. Then i
would need the renderer object to be very generic. Nothing in it that a
Gtk renderer api couldn't have.
> I thought about having the object know whether it was selected, but
> was worried about doing 'double accounting', and what would happen if the
> two got out of synch.
See my other mail suggestion.
/ alex
