Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
When debugging, I want a noise when I get an error
Message
De
03/02/2005 08:46:03
 
 
À
03/02/2005 01:31:57
Nancy Folsom
Pixel Dust Industries
Washington, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP1
Divers
Thread ID:
00983171
Message ID:
00983423
Vues:
26
Nancy:

"SET NEXT STATEMENT" is disabled by the following line:
DEFINE BAR 1 OF FontSize PROMPT 'Smallest' SKIP FOR NotTopForm()
where I have
PROCEDURE NotTopForm()
   IF 'O'=TYPE("_screen.ActiveForm")
      RETURN "TopForm" # _SCREEN.ACTIVEFORM.NAME
   ELSE
      RETURN .T.
   ENDIF
ENDPROC
Note that the problem only occurs when I have the "SKIP FOR" phrase -- if removed, I have no problem.

Jim

>Jim-
>
>>I've just been doing "DO Main.PRG" from the command line.
>>
>>Tracing through this, I found the program call which appears to be the culprit. If I skip it, I have no problems (that is, "Set Next Statement" is enabled, as desired).
>>
>>The program created a menu, um, the only way I knew how to at the time, and by that I mean before I knew about menu builders and how to get the menu into my top-level form. I'll see what I can do about re-working that, but at least I know what the cause was.
>
>That's very interesting. Hadn't ever run across that. Learn sumptin new every day, what? Anyway, if it's not too complex to explain, what seems to be the thing that disables the set next statement?
Jim Nelson
Newbury Park, CA
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform