Yes, that is a bit more complex. First, don't confuse SAX handler
callbacks with GUI handler callbacks. Two approaches:
1) Make AsyncTask implement org.sax.ContentHandler. That way the
SAX callbacks have direct access to AsyncTask.publishProgress().
2) Create a delegate so that the parser has a ha
owh mostly for being more memory efficient ? :D
I have tried with the AsyncTask, which seemed like a great option for
me (especially being able to do an updateProgress) but unfortunately
my situation is somewhat more complex :(
In my situation I have a main class (with the main UI Thread
obviously
The AsyncTask pattern already provides a thread (from a pool) that you can
use anytime you need one. It's not at all clear why you need a singleton XML
parser.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send emai
Hi Mark,
first of all thanks for your answer :D
I come from a J2ME background in which I had the same problem, i.e I
need to have a always-existent database interface and a always-
existent xml-parser which (in J2ME) I placed in a singleton Thread, so
that they could be paused when needed and they
4 matches
Mail list logo
