Subject Re: [IBO] Non-db-aware DatePick ?
Author e9426420@stud4.tuwien.ac.at
I have tried to find the problem but I couldn´t do it. :(
I have traced the code through IBC_Date.IMP, TIB_CustomDate and TIB_CustomE=
dit

here are some of my findings
The procedure TIB_CustomEdit.Change is also called twice
TIB_CustomDate.KeyPress is only called once
The call stack looks like this

TIB_CustomEdit.Change
TIB_CustomDate.WndProc(???)
TIB_CustomDate.WndProc(???)
TIB_CustomDate.KeyPress(???)

am I right that TIB_CustomDate.WndProc calls TIB_CustomEdit.Change ?
but I don´t understand the process of the this WndProc procedures and there=
messages
(the Message.Msg numbers are 48401, 45111, ...)
Where can I find information what these messages mean.
Can somebody help me? I am not very familar with these components things.

thanks
Oliver

>I suggest you get in under the hood and find out what the problems are.
>See IBC_Date.IMP.

>>I used the OnChange event and in the event-procedure IB_Date.text has str=
ange values. In addition to >>that the OnChange event is always called twic=
e if I press a number key to change the date (not if I >>click the open cal=
endar). This is also true for the bound control.
>>
>>to explain the strange values look at this onChange proc
>>procedure TForm1.DateTimeChange(Sender: TObject);
>>Begin
>>Showmessage('.Text='+dtp.Text+' .Edittext='+dtp.EditText)
>>end;
>>
>>my Dateformat is dd.mm.yyyy
>>if I change 27.11.2001 to 26.11.2001 (overwrite the 7)
>>2 messageboxes appear
>>1st: .Text=2..1..001 .Edittext=2.11.2001
>>2nd: .Text=26.11.2001 .Edittext=26.11.2001
>>
>>the second time OnChange is called everything is fine