On Sep 9, 2012, at 1:39 PM, Stephan Steiner wrote:
> As it almost seems to good to be true, I cannot help but wonder - am I
> risking anything using the approach you outlined?
Not that I'm aware of.
Note that since February this approach has been simplified via two additional
facilities:
Jon
Reading your post just made my day - I never quite understood why Android is
so extremely opposed to using non GUI classes for processing - every second
operation you make requires a view or an activity. This allows me to update
launch simple toasts, and do other stuff where I don't need to kn
On Feb 20, 2012, at 11:50 AM, Chris Tacke wrote:
> I've moved to something a bit simpler that, from initial tests anyways,
> appears to work. Does this seem reasonable though (I think it assumes that
> the UIInvoker class itself is created on the UI thread):
>
>public class UIInvoker : Disp
I've moved to something a bit simpler that, from initial tests anyways, appears
to work. Does this seem reasonable though (I think it assumes that the
UIInvoker class itself is created on the UI thread):
public class UIInvoker : DisposableBase
{
private Activity m_activity = new
