Statalist


[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

st: RE: RE: RE: user input as scalar value


From   "Nick Cox" <n.j.cox@durham.ac.uk>
To   <statalist@hsphsun2.harvard.edu>
Subject   st: RE: RE: RE: user input as scalar value
Date   Thu, 26 Jun 2008 15:26:06 +0100

Not really. 

With this method, Stata waits for you to submit input. If you just press
Return, then the local macro will be empty. Depending on the program,
that is either fine -- there is a default -- or probably a fatal error
that will show up sooner or later. 

This is up to the programmer. If the programmer wants a dialog box, or
users really expect that, then that's clearly another way to proceed. 

Similarly, writing a program with options is another way to proceed. 

I had to look this up in the help. In several years' Stata programming,
I am not sure I have ever used it. So what, you may well ask. The point
is that it's there for those who want it. 

Nick Cox 

Martin Weiss

Is it at all possible to add a dialog box to this? The request could
easily
go overlooked...

Nick Cox

Yes, you can do this. 

A canonical exchange within the do file is 

di "Enter value for foo: " _request(foo) 

after which local foo contains the value typed. 

See -help display-. 

I'd rather take arguments from the command line, but that's a matter of
taste. 

Rajesh Tharyan

I have a do file, wherein I have a few scalars which I am using to
expand,
loop , as cutoff limits etc. Is it possible to have the do file 
prompt the user to input the value of the scalar, so that I do not have
to
make the changes to the do file.

Suppose I had a do file like

Scalar a=5
......
Expand a
.......

Can I get stata to prompt the user like 

Enter the value for expansion : 
that input then gets stored as a
The code executes..

*
*   For searches and help try:
*   http://www.stata.com/support/faqs/res/findit.html
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/



© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index