Maximize Viewport & Grid Snap

[Herr Kuchen]

From the paper space tab: whenever I click "Maximize Viewport" to work in the model, I find that Grid Snap toggles ON, despite being OFF beforehand. Has anyone run into this problem? I'm aware of no settings that prevent this from happening. It's not a major issue, but pressing F9 to switch it OFF every time is a bit of a pain...

[BlackBox]

Interestingly, I cannot reproduce this - maximize viewport, grid snap is not enabled - what is happening instead, is that my other viewport turns black.

Apparently, the other viewport, which I did not maximize, and is locked, is set back at origin (0,0) and has to be unlocked, re-positioned and aligned with my 'frame' for that view (in model).

Very glad that I instead simply activate the Model tab when I need to work in model, as having to duplicate work like this would just set me off. Haha


Cheers

[CCarleton]

Very glad that I instead simply activate the Model tab when I need to work in model, as having to duplicate work like this would just set me off. Haha

I've apparently never known what maximize viewport is, although I have apparently found my way into this command by accidentally double clicking a viewport, but if I do that I just hit the undo button. I also just go to model space if I need to do work in it.

I also tried this out and didn't have it happen, but whenever I find variables that are changing and I don't want them to I use the variable reactor routine by Peter Jamtgaard. I believe that one started out as a savetime monitor, but I expanded it for pickfirst, dynmode, and filedia. No reason why you couldn't expand it to snapmode if you never want it on.

Edit:
My Variable Reactor Routine

;--------------------------------------;
;Routine to ensure designated          ;
;variables remain unchanged:           ;
;                                      ;
;Automatic save: 30 minutes            ;
;Pickfirst: 1                          ;
;Filedia: 1                            ;
;Dynmode: 3                            ;
;                                      ;
;Reactor by: Peter Jamtgaard           ;
;--------------------------------------;

(vl-load-com)
(setq VTFRXN (vlr-editor-reactor nil '((:VLR-sysVarChanged . VTF))))


(defun VTF (CALL CALLBACK)
  (if (and(= (strcase (car CALLBACK)) (setq str "SAVETIME"))(not (eq (getvar str) 30)))
    (progn
      (setvar "SAVETIME" 30)
    )
  )
  (if (and(= (strcase (car CALLBACK)) (setq str "PICKFIRST"))(not (eq (getvar str) 1)))
    (progn
      (setvar "PICKFIRST" 1)
    )
  )
  (if (and(= (strcase (car CALLBACK)) (setq str "FILEDIA"))(not (eq (getvar str) 1)))
    (progn
      (setvar "FILEDIA" 1)
    )
  )
  (if (and(= (strcase (car CALLBACK)) (setq str "DYNMODE"))(not (eq (getvar str) 3)))
    (progn
      (setvar "DYNMODE" 3)
    )
  )
)
(setvar "savetime" 30)
(setvar "pickfirst" 1)
(setvar "filedia" 1)
(setvar "dynmode" 3)

;--------------------------------------;
;Creates the command "unloadreactor"   ;
;which disables the reactor for        ;
;current DWG                           ;
;--------------------------------------;

(defun c:unloadreactor()
(setq VTF nil)
)

[Herr Kuchen]

Thank you for the input, I'll take a closer look at the proposed solution when I have some time to spare (perhaps the last week of the year, when things are slow). It is indeed curious... but again, not a big deal.