Topic: setvariable fails in 2018, works in previous versions?

[Jeff_M]

Riddle me this.... at the command line in 2018 this works.

Command: DYNMODE

Enter new value for DYNMODE <-3>: 3

Command: SETVAR
Enter variable name or [?] <DYNMODE>:

Enter new value for DYNMODE <3>: -3

Command: (setq *doc* (vla-get-activedocument (vlax-get-acad-object)))
#<VLA-OBJECT IAcadDocument 00000000293ddd08>

Command: (vla-setvariable *doc* "dynmode" 3)  ;;<<<<<works in earlier versions
; error: Automation Error. Error setting system variable;;; yet 2018 throws this

[ronjonp]

Same behavior here .. although (SETVAR 'DYNMODE 3) works fine.

[Jeff_M]

Thanks, ronjonp!

[Lee Mac]

Does it work if you supply a variant?, e.g.:

Code - Auto/Visual Lisp: [Select]

1. (vla-setvariable *doc* "dynmode" (vlax-make-variant 3))

[ronjonp]

Does it work if you supply a variant?, e.g.:

Code - Auto/Visual Lisp: [Select]

1. (vla-setvariable *doc* "dynmode" (vlax-make-variant 3))

Command: (vla-setvariable *doc* "dynmode" (vlax-make-variant 3))
; error: Automation Error. Error setting system variable

[ChrisCarlson]

Interesting, modifying it to vla-GetVariable works as expected.

[dgorsman]

Don't have it installed here, so another diagnostic stab in the dark - what does the "available" function say (I think it's vlax-property-available-p...) about read-write status?

[BIGAL]

Just a dumb suggestion is it 3 or "3" some bright spark may have changed something.

Did not work on civ3d 2018