Notice for Xref is unloaded

[Automohan]

Need solution for this - we usually unload some xref's for better performance of the file to modify

Before print click, need a warning message should appear that some of the xref's are unloaded do you need to load it

& before print

Mistakenly doing publish with unloaded xref's & wasting of time.......

thanks

[scot-65]

Perhaps some conceptual thinking...

Determine the number of xrefs in a given file at startup.
Determine the state of each xref (in this instance unloaded).
Save this information in the dictionary as a list <<may not be necessary...>>.
Set one of the USER variables to the value of the unloaded xrefs.
Write to MODEMACRO this value:
(setvar 'MODEMACRO "$(if,$(=,$(getvar,USERI1),0),Loaded,Unloaded)")
<untested>
Build a command reactor to intercept the XREF command; specifically
CommandEnded/Canceled/Error to <<rebuild dictionary and>> update USERI1.
Optional sub-section in command reactor to intercept PLOT, PUBLISH, etc.
and check the value of USERI1 and invoke an alert.

The USER keys, for the most part, were originally designed to store custom
information for the purpose of displaying the custom value somewhere in
the UI. Suggest setting the user key every time a drawing is opened in case
a third party program interferes (I was guilty of this at one time).

???

[ronjonp]

Maybe something like this:

(or *unloadedxrefalert*
    (setq *unloadedxrefalert* (vlr-command-reactor nil '((:vlr-commandwillstart . xrefalert))))
)
(defun xrefalert (get info / m)
  (cond	((wcmatch (car info) "*PLOT*,*PUBLISH*")
	 (setq m "")
	 (vlax-for b (vla-get-blocks (vla-get-activedocument (vlax-get-acad-object)))
	   (if (and (= -1 (vlax-get b 'isxref)) (= 0 (vla-get-count b)))
	     (setq m (strcat "\n" (vla-get-path b) " is UNLOADED!!" m))
	   )
	 )
	 (or (= m "") (alert m))
	)
  )
  (princ)
)

[scot-65]

The other day I was assigned to edit someone else's unmaintained
file and was able to purge out 1500 unused blocks. The method you
show iterates thru the blocks inside the reactor, which might cause
a significant delay when calling forward commands PLOT and PUBLISH.

[ronjonp]

Agreed that many blocks in a drawing would slow this down. Do you have a better way to approach it?

From my testing in the past I've only seen a huge delay when block definitions are in the ten to hundreds of thousands.