Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Catching error information
Message
From
26/06/2018 18:49:40
Thomas Ganss (Online)
Main Trend
Frankfurt, Germany
 
 
To
26/06/2018 11:18:26
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01660874
Message ID:
01660896
Views:
61
>You could use AMOUSEOBJ() but I don't see any usefulness of recording last key or mouse info. IMHO ASTACKINFO() is much more helpful. It would already tell you which "Click" or other method caused it.

Agreeing totally on AStackinfo() being a great help.
Also all Asynch/Timer events should be logged - in case of often firing timers threatening to fill up the disk quickly, a round-robin table with enough entries for a small timespan can be used, always overwriting oldest record.

Had one case where Returning from OLE in asynch call manner could SOMETIMES (only when returning when some particular code was on the stack) mess up the stack, as some old routines still used privates. Joys of porting FPW and reusing ;-))

Not easy to guess as "messing-up code" already was gone from Astackinfo()...
Previous
Reply
Map
View

Click here to load this message in the networking platform