Topic: acet-fscreen-toggle (solved)

[paulmcz]

Once I open Visual Lisp Editor, any subsequent drawing I open after that, I get following message:

Assignment to protected symbol
acet-fscreen-toggle
Enter break loop?

And on command line:

; User warning: assignment to protected symbol: acet-fscreen-toggle <- #<SUBR
@019d31cc acet-fscreen-toggle>

This goes on even after I close the editor.
If I close autocad and open again, everything is fine until I use "vlide" command again.

Any idea how to get rid of this?
Thanks.

[paulmcz]

I am not sure what this (pragma) should do but the problem seems to be fixed:

In Visual Lisp Editor:
Tools>Enviroment Options>General Options
in "SETQ to protected symbols" , "Prompt to enter break loop" was ON.
I changed it to "Error" and that fixed it.

Thanks anyway,
Paul.

[Kerry]

Better read up on that Paul.

[paulmcz]

Read what? Help files? I just did. Any dangers I should know about?

[Kerry]

Lets put it this way.

I 'protect' functions and global variables using a similar method mentioned by Luis.

If someone changed the optimum handling which by 'best practice' protects those values and methods and then complained to me because the Symbols were being overwritten by another application I would be forced to laugh in their face.

[paulmcz]

Kerry, I have no clue what caused this. I am well aware about the global variables and I never try to assign any values to known to me protected symbols. Before this, I didn't know and I still don't anything about "acet-fscreen-toggle". I am still investigating what this is all about. I appreciate any input that would shed some light into this for me.
I didn’t quite get Luis’s hints, maybe because I am not as advanced as many of you here.
The change I made in the Environment Options was just a desperate try to get rid of the message. In help file it says about this option:
Error This option prohibits modification of protected symbols. Any attempt to modify a protected symbol results in an error message.
Now, since I don’t get any error messages, I am puzzled even more than I was before. Apparently, I am not assigning values to protected symbols but when I turn the option
“Prompt to enter break loop” ON again, I get all the warnings back.
To tell you the truth, I am lost. If you know about some good reading about all this, I’d love to read it.
I just remembered that I installed and uninstalled “Dwggateway” plug-in recently. Do you think that it could be the problem? When I open acad,  I get this on the command prompt:
ACAD.RX Error: Unable to find file "C:\Program Files\Common
Files\DWGgateway\DGArxR2000.arx".
But everything seems to work fine. I don't get it.

[Kerry]

The FULLSCREEN command is available from my AC2002 to AC2006. I dont remember about AC2000.

The  FULLSCREEN command loads  fscreen.arx and runs (acet-fscreen-toggle).
Part of it's functionality is to reload menufiles. and associated MNL files

just to demonstrate how usefull the protection is run the fullscreen command, restore <run again>, then ;

load this from the IDE

(defun acet-fscreen-toggle () (alert "Pffffff"))

If you dont get a warning that an arx defined command is being redefined then it's aces wild.

Sounds to me like acet-fscreen-toggle is being redefined somewhere. It is most likely happening when one of your MNL {or similar} files is being reloaded when the menu swaps.


The best tip I can give is do a search on your system for ANY file that has the string acet-fscreen-toggle , then see if you can find the offending reloader/redefiner.

Second , perhaps change all your loaders so that they test for a file, or group of files, being loaded before reloading them.

good luck ..

[paulmcz]

Kerry, you are the man.
You were right, the fscreen.arx was the problem. I ran your tiny function and didn't get any error or warning message. There is fscreen.lsp file in Express folder, which loads fscreen.arx but that's all it does. Since I have no chance to see what's wrong with any .arx file, I reinstalled Expresstools. Now I can have default "Prompt to enter break loop" setting in Environment Options and everything works fine.
Thanks very much, I owe you one.
Paul.