Is there a way to enable grips throughout all pages and projects per user? If I turn them on, they are only active for one page. If I navigate to another page, they are disabled again.
For child symbols, the cross references automatically show up. We don't want to see this. Is there a way to turn these off completely?
If I have a set of object snaps selected and I toggle (F3) o-snap off, it re-prompts me every time I turn it back on. I would like the o-snap selections to remain when I toggle. Is this possible?
Grips are disabled intentionally to avoid problems that can occur when things like symbols and wires are stretched, inadvertently or otherwise. So I would not recommend turning them on.
To suppress cross references at child symbols, select Project Manager > Options > Project Options > Display Formats and edit the Device Cross Reference format. Uncheck the box for "Display Child Symbol Cross-referencing".
Regarding the object snaps toggle, do you mean the settings dialog appears when you turn object snaps back on? Does this happen in the same session or only after restarting promis.e? Does the problem happen in plain AutoCAD as well? I'm wondering if this is a behavior specific to certain AutoCAD versions, it does not happen for me in AutoCAD 2010.
With the o-snaps. Yes the dialogue re-appears. In some cases the previously checked snaps are still active and it does not re-prompt, but it seems if I'm in the process of adding a symbol by Device ID, it will prompt for o-snaps and all will be cleared. It does not seem to happen in autocad becuase of no placing symbol by device id function. I run Promis*e off of Autocad 2012...
As an update on this, Promis*e seems to reset OSMODE to 0 and thus causing the prompt when toggling F3 back on. (I use my OSMODE at 55 always). I think it is happening most when a page is just opened and the OSMODE hasn't been set yet in that instance.
Aaron, I am now running on AutoCAD 2012 like you, and my OSMODE value is preserved when I restart promis.e. Please set OSMODE as desired, then restart promis.e. Type OSMODE at the command line periodically as you work to check the value to try to pinpoint when it gets reset.
I still can't seem to get it to forget the OSMODE value. Here's what I did:
However, I am running a 32-bit system and I did find some mention of OSMODE problems related to 64-bit systems on the Autodesk forums The workarounds presented there included:
Might there be some custom LISP routine you're using that is setting OSMODE to 0?