[mono-android] axml files issues

[John Murray]

Further to previous tests I have now tried running the said xml under
eclipse

The fact that it renders in the visual designer is no guide at all

Adding a second TableLayout sequentially after a first table will cause the
app to 'close unexpectedly'
(under Eclipse) on running it.
However nesting the TableLayout in the first table causes erratic behaviour 
First time I did it, it caused a 'close unexpectedly' error - then after
closing Eclipse and starting up again It worked as a nested Table. Then
second try it failed again 
This is very similar to the behaviour under MonoDroid except one doesn't get
a warning - it just hangs 

So it looks like it's not a machine specific issue and is common to Eclipse
as well


John Murray

-----Original Message-----
From: Jonathan Pryor [mailto:jpryor at novell.com] 
Sent: 21 March 2011 17:23
To: john at murray.gb.com; monodroid at lists.ximian.com
Subject: Re: [mono-android] axml files issues

On Mar 21, 2011, at 1:10 PM, John Murray wrote:
> I think I've solved the issue - not sure if it is peculiar to Monodroid
because the following xml is acceptable in Eclipse and Droiddraw but causes
Monodroid in VS2010 to hang

What does this mean, exactly? Do you mean that within Eclipse and DroidDraw
the XML renders as expected, but when you use the same XML on device with
Mono for Android it fails to work?

If that's the case, could you try using that XML with a Java project, on
device?

As far as I know, Mono for Android isn't doing anything special with the
XML, we're (currently) just passing it as-is to `aapt` & co., so this
_shouldn't_ behave any differently between a Mono for Android app & a Java
app, on device...

Thanks,
 - Jon