2x Identical Mviews in my paper space - Is it possible?

[ADSK2007]

Hello all

 

I need to have one mview always updating itself with an active viewport. Here is what I mean

 

I have a viewport on top right corner of my sheet - Lets call it "Mview A"

I create a new Mview "We call it Mview B" and turn ON or OFF some layers using "Freeze on active viewport"

I want "Mview A" also turn those layers ON or OFF Automatically.

Now if I create a new Mview C and turn layers ON or OFF, I want my Mview A follow Mview C (in other words, Mview A should always be identical to my active viewport.)

 

Is this possible to do with code?

 

Regards

 

ADSK2007

[David Bethel]

In short, 'Probably not'

 

A little longer, VIEWPOPRT entities cannot be made or modified with AutoLisp. The work around could be a reactor that would read the alterd viewport dxf data, and the use (command) to try and update another to match the layer states. This would be a fairly daunting task. And I would think it would have to customized for each unique drawing file.

 

-David

Edited September 12, 2012 by David Bethel
Could vs Would

[Lee Mac]

A little longer, VIEWPOPRT entities cannot be made or modified with AutoLisp. The work around would be a reactor that would read the alterd viewport dxf data, and the use (command) to try and update another to match the layer states.

 

To clarify, you cannot use (command) with a Reactor, however, the Viewports could be created and modified using the relevant Visual LISP Properties and Methods - though I agree, such an application would certainly not be straightforward to create.

[David Bethel]

To clarify, you cannot use (command) with a Reactor,

 

Did not know that. Not even if the reactor calls another routine?

 

however, the Viewports could be created and modified using the relevant Visual LISP Properties and Methods - though I agree, such an application would certainly not be straightforward to create.

 

I'm surprised ADESKk allows access to the viewport's xdata now. I would have thought it could lead to disastrous result with corrupt or conflicting data. -David

[Lee Mac]

Not even if the reactor calls another routine?

 

Not even then, the reactor callback function cannot call the command function during evaluation.