How to access this ? AMFBinaryData.verboseLogging = false;
Hugo Ferreira <hferreira...@gmail.com> escreveu no dia segunda, 1/11/2021 à(s) 10:28: > Hi Greg, > > Thank you. > > I'm not using js:AMFClassAliasBead > > I call the services by AS code, using SimpleRemoteObject: > > private var remoteObject:SimpleRemoteObject = null; > remoteObject = new SimpleRemoteObject(); > remoteObject.send(service, arguments); > > Of course, I don't type this all the time. I have a helper class to do so. > > Greg Dove <greg.d...@gmail.com> escreveu no dia segunda, 1/11/2021 à(s) > 04:24: > >> With the latest code, you should be able to control it easily by swapping >> your class alias bead: >> <js:AMFClassAliasBead verboseLogging="false" /> >> >> It is true by default (same as it was before), but only in debug build. If >> you set it to false (like above) it should be quiet. >> >> Please let me know if you see any issues or anything to be improved. >> >> Cheers, >> Greg >> >> >> >> On Mon, Nov 1, 2021 at 11:24 AM Hugo Ferreira <hferreira...@gmail.com> >> wrote: >> >> > Thank you very much. >> > >> > Greg Dove <greg.d...@gmail.com> escreveu no dia domingo, 31/10/2021 >> à(s) >> > 07:12: >> > >> > > Hi Hugo, >> > > >> > > I did some work on this tonight. >> > > I realise it's not a substantial change, but plan to test it along >> with a >> > > couple of other changes, and push it to the asjs repo first thing >> > tomorrow >> > > before I start regular work (about 12 hours from the time of this >> email). >> > > Hope that will make things easier for you in the coming week. I'll >> reply >> > to >> > > this thread with more info after I add it. >> > > >> > > >> > > >> > > On Sun, Oct 31, 2021 at 8:10 AM Hugo Ferreira <hferreira...@gmail.com >> > >> > > wrote: >> > > >> > > > 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). >> > > > > > >> > > > > >> > > > >> > > >> > >> >