Thanks! Your report was clearer than what I would have written… ;-)
Harbs
> On Jan 14, 2020, at 10:28 PM, Greg Dove wrote:
>
> I was just going to ask you the same thing! Yes, I'll do it
>
>
> On Wed, Jan 15, 2020 at 9:26 AM Harbs wrote:
>
>> You want to capture the issue on Github?
>>
I was just going to ask you the same thing! Yes, I'll do it
On Wed, Jan 15, 2020 at 9:26 AM Harbs wrote:
> You want to capture the issue on Github?
>
> > On Jan 14, 2020, at 10:25 PM, Greg Dove wrote:
> >
> > actually that's not right. It is still creating a binding which is
> > returning the
You want to capture the issue on Github?
> On Jan 14, 2020, at 10:25 PM, Greg Dove wrote:
>
> actually that's not right. It is still creating a binding which is
> returning the incorrect value, so not a direct value assignment.
>
>
> On Wed, Jan 15, 2020 at 9:23 AM Greg Dove wrote:
>
>>
>>
actually that's not right. It is still creating a binding which is
returning the incorrect value, so not a direct value assignment.
On Wed, Jan 15, 2020 at 9:23 AM Greg Dove wrote:
>
> I think it is close to working. Seems to be including backslashes when it
> should not, and dropping second
I think it is close to working. Seems to be including backslashes when it
should not, and dropping second curly brace.
On Wed, Jan 15, 2020 at 9:18 AM Greg Dove wrote:
> I tried it yesterday, yes. I did not doublecheck that this morning though
>
>
> On Wed, Jan 15, 2020 at 9:16 AM Harbs
I tried it yesterday, yes. I did not doublecheck that this morning though
On Wed, Jan 15, 2020 at 9:16 AM Harbs wrote:
> Have you confirmed that the escape sequence which works in Flex doesn’t in
> Royale?
>
> > On Jan 14, 2020, at 10:14 PM, Greg Dove wrote:
> >
> > The escape sequence for
Have you confirmed that the escape sequence which works in Flex doesn’t in
Royale?
> On Jan 14, 2020, at 10:14 PM, Greg Dove wrote:
>
> The escape sequence for binding that works in Flex, is single backslash.
> I just quickly tested this now with
>
> where entry was also defined locally as a
The escape sequence for binding that works in Flex, is single backslash.
I just quickly tested this now with
where entry was also defined locally as a [Bindable] in script block.
That works.
'I think this is rare enough that we have bigger fish to fry even if it is
a bug.'
I agree. I suggest we
IMO, the second example may not be escaped as we don't know the escape sequence
for binding. You have used an XML entity instead of the brace, but I think
that immediately gets evaluated into the brace UTF-8 character before parsing.
These entities are required for compliant XML, but don't
Hi,
what's clear is that sometimes trying to do this kind of things in mxml is
difficult, and I remember experimenting a lot in Flex doing things like
that. As well thinking in adding more texts and other things in MXML for
TDJ and sometimes is not easy or we can do it. As you notice is the long
It was escaped in the second example.
I think this is rare enough that we have bigger fish to fry even if it is a bug.
> On Jan 14, 2020, at 9:26 AM, Carlos Rovira wrote:
>
> I don't think is a bug too.
> If you want to translate to plain text you must escape it, or better make
> whole in a
I don't think is a bug too.
If you want to translate to plain text you must escape it, or better make
whole in a var in AS3 and display the value.
El lun., 13 ene. 2020 a las 18:46, Alex Harui ()
escribió:
> If I understand the scenario correctly, I don't think that's a bug. XML
> characters
If I understand the scenario correctly, I don't think that's a bug. XML
characters are translated into UTF-8 characters which are then parsed. The
MXML Compiler is scanning all values for binding expressions.
It would be a bug if there is no way to escape {} in a value so that it isn't
seen
I have the following markup:
But it’s displayed as:
and got the same result.
I think this is a bug. Thoughts?
Harbs
14 matches
Mail list logo
