Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Full Blown VFP-like Command Window in VB
Message
De
02/05/2007 13:19:49
 
 
À
02/05/2007 12:08:24
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
01221709
Message ID:
01221876
Vues:
7
>>>>Actually you can, but it has practically no value. If you type a small program in the command window, and use ctrl-enter instead of enter, you can highlight what you have written, right-click and choose Exectute Selection. What happens "behind the scene" is that VFP creates a temp file, execute it and deletes it, this is also what happens when you use the Execscript() function.
>>>
>>>Hey Tore,
>>>It has practical function when coupled with debugging especially with oleautomation where access to good documentation is less:)
>>>Cetin
>>
>>As I wrote in message#1221745: I find it much easier to type MF+Enter, which expands to MODIFY COMMAND due to intellisense. This opens up a empty program window with no name. If my code works, I either save as a prg, or I copy-and-paste into the relevant place. and my command window doesn't get cluttered.
>
>Hmm I don't see how that works as interactive as command window is. There select and execute and you have a separate memory space, no? I meant to have created objects accessible as I try other commands:)
>Cetin

OK, but if you read the whole thread, the discussion really was about whether you could use if-endif constructs, and so on. I guess you agree that those kinds of tests are better suited for a temp prg, and not in the command window?
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform