Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
When debugging, I want a noise when I get an error
Message
From
03/02/2005 11:38:32
 
 
To
03/02/2005 08:46:03
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP1
Miscellaneous
Thread ID:
00983171
Message ID:
00983516
Views:
26
Jim-

Thanks for posting the example. The problem is the function in the Skip For clause. Whether it's a bug or by design is debateable. I can make an argument for the latter even though my gut says the former. <s> The reason I think it might qualify as a bug is because using the same Skip For in the top level menu pad doesn't seem to have the same problem. Anyway, here's my example to reproduce it:
Set Asserts On

Define Pad _1fx0i0kvh Of _Msysmenu Prompt "FontSize" Color Scheme 3 ;
  KEY Alt+F, ""
On Pad _1fx0i0kvh Of _Msysmenu Activate Popup FontSize

Define Popup FontSize Margin Relative Shadow Color Scheme 4

*!* Comment the following lines to make the Skip For and
*!* to disable the Set Next Statement option.
Define Bar 1 Of FontSize Prompt "Smallest" ;
  SKIP For NotTopForm()

*!* Uncomment the following lines to make the Skip For and
*!* Set Next Statement play nicely together.
*!* Define Bar 1 Of FontSize Prompt "Smallest" ;
*!*   SKIP For 'O'=Type("_screen.ActiveForm") .And. ;
*!*   "TopForm" # _Screen.ActiveForm.Name

Assert .F.

* Just some statements to SET NEXT STATEMENT TO
x=3
x=5
?x

Procedure NotTopForm()
  If 'O'=Type("_screen.ActiveForm")
    Return "TopForm" # _Screen.ActiveForm.Name
  Else
    Return .T.
  Endif
Endproc
Previous
Reply
Map
View

Click here to load this message in the networking platform