[mono-android] axml files issues

[john Murray]

Hi Jonathan
What I mean is that a particular axml file causes visual studio to hang on
the FindViewByID
Obviously visual studio can only render the axml when it debugs but I cant
get that far.
The same xml renders in droiddraw and eclipse (because they have a visual
designer)- I struggle with Java and haven't tried getting as far as
debugging in Eclipse. I presume if it renders there it's ok

What I found was that if I took out the second tablelayout (sequential not
nested) then it worked in Visual studio. I tried with a nested table layout
and it worked at first as I reported below but I spoke too  soon - it is now
hanging on the base:oncreate() line 
Returning to the one table layout in the xml I can get it to work = indeed
it seems to work with any simple axml without much content. I wonder if it
is the content rather than the table layout.
Despite this pointing to an issue with VS and tablelayouts in xml, the
erratic nature of the problem suggests it may be my machine and VS set up. I
am hoping to transfer all  to another PC with a load of memory (6g v 4g ) to
see what happens. 
Fwiw I frequently get hangs on the emulator and I have to close down VS to
restore normal operation (not that it is an unrecoverable hang just that if
you cancel the debug, the next debug never works unless you close VS) 
John Murray

>>>> 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?
Exactly 

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

>>>>> 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...

That's why I suspect it is probably a machine specific memory issue

Will report after further tests
For information currently running on a Toshiba r700 laptop 2,4ghz with 4g
memory win 7
I can't see that that is poor - but one never knows - the emulator is pretty
awful anyway


-----Original Message-----
From: monodroid-bounces at lists.ximian.com
[mailto:monodroid-bounces at lists.ximian.com] On Behalf Of Jonathan Pryor
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

_______________________________________________
Monodroid mailing list
Monodroid at lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid