Merging Reference Files - Maintain "Allow Optimized Clipping" Setting?

Hi Andrew, 

I realise, though I think the question is an extension of the same topic, and requires the context

Just to note that you are posting against a discussion that was verified as answered over 5 years ago and may not be noted as a new question. I would suggest posting this as a separate item and reference this old discussion. Otherwise I could split it off as a separate item.

Very useful couple of lines there. solved an annoying problem. 

Next up though, is there a way to order the reference merge by slot number?? 

Reason is this: references in sheets are generally clipped by a shape within the boundary file lose their clip. when I perform a reference merge all, all refs are merged at the same time and the drawings lose their clip boundary.

When I merge manually, so that the boundary file is merged last, all clip volumes are honoured!!

When save-as ing with reference merge, the references are merged by order of slot number, lowest to highest, therefore I set my sheets up so that the boundary resides in slot 100 by default, meaning all other refs are processed before, and the clip shape is honoured

Thanks Jon,

I quite often use the method you described thanks. In any case I ended up getting it to work using the following key-in combination;

REFERENCE MERGE

ACCUDRAW BUMP TOOLSETTING 1

REFERENCE MERGE *

This combination opens the required dialog firstly without actually doing any merging. It then uses the Accudraw bump tool setting to switch the "Allow Optimized Clipping" setting to ON. This will at least keep the setting on for the current session so that next time merge is run (in this case for all references) the setting is used.

Unknown said:

Is there any setting, configuration variable or keyin I can use to maintain this setting

Record VBA Macro

I don't have a precise answer to your question, but one way to discover those unknown settings is to record a VBA macro.

While you record, toggle that setting on and off. You don't have to understand VBA to do this, but look at the results of the recording …
Recording a VBA macro

After you stop recording, look at the results. They will be in a VBA project, in a procedure called Macro1 or similar. The recording usually (but not always) shows you what application variable is being manipulated.