I was actually confused by the docs for that method call as well. I wasn't sure what was meant by *clip*. I guess they mean "*clipping region*", which I guess is a rectangle.
I was under a serious time constraint when I first looked into this. I was afraid clip might have referred to some image and that the method could be rather slow if it is saving some image. On Thursday, September 13, 2012 2:33:45 AM UTC-5, NikDmit wrote: > > There is another save without parameters > > public int save () > Since: API Level > 1<http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels> > > Saves the current matrix and clip onto a private stack. Subsequent calls > to translate,scale,rotate,skew,concat or clipRect,clipPath will all operate > as usual, but when the balancing call to restore() is made, those calls > will be forgotten, and the settings that existed before the save() will be > reinstated. > Returns > > - The value to pass to restoreToCount() to balance this save() > > > I think, multiplying by the inverse will work for my case pretty well. > Android itself is not that complicated system, but environment and > documentation leave much to be desired. The best documentation I've ever > read is Qt framework's documentation. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
