moljac wrote
>
> Does
> Visual Studio +/ Advanced Save Settings +/ Unicode without signature
> (Codepage xx)
> helps?
>
> I thnik MS guys are calling it Signature and not BOM...
>
> mel
>
>
I can confirm, that changing file->advanced save options to "Unicode (UTF-8
without signature) -
Does
Visual Studio +/ Advanced Save Settings +/ Unicode without signature
(Codepage xx)
helps?
I thnik MS guys are calling it Signature and not BOM...
mel
On 2012.05.17 11:18, Lluis Sanchez Gual wrote:
I can confirm that this is a limitation in the Android SDK. Eclipse suffers the
same p
I can confirm that this is a limitation in the Android SDK. Eclipse suffers the
same problem, it can't handle layout files which have a BOM.
I'm going to add a check for this specific issue and show a more meaningful
error message when it happens.
To fix it you can just remote the header in the
The problem seems to be with files which have a byte order mark. MonoDevelop
creates new files without a BOM, and that's why it then works. At least I know
what's the issue now.
El 17/05/2012, a las 05:08, NebulaSleuth escribió:
>
> Lluis Sanchez Gual wrote
>>
>>
>>> I am unable to reprodu
Lluis Sanchez Gual wrote
>
>
>> I am unable to reproduce this problem. Can you send me a sample layout
>> (+included files) I could use to reproduce the error?
>>
>
So I was going to give you an example, but I wanted to simply it first. So
what I found was very strange indeed.
If I created
Lluis Sanchez Gual wrote
>
> Are you using Windows or Mac? MonoDevelop or Visual Studio?
>
I am using Windows 7 64bits and Visual Studio 2010.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Designer-Error-tp5709771p5709827.html
Sent from the Mono for Android ma
Are you using Windows or Mac? MonoDevelop or Visual Studio?
El 16/05/2012, a las 18:07, José M. Rivera escribió:
>
> Lluis Sanchez Gual wrote
>>
>> I am unable to reproduce this problem. Can you send me a sample layout
>> (+included files) I could use to reproduce the error?
>>
>
> http://mon
Lluis Sanchez Gual wrote
>
> I am unable to reproduce this problem. Can you send me a sample layout
> (+included files) I could use to reproduce the error?
>
http://mono-for-android.1047100.n5.nabble.com/file/n5709822/tittle_header.axml
tittle_header.axml
http://mono-for-android.1047100.n5.nab
I am unable to reproduce this problem. Can you send me a sample layout
(+included files) I could use to reproduce the error?
El 15/05/2012, a las 21:02, NebulaSleuth escribió:
> I had the same problem. It was because my design file used an
> statement.
>
> It appears that the designer doesn't
NebulaSleuth wrote
>
> I had the same problem. It was because my design file used an
> statement.
>
> It appears that the designer doesn't like it, or has a problem resolving
> the path. This is unfortunate because I use them whenever I have a
> element.
>
Yes, my design file has the tag
I had the same problem. It was because my design file used an
statement.
It appears that the designer doesn't like it, or has a problem resolving the
path. This is unfortunate because I use them whenever I have a
element. That way my xml isn't so messy.
something like:
Lluis Sanchez Gual wrote
>
> Make sure the initial processing instruction (the tag) is the
> first one in the file, and that there is no whitespace before it.
>
I checked and the tag is the first one on the file and also ther
is no whitespace before it. Even though the designer falied when i r
Looks like the layout file contains invalid xml. Make sure the initial
processing instruction (the tag) is the first one in the file, and
that there is no whitespace before it.
El 15/05/2012, a las 19:46, José M. Rivera escribió:
> I am getting the following error when trying to open a layout
13 matches
Mail list logo
