(initget ...)

Dear Alls,
(initget 1 ) = not allow "enter"
(initget 2 ) = not allow "0"
(initget 3 ) = not allow "enter" & "0"
(initget 4 ) = not allow "- value"
(initget 5 ) = not allow "+ value" & "- value"
(initget 6 ) = not allow "0"
(initget 7 ) = not allow "enter" & "+ value" & "- value"
(initget 8 ) = cancel limit check
(initget 16 ) = not used
(initget 32 ) = cause get function that include a base point to display a
rubber band cursor or window that is highlighted rather than solid
(initget 64 ) = not allow Z coordinate in next getdist function
(initget 128 ) = allow arbitrary input (accept any "key word")
(initget ... ) = ???
(initget ... ) = ???
(initget ... ) = ???
(initget ... ) = ???
Any others ???
Best regards
Ade Suharna

 

See the developer help for more info. There are
theoretically 256 possiblities base on sums of
0, 1, 2, 4, 8, 16, 32, 64, and 128 although not
all modes are relevant for individual getxxx functions.
The developer help has a matrix of which shows
the applicabilities.

 

Hi Doug,how about
(initget "Yes No") = ????
(initget "") = ????
any comment ?

 

(initget "Yes No") => GetKword
(initget "Yes Si No")

 

Initget takes 2 arguments. The string argument
is for keywords. I prefer to store the keyword
string and use it for both the keyword prompt
and the initget string. Supporting multiple languages
in a single program could be counterproductive
since the keyword strings and program branching
become more difficult to maintain and debug.
I would rather have a localization scheme with
separately maintainable keyword and phrase
files.

I usually use initget with the bit argument in
addition to the keyword string but agree here
that no bit argument is necessary. The prompt
should make clear which is the default response.