[android-developers] Re: Best practise for DocumentFile? Is it the right approach?

2015-01-29 Thread Grunthos
Don't suppose anyone has insights for just one of these questions? #4 would be pretty useful. -- 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

[android-developers] Re: Reusable code organization with Android Studio

2015-01-23 Thread Grunthos
Interesting post, I find myself in a similar posiion re libraries and, more generally, in trying to find realistic best practice guides. On Saturday, January 24, 2015 at 5:07:58 AM UTC+11, Nobu Games wrote: - *I use only a single massive repository *that is basically an Android Studio

[android-developers] Re: Keeping views in sync on model change

2015-01-19 Thread Grunthos
On Friday, January 16, 2015 at 8:30:18 AM UTC+11, Nathan Barraille wrote: - Go the way I think the Android framework is supposed to work, and notify change on all content URIs whenever a track has changed. This will force the loader to re-run and refresh data from the database. This is

[android-developers] Best practise for DocumentFile? Is it the right approach?

2015-01-17 Thread Grunthos
I have an app that needs to support API 7 through lollipop; until KitKat, it used 'File' objects to talk to the local file system. I had planned to use DocumentFile as a simple solution to my problems. However, I can not see simple ways to do the following: 1. Save the equivalent of path and

[android-developers] Re: SQLite Collate UNICODE - not case sensitive in ICS??

2012-03-16 Thread Grunthos
An entire android app? Or will just a demo class do? On Mar 16, 5:16 pm, Zsolt Vasvari zvasv...@gmail.com wrote: Create a small test case and submit it to b.android.com -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this

[android-developers] Re: SQLite Collate UNICODE - not case sensitive in ICS??

2012-03-16 Thread Grunthos
FWIW, I created issue 27053: http://code.google.com/p/android/issues/detail?id=27053 This code snippet was included; I will probably end up using it to test the phone when the app first runs. Ugh. package com.some.name; import android.database.Cursor; import

[android-developers] Re: SQLite Collate UNICODE - not case sensitive in ICS??

2012-03-16 Thread Grunthos
On Mar 16, 8:19 pm, Mark Carter mjc1...@googlemail.com wrote: So you may want to verify the problem exists in SDK 3.0, but not in 2.3.3. No, it's just Android 4.0.x And the UNICODE stuff is, effectively, an extension to the core SQLite code, so the problem is not likely to be related to SQLite

[android-developers] SQLite Collate UNICODE - not case sensitive in ICS??

2012-03-15 Thread Grunthos
I have been testing an app in ICS and found that SQL queries of the form: select text from table order by text collate UNICODE no longer sort in a case-insensitive way. The same code in Android 1.6 and 2.x returns the rows in case- insensitive order. Is there some documented change that

[android-developers] Re: SQLite Collate UNICODE - not case sensitive in ICS??

2012-03-15 Thread Grunthos
On Mar 16, 2:29 pm, Zsolt Vasvari zvasv...@gmail.com wrote: I don't know I always do a LOWER() just to be safe... While that works, it is roughly 25% slowerwhich is not something I can readily afford. I'd be much happier if there was a known bug (to be fixed) or a flag I could set on

[android-developers] Re: SQLite and Collate UNICODE

2011-02-25 Thread Grunthos
/SQLite... (just search the page for UNICODE). it's just it does not seem to be working quite right for me. On 25/02/2011 4:23 PM, DanH wrote: http://www.sqlite.org/faq.html#q18 On Feb 24, 7:55 pm, Grunthos p...@rhyme.com.au wrote: Hi, In SQLite under Android 2.1 and 2.2 I have been

[android-developers] SQLite and Collate UNICODE

2011-02-24 Thread Grunthos
Hi, In SQLite under Android 2.1 and 2.2 I have been using 'Collate UNICODE' to sort and compare values; for sorting it does what I expect -- it is case-insensitive, and handles the expanded character set well. But for comparisons, eg. f = 'something' where f is a text field, it seems to NOT do