SDI & Filetabclose

SDI & Filetabclose

roland.r71
Collaborator Collaborator
830 Views
4 Replies
Message 1 of 5

SDI & Filetabclose

roland.r71
Collaborator
Collaborator

I've been bugged for years by this, and never came up with a solution, if any.

 

When turning on SDI (1), Autocad automatically issues a FILETABCLOSE

When turning it back off, (0) it will restore them

From the command line (in ACAD 2014) that is.

 

When running a lisp, which turns SDI on, does some stuff and turns it back off, the FILETABCLOSE comes AFTER the lisp has finnished. The fact that its already off doesn't seem to matter, nor does it restore it immediately from setting SDI back to 0 (as it would from the command line)

 

I tried storing en restoring the FILETAB state, but to no avail, as it happens after the lisp is done.

 

Anybody got a clue how to prevent or restore this?

 

Testing it is as simple as:

(setvar 'sdi 1)
(setvar 'sdi 0)
(command "FILETAB")

 

After running that (as a lisp file, dropped into the drawing) the filetabs are (still) gone.

Push the arrow up key 1 time (last command), and there it says: FILETABCLOSE

0 Likes
831 Views
4 Replies
Replies (4)
Message 2 of 5

hak_vz
Advisor
Advisor

Have no experience with using SDI, but after looking at this post,  it seams that your only option is to restart Acad.

Miljenko Hatlak

EESignature

Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
0 Likes
Message 3 of 5

roland.r71
Collaborator
Collaborator

It's not about the commands not working. Its about different behaviour between commandline & running lisp. The command gets automatically issued after the SDI is turned on.

In case of lisp it looks like the command gets catched, until the lisp is done.

 

So restarting acad won't help a bit to solve it.

0 Likes
Message 4 of 5

cadffm
Consultant
Consultant

Sorry, i guess most of us can not help because we haven't this problem (in other versions).

For example me: I can test in 2013 (not filetab command available) or in 2020/2021.

 

In your "lsp" you send a FILETAB command,

this sounds you want to see filetabs, this also sounds that you can not see a filetab after SDI set to 1

Is this right?

 

In 2020, I don't see problems

The only thing is: If you turn on SDI, it forces FILETAB=1 by re-setting to SDI=0

in this case it isn't a problem to add (command "_.filetabclose") to the Lisp to turn it off again.

 

Sorry

Sebastian

0 Likes
Message 5 of 5

roland.r71
Collaborator
Collaborator

When working on my previous 3.0 version, about 2-3 years ago, I already noticed it occured "sometimes", & mostly (Always?) using 2014, but not with 2018. Back then I never found a cause.

 

This time I was testing it again on 2014 and i noticed it Always happens when processing.

 

Further testing brought me to SDI as the culprit. But it looks like that's only the case with the 2014 version. I'm currently at work using 2019 and it doesn't have this problem. (turning on SDI leaves the filetabs in place)

 

For my simple test i put a filetab command at the end, which should normaly restore them, but the filetabclose (issued by setting SDI to 1 at the start) is somehow buffered until the lisp is done.

 

...but i found out i don't even need to turn SDI on, to have the fileopen command work correctly, but just no more then 1 drawing. (as fileopen will still switch to SDI mode internally)

0 Likes