To take a snapshot of a View use
View.getDrawingCache()
You should have turned cache on before that
View.setDrawingCacheEnabled(true)
br
On Mar 23, 6:50 pm, Diego Pino <[EMAIL PROTECTED]> wrote:
> So, what to use instead of copyWindowBitmap to take asnapshotof a
> view?
>
> On Feb 29, 3:53 am, "Dan U." <[EMAIL PROTECTED]> wrote:
>
> > FYI, the challenge date was changed a long long time ago. You have
> > more than 2 weeks.
>
> > On Feb 28, 12:57 pm, endl <[EMAIL PROTECTED]> wrote:
>
> > > It is very nice that you've done it before 2 weeks before challenge
> > > deadline. Why did you add the method to the current SDK? Instead of
> > > this you could simply remove it and it would be clear that is not
> > > supported any more. And now you have a function that simply crashes
> > > the application! Do you have any other functions that simply crash?
>
> > > On 28 фев, 23:07, hackbod <[EMAIL PROTECTED]> wrote:
>
> > > > Hi all,
>
> > > > This function will be removed in the next SDK. It is not feasible to
> > > > support it along with hardware accelerated rendering into surfaces.
>
> > > > On Feb 28, 9:55 am, endl <[EMAIL PROTECTED]> wrote:
>
> > > > > It is not the solution. They will run the code with the last SDK and
> > > > > it will fail. Write working code or don't write it at all. Have a nice
> > > > > day, Volodya!
>
> > > > > On 28 фев, 20:13, "[EMAIL PROTECTED]"
>
> > > > > <[EMAIL PROTECTED]> wrote:
> > > > > > Use previous SDK
>
> > > > > > On Feb 26, 11:40 pm, Yoshi <[EMAIL PROTECTED]> wrote:
>
> > > > > > > This function don't work well on the m5 version of SDK.
>
> > > > > > > Log.d("cap1", "cap1");
> > > > > > > screen = mMapView.copyWindowBitmap();
> > > > > > > Log.d("cap2", "cap2");
>
> > > > > > > When the functioncopyWindowBitmapis executed, the activity is
> > > > > > > crushed; the first Log is printed on LogCat but second one is not.
> > > > > > > There are some strange messages on LobCat before crushing.
>
> > > > > > > DEBUG/SurfaceFlinger(527): Surface 1, heap=0x1aa960 destroyed
> > > > > > > DEBUG/SurfaceFlinger(527): Surface 0, heap=0x1aa960 destroyed
> > > > > > > DEBUG/SurfaceFlinger(527): Surface 1, heap=0x1aa960 destroyed
> > > > > > > DEBUG/SurfaceFlinger(527): Surface 0, heap=0x1aa960 destroyed
> > > > > > > DEBUG/SurfaceFlinger(527): Surface 1, heap=0x1ab098 destroyed
>
> > > > > > > The function was work well on the previous SDK.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
