> > >>getCTM >> Returns the transformation matrix from current user units (i.e., >> after application of the transform attribute, if any) to the >> viewport coordinate system for the nearestViewportElement. >> >>|clientX| of type |long|, readonly >> The horizontal coordinate at which the event occurred relative to >> the DOM implementation's client area. >> >>is the "viewport coordinate system for the nearestViewportElement" of >>the outermost svg element the DOM implementations client area ? >> >> > > I don't see why these have to be the same thing. In particular >it might make sense for these to be separated by currentScale/Translate. >However I suspect that the SVG specification is insufficiently clear on >this point to have a reasoned discussion. > > yes, it clearly makes sense to seperate these by currentTranslate/Scale !
> > >>furthermore root.getCTM() does not include the viewBox transformation of >>root, >> >> > > This is clearly wrong. getCTM goes from the user-space of >the current element - which for an SVG element is clearly defined to >include the viewBox transform. This is the main reason getCTM is >almost useless if you try to chain 'getCTM' calls up the rendering >tree you get 'double' viewBox transforms. > > ahh! thanks again for clarification, now i understand what the problem is , i think! > > >>whereas anyElement.getCTM() does. >>so >>root.getScreenCTM() = root.getCTM() >> >> > > This might be true because getScreenCTM would also include >the viewBox transform the real question is does root.getCTM >return just the viewBox transform of the root element or does >it also include currentScale/Translate? > > I don't really know and as I said I don't think the SVG >specification is sufficiently clear on the topic. Since I >consider getCTM to be a lost cause due to the inability to >'chain' calls I'm not sure it's worth significant effort to >clarify - the SVG WG should just deprecate it. > > agreed! the below mentioned methods are sufficient for all cases i can think of. > I don't really know why you are interested in this (implementation >or usage), but the really useful methods to use are >'getTransformToElement' and 'getScreenCTM' > > mostly usage, but as long as these methods are not implemented correctly in mozilla, im relying on my own functions, and i try to get them as close to the spect as possible. cheers Holger >>> >>> > > > > > > ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
