Topic: Question about "initget"

[CAB]

In ACAD2006

Code: [Select]

Command: (initget 1 "D E F")
nil

Command: (getkword "\nChoose a Letter [D/E/F]: ")

Choose a Letter [D/E/F]: e
"E"

Command: (getkword "\nChoose a Letter [D/E/F]: ")

Choose a Letter [D/E/F]: a

Invalid option keyword.

Choose a Letter [D/E/F]: f
"F"

[MeasureUp]

In ACAD2006

Code: [Select]

Command: (initget 1 "D E F")
nil

Command: (getkword "\nChoose a Letter [D/E/F]: ")

Choose a Letter [D/E/F]: e
"E"

Command: (getkword "\nChoose a Letter [D/E/F]: ")

Choose a Letter [D/E/F]: a

Invalid option keyword.

Choose a Letter [D/E/F]: f
"F"

Thanks CAB, have you tried (initget 1 "A B C") first, then (initget 1 "D E F") and (getkeyword "D/E/F: ")?

[CAB]

Oh it ignores the second initget. 

[CAB]

In VLIDE it behaves normally. 

[MeasureUp]

In VLIDE it behaves normally. 

I can't find any errors by using VLIDE.
And that is why I don't mention of using it.
From the command prompt, the 1st set of "initget" looks fine:

Code: [Select]

(initget "A B C")
(setq ABC (getkword "\nSelect A/B/C: "))
Select A/B/C: -> A
"A"
but the 2nd set has a problem:

Code: [Select]

(initget "D E F")
(setq DEF (getkword "\nSelect D/E/F: "))
Select D/E/F: -> D
Invalid option keyword.

[Kerry]

What happens if you put the code into a function body and load the file containing it and run the function.

Not many of us would expect to enter the code line by line at the command line ...