RE: More on getObjectExtent()

One more question. I think we already talked about this and came to a
conclusion, but I wonder if the right decision was taken.
 
Does getObjectExtent() include the 'viewcontext' APS attribute in its
calculation?
 
I think we talked about this a while back and said 'no'. Again, the
current wording doesn't mention 'viewcontext' so I have to assume it's
not included.
 
However, say I have the following scenario in test.cgm:
 
test.cgm contains an APS called 'myTarget' with a 'viewcontext' larger
than its graphical primitives.

*	
	I can navigate directly to 'myTarget' with test.cgm#myTarget and
I should _zoom_ to the 'viewcontext' rectangle
*	
	I can also use myPicture.setView(
myPicture.getAppStructureById("myTarget").getObjectExtent() );

The second case would generate a different result compared to the first,
is that what we want?
 
Benoit.

________________________________

From: public-webcgm-wg-request@w3.org
[mailto:public-webcgm-wg-request@w3.org] On Behalf Of Bezaire, Benoit
Sent: Tuesday, November 18, 2008 1:53 PM
To: WebCGM WG
Subject: More on getObjectExtent()


The wording says "[...] The bounding box calculation is based on the
abstract locus of the primitives within the APS."
What does 'abstract locus' mean?
 
I'd like to know if getObjectExtent() returns a tight bounding box on a
given APS. i.e., given a polybezier, are control points part of the
bounding box calculations or not?
 
Benoit.