Hi,
On Mon, Apr 29, 2013 at 6:43 PM, Paul Johnson
<[email protected]>wrote:
> Hi,
>
>
> There is always the low-tech solution of riddling your code with calls
>> to Console.WriteLine...
>>
>
> Did that too - AppDelegate ignored. Now something has just occurred to me
> and I'm not sure if it happens in monotouch as it does in monodroid.
>
> When the compiler hits an event, the event code is read to ensure it's
> correct and working. For example
>
> listView.Click += delegate {
> if (condition)
> // do something
> else
> // do something else
> };
>
> If the something else line goes out of bounds or does something silly, the
> compilation dies there.
>
> What I'm wondering is if something similar is happening here except
> instead of it being at compile time, it's at runtime (the method is called
> before AppDelegate is reached when it shouldn't be reached until
> FinishedLaunching has been hit - in other words, the UI is starting before
> it's started officially)
>
Never say never, but this doesn't sound plausible to me.
What is the actual behavior you're seeing on the screen? Does the app show
up as expected, or does it exit?
Rolf
>
> Does/can that happen?
>
>
> Paul
>
> --
> "Space," it says, "is big. Really big. You just won't believe how vastly,
> hugely, mindbogglingly big it is. I mean, you may think it's a long way
> down the road to the chemist's, but that's just peanuts to space, listen..."
> Hitch Hikers Guide to the Galaxy, a truly remarkable book!
>
> _______________________________________________
> MonoTouch mailing list
> [email protected]
> http://lists.ximian.com/mailman/listinfo/monotouch
>
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch
