View representations

[Anonymous]

Hi,
Is it possible to create view representations in an assembly using Intent (via adopt or something)? I want to use this created view representation in my drawing (which I know is possible in Intent).


Cheers,
Mark

[Anonymous]

Hi,
Intent creates an "Intent" design view representation but any others must be
created via the api.
Thanks
Elly

--
"MarkBrouwers3959" wrote in message news:6377156@discussion.autodesk.com...
Hi,
Is it possible to create view representations in an assembly using Intent
(via adopt or something)? I want to use this created view representation in
my drawing (which I know is possible in Intent).


Cheers,
Mark

[Anonymous]

Hi Elly,
Thanks for the reply.

I know that Intent creates an view representation 'Intent', but I want to put an other view representation on my drawing. Within Intent I can use the :IvBaseView rule which has a property designViewRepresentation (string) that can hold the name of the view I want to put on the drawing. What is the point of having this property if you can't create a view representation in my Intent model ?

I'm writing an c# addin in Inventor using the Inventor/Intent API to create dynamic rules (children, mates, ...). Up until now it's working quite well but now I'm stuck with the fact that I want to create drawings of my model where some parts are being 'replaced' by their 2D symbol (i.e. electrical powersocket are replaced by their electrical symbol). I wanted to use view representations to achieve this, but apparently Intent only uses one view representation.
Is the only alternative that I have to use the API of Inventor (or Intent) to create and populate the view representation ?

TIA

Mark

[glibardi]

I believe that is your only option at this time.

-Gene

[Anonymous]

Hi,
The more that Intent allows non Intent content to be used seamlessly the
better. So even if Intent doesn't support the views, you need to be able to
select it so that Intent can drive the drawing creation right?

As far as view creation from within Intent goes, I think the problem is a
little more complicated than it sounds, since Intent doesn't inherently have
swappable states - a rule like visibility is a rule like length. Thinking
out loud, i'm thinking the desired process might link to Intent, by kicking
of a set of model changes intended to create a certain view, off of which
the process then creates the representation, before going back to the base
state. But it's still an external process used to create the views. A more
sophisticated step would be to have intent write that information into the
xml format used for design views.

One other thought that i have not tried: In theory you could create view
reps in your template. i know that the design view seems to care about the
path to the node in the inventor model, not whatever part/assembly files are
underneath, so even if Intent swaps them out this could work.

Hope this helps a bit
Elly

"MarkBrouwers3959" wrote in message news:6378027@discussion.autodesk.com...
Hi Elly,
Thanks for the reply.

I know that Intent creates an view representation 'Intent', but I want to
put an other view representation on my drawing. Within Intent I can use the
:IvBaseView rule which has a property designViewRepresentation (string) that
can hold the name of the view I want to put on the drawing. What is the
point of having this property if you can't create a view representation in
my Intent model ?

I'm writing an c# addin in Inventor using the Inventor/Intent API to create
dynamic rules (children, mates, ...). Up until now it's working quite well
but now I'm stuck with the fact that I want to create drawings of my model
where some parts are being 'replaced' by their 2D symbol (i.e. electrical
powersocket are replaced by their electrical symbol). I wanted to use view
representations to achieve this, but apparently Intent only uses one view
representation.
Is the only alternative that I have to use the API of Inventor (or Intent)
to create and populate the view representation ?

TIA

Mark