>Antonio,
>(:ლ)
>
>in danger to bore you.

No, not at all!

>
>There Click is not called at all

Yes, I was going to correct myself, but you stepped in and rightly so. The click is trappable but there is not much we can do with it (because the control visual and data states are out of sync).

>So if there is no event (click) shown (asuming you are tracing all, I miss mouse moves) - there is no event. So there is no code runing. As simple as that. Thats what I've told you. The click is gone because the messagebox deals wtih the eventloop and returns without. You see it and you still argue about it. The eventlog tells you the truth. No line for click visible - no click run.
>

[snip]

>
>As I have told you, your UI approach (Messagebox and then proceeding to next object) is wrong. If there is something to say about the textbox it needs to stop and stay within the textbox. The design of VFP asumes you will not complain about some input and then leave the object (because if you are gone there is no more control by the text box at all.)

With this I strongly disagree, and there is nothing in the VFP design that designates that kind of behavior you're assuming. In fact, the design of valid() is such that we were given the chance to move focus specifically to any control in the form from there. And, of course, the purpose of a Messagebox() is not only to "complain".

>Again:
>Validation data on VALID event:
>All fine -> ready to leave -> no messagebox
>problem -> Messagebox possible -> stay in the textbox using RETURN .F. after messagebox.
>
>You have my example. Try to eventlog the checkbox from the textbox as you do with the listbox. It will end up the same.
>
>You might call it ugly, or a bug, but there is no change to it. Never ever.

Yes, I know that if I stay in the text box there will no problem. In this case, it's up to the user to decide, in face of the information the application gives him back. But if he decides to continue and got out of the box with a click on the list, his action won't be honored.

I wouldn't mind if the highlighted item remained the same. What cannot be is to give the user a visual information that does not correspond to the actual state of the control.

That is ugly and a bug.