Thanks for your answers!
Joe, adding a 'where'-clause to the content-resolver is a good idea.
Thanks also for your follow-up, I'll give it a go! I know the
Gallery3D-code is probably not the best as an entry-level example on
how to deal with providers and Uris, but I love it's functionality and
On Wed, Sep 29, 2010 at 2:40 PM, niko001 ebs...@googlemail.com wrote:
Dianne, I feared as much :-)! I think I'll go with implementing my own
content-provider. Do you know if it would have to be exactly the same
schema as the current media provider, or could I add one or two
columns without
A bit more information:
The DATA column in the MediaStore provider contains the file path, and
it is possible to create a LIKE selection that selects content from a
specific folder -- using a content: Uri not a file: Uri.
LocalDataSource looks like the place to start.
However, I suggest you
What are your logs showing?
I was trying to load images into an imageview using file Uris, which
worked great in 2.2, but not on 2.1 and below. I could never figure
out why.
I posted the question on SO here:
The cooliris Gallery3D code?
http://android.git.kernel.org/?p=platform/packages/apps/Gallery3D.git
How is the image cursor created? I assume it's obtained from a
MediaStore query. But if you change to a file uri, the MediaStore will
no longer handle the query...
I think you can obtain the
5 matches
Mail list logo
