StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7151693
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-08-22T18:13:37.680
FavoriteCount
0
LastActivityDate
2011-08-22T18:13:37.680
LastEditDate
LastEditorUserId
0
OwnerUserId
724461
ParentId
6279700
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
As said in this <a href="http://android-developers.blogspot.com/2011/03/memory-analysis-for-android.html" rel="nofollow">article</a>, the pixel data for Bitmap objects is stored in byte arrays on Android 3.0 (Honeycomb). Previously it was not stored in the Dalvik heap but was stored in external heap which is not managed by Dalvik VM. So it is a big difference between Android 2.x and 3.x. And it might not be safe to draw into bitmap from native code because NDK does not provide native API for levels higher then 9. In general API should be backward compatible but hardwareAccelerated attribute changes the behavior of several methods and may break compatibility. For example the following operations behave differently when hardware acceleration enabled: <ul> <li>Canvas <ul> <li>clipRect: XOR, Difference and ReverseDifference clip modes are ignored; 3D transforms do not apply to the clip rectangle</li> <li>drawBitmapMesh: colors array is ignored</li> <li>drawLines: anti-aliasing is not supported</li> <li>setDrawFilter: can be set, but ignored</li> </ul></li> <li>Paint <ul> <li>setDither: ignored</li> <li>setFilterBitmap: filtering is always on</li> <li>setShadowLayer: works with text only</li> </ul></li> <li>ComposeShader <ul> <li>A ComposeShader can only contain shaders of different types (a BitmapShader and a LinearGradientShader for instance, but not two instances of BitmapShader)</li> <li>A ComposeShader cannot contain a ComposeShader</li> </ul></li> </ul> Here are more details about hardware acceleration: <a href="http://android-developers.blogspot.com/2011/03/android-30-hardware-acceleration.html" rel="nofollow">http://android-developers.blogspot.com/2011/03/android-30-hardware-acceleration.html</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy do NDK-updated bitmaps show black when hardwareAccelerated is turned on in Honeycomb?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAndrey Kamaev
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COI already found this information - I'm looking for a solution to draw into hardware accelerated bitmaps on Honeycomb. Telling me that it might not be possible is not an answer.
 singulars
 PostPostId
 PO
 UserUserId
 USBitBank

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.