Hi Greg,
Having a switch option is great for a specific project that the developer
knows that will not consume all properties from the server (it's not a bug
on the project but a feature :D).
In this case, what happens is that the case warning is printed many times.
With 200 records and more than 200 properties we get and block.
Thank you very much.
Greg Dove <greg.d...@gmail.com> escreveu no dia sábado, 30/10/2021 à(s)
19:39:
> Ok Hugo, you already answered my question from the other thread, I will
> look at this today and give you an option to switch that off.
>
> Thanks,
> Greg
>
> On Sun, 31 Oct 2021, 6:57 am Hugo Ferreira, <hferreira...@gmail.com>
> wrote:
>
> > Hi,
> >
> > Today I mentioned about ignoring the warning: ReferenceError: Error
> #1056:
> > Cannot create property
> >
> > While I'm building and testing my application, I'm seeing the performance
> > slowing down, until I added a new dropdownlist and now it takes about a
> > minute to only 200 records on the dropdownlist and the page
> > freezes completely.
> > I found that this is related to this warning because this value object
> has
> > many properties that I'm intentionally ignoring and the trace is slow.
> >
> > So, I commented out the line trace('ReferenceError: Error #1056: Cannot
> > create property ' + prop + ' on ' + localTraits.qName); at AMFContext.as
> > and now the dropdown load the data instantly without any break.
> >
> > OK, this will only happen in debug mode, even so, it's not viable to wait
> > about one minute everytime I test a new build.
> >
> > Would be nice to ignore this warning for this specific project but I
> don't
> > know what's the best practice to do this (meanwhile I will do a monkey
> > patch on my side to solve this issue without being forced to comment the
> > line everytime I update Royale and build).
> >
>
