Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How to trap a change in a ListBox after a MESSAGEBOX()
Message
From
12/03/2016 07:56:42
 
 
To
12/03/2016 07:20:01
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Miscellaneous
Thread ID:
01632877
Message ID:
01632911
Views:
42
Lutz, I really do appreciate your advice and effort, but I think you're missing the point: I don't want to get rid of the MESSAGEBOX(). Please refer to the subject of this thread. What I want to know is if this is a problem with my code or a VFP's problem. Of course, it that is a VFP problem, then I'll have to take a different approach, but first I do want to sort it out.

Regarding your observations:

>#1 The WAIT WINDOW is misleading you. If you change to ? or debugout you will see the order the events will happen, while your WAIT WINDOW just show you the last message.

I'm sorry, but this is irrelevant. The WAIT WINDOW is fired when there is a change in the ListBox, and that's what I'm looking for (again, please refer to the thread subject). Outputting elsewhere does not change a thing.

>#2 The click event of the Listbox will never be called after the messagebox is raised.

Yes, that's the problem that brought me here: how is it possible that a click in an enabled control does not raise its Click() event?
----------------------------------
António Tavares Lopes
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform