[lazarus] IDE bug...
Mattias Gaertner
nc-gaertnma at netcologne.de
Wed Aug 21 09:43:09 EDT 2002
On 21 Aug 2002 22:32:59 +1000
David Creelman <dave at geko.net.au> wrote:
> > That's new. What type of artifacts and what controls?
>
> The artifacts aren't left behind. They only appear when moving. Should
> have mentioned that first.
> The artifacts appear when moving a control around on a form with other
> controls. When the bounding box of the moving control crosses the
> bounding box of another control, a line appears. Subsequent testing
> shows that this occurs with any control, not just TWinControl
> descendants.
If these lines are green horizontal or blue vertical then:
It's not a bug, it's a feature. They are called guidelines. (Delphi lacks them). They help you to align components to another. You can switch them off in the environment opts.
> Hope this helps. ....Also this one might not be a high priority I guess
> since the form designer does work, it's a cosmetic issue.
Huh, there are still some very nasty 'bugs' in the designer (e.g. capturing, keys, parent-child relationships, form names). They are simply not implemented, but there are no warnings, so you won't notice that sometimes things goes wrong. So I call them bugs.
> There is also a great deal of control redrawing going on. It flickers a
> lot.
Yep, I noticed this tomorrow. There were also a lot of mem leaks, which I fixed one minute ago.
It came together with some stuff on monday. Hopefully this can be fixed soon...
> > > Sometimes after dropping several controls on the screen, running,
> > > editing, running and editing, the selection gets fixed on a particular
> > > control and can't be moved off it.
> >
> > That's probably the designer capturing bug. I will try to fix it this week.
> >
>
> Just out of interest, what file is that in ?
Don't know yet. I had not yet the time to track it down. But probably designer.pp, controls.pp, gtkobject.inc or gtkcallback.inc.
Mattias
More information about the Lazarus
mailing list