Hi Thorsten, >>We're talking about a UNO API here, so only UNO services are allowed :) > > Ok, I'll think about it. But in this broad sense, that's something > unrelated to XSimpleCanvas (the same argument applies to XCanvas), and > in fact quite abundant also for other UNO interfaces (i.e. that useful > helper functionality is only available in C++).
Okay. > You explicitely requested removal of setClip( PolyPolygon ), thus: a > clip on an XSimpleCanvas is always rectangular (with empty/null clip > being a special case of rectangular, naturally). Regarding the > usefulness of the method: we should IMO either provide getters for > _all_ the state, or none. Either the client needs to store what she's > set at XSimpleCanvas by herself (if she later needs the state), or the > interface is able to provide all of it (personally, I slightly prefer > not providing the getters - because it clutters the interface, and, as > you suggest, one probably needs it rather seldomly. Or maybe only > provide the getRender/ViewState ones, as most of the information can be > deduced from that. Hm). > > What do you think? Hmm, too. What if somebody sets a clip region at the canvas retrieved from the XSimpleCanvas, and then calls getRectClip at the latter? How could a reasonable implementation behave then? Perhaps removing the getters is a good idea ... :-\ As long as we have Render/ViewState, probably everything's fine ... Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
