Should the list be just for development conversations ?

>No this list is for users comments, problems, requests and general >information. The is a non-public list for developers.

What Michael meant to say was "There is a non-public list for developers". Meaning that you can post anything you like here (related to Lazarus of course).

Shane

Does that mean that you type slow or think fast? :-)

Shane

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.

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.

There is also a great deal of control redrawing going on. It flickers a lot.

Just out of interest, what file is that in ?

Also, would you rather I put these into the bug tracker ? Should the list be just for development conversations ?

Hi All,

I've been playing with the latest versions of Lazarus and have run into one or two IDE issues.

Using most recent source, gtk, X 4.2 on Mandrake.

About every forth or fifth mouse click is missed. This can be seen by dropping a calender on a form, running and clicking on the year scroller many times. Not all of the clicks get through. Don't know why this is happening.

There are some rectangular artifacts left when moving TWinControl descendent controls around on the screen.

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.

Sorry I can't get more details. Hope this helps a bit. Great work !

Cheers
DC

Shane Miller wrote

What Michael meant to say was "There is a non-public list for developers". Meaning that you can post anything you like here (related to Lazarus of course).

Hee hee. That's what I get for thinking faster then I can type. :-)

David Creelman wrote

Also, would you rather I put these into the bug tracker?

You can put it in both places. In fact if you add a bug to the bug tracker that bug is automatically sent to this list as well.

Should the list be just for development conversations ?

No this list is for users comments, problems, requests and general information. The is a non-public list for developers.

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...

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

I spotted two reasons:
1. The gtk-interface sometimes does not get a mouse release event, although the mouse press event was there. Perhaps a capturing problem.
2. The gtk-interface sometimes gets a double click instead of a single click. Perhaps a sharing gdkwindow problem.

So, there are at least two bugs. I have to gather more information, so I don't know when this will be fixed.

There are some rectangular artifacts left when moving TWinControl descendent controls around on the screen.

That's new. What type of artifacts and what controls?

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.

Mattias

Good to know we have a telepath on the team!

Mattias Gaertner wrote

Yep, I noticed this tomorrow.

Martyn Ranyard
Free Software Advocate

jabber -
icq - 122500800
irc - Joran on oftc
msn -
e -