Giuliano Colla ha scritto:
The FBaseBounds are sometimes wrong in 0.9.24. This has been fixed in
svn.
Did you test with the current 0.9.25?
Yes. I saw no changed behavior since r 12699 until your modified it in
r 13219.
However, as I have an app which shows the problem, I can try to trace
what happens with FBaseBounds, and provide more information.
I've made my test, checking just FBaseBounds.Top, because it's the one
relevant in my app.
What happens is the following:
The two widgets created with the form, which are top aligned, have the
same value for Top and for FBaseBounds.Top (i.e. 1 for the first and 43
for the second).
All the other widgets are created run-time, and initially set bottom
aligned, have the correct value for the Top property (corresponding to
their position) and 0 in FbaseBound.Top.
So when one of them is set top aligned, if FBaseBounds.Top is used, 0 is
< 1 and the widget goes above the first one, instead of below. If the
top property is used instead, the widget goes in the right place.
I didn't investigate further, but it seems to me that if a widget has a
top property of 350 and FBaseBound.top = 0 and if FBaseBound.top must be
used to know where the widget is, there must be a bug somewhere.
Giuliano
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
