Hello Peter, Could you provide a sample app which shows the behavior? With that, I can open up an issue report because this sounds like something we should take a closer look at.
Peter Schneider wrote: > > But I am a bit confused about "[...]These warnings should be disabled in > most > of the modern browsers[...]". > The debug warnings do _only_ appear when I run a application which was > build > with "generate source-disposerDebug". In those builds these warnings > _should_ > appear when appropriate, right? > The question is, when are they appropriate? I did some researches before the 1.1 release on disposing objects, which you can see in this bug report: http://bugzilla.qooxdoo.org/show_bug.cgi?id=3411 It seems that disconnecting all objects is to much overhead. The garbage collector should be able handle this. Thats why we removed the automatically disconnecting of the properties in most cases (more details in the bug report). The exceptions are older browsers where we know that the garbage collection has some issues with such an approach like IE6 and FF2. These browsers should show you such warnings. Peter Schneider wrote: > > Is this the general approach to dispose/destruct properties that are > non-qooxdoo objects/arrays? > The general approach is to check where the warnings comes from and see if this warning is appropriate. :) Regards, Martin -- View this message in context: http://qooxdoo.678.n2.nabble.com/Missing-destruct-definitions-in-qx-io-remote-transport-XmlHttp-v1-1-tp5018573p5064230.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
