Hi Malte, > That's why I said "basically" - the MapMode. > > Since UNO AWT API doesn't have support for this at all, I wonder if it's > good to take this into account for something that was intended to be a > conversion "helper" function. > > If that method takes the MapMode into account, point/size conversions > are not the same anymore...
Okay, so my memory didn't fool me. Well, given that the interface shall be implemented at the device implementation (VCLXDevice), and thus has a direct relation to the underlying VCL OutputDevice, I think we should take the MapMode into account: Somebody might have manipulated the MapMode of the underlying device, bypassing UNO. This might or might not be legitimate, but IMO we need to be prepared for this. Also, is there a chance we might decide to expose the MapMode to UNO in the future? Not sure about this ... Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
