🚀 go-pugleaf

[Bart Loosvelt wrote:
"Now, suppose you start with an empty DATEFIELD value in your current
record. Enter a correct date in the DBEdit, don't press TAB, click the
SpeedButton with the mouse. It says that the DATEFIELD is still empty!
Click the TButton and it will correctly tell you the value you just
entered. Then, press the SpeedButton again and it will suddenly also
tell you the correct value.

This is because the last edited value is copied to the TField only
when the DBEdit looses focus. The SpeedButton cannot get the focus,
while the TButton can. ...
Maybe I'm weird, but this annoys me. Why can't we have one place where we
can retreive the most recent data from, instead we have to
- write data in the TFields if we want to modify a record at run time
- read the data from the Controls if we want to get the most recent
values "]

Things like speedbuttons that save resources by not accepting the focus do
have certain annoying side effects, one of which is that data-aware
controls ignore any clicks on them, since they don't know they should post
the data until they lose the focus.

However the way to fix it is just to call dataset.post when the speedbutton
is clicked - you don't need to read the control's text yourself.

Deborah Pate