It looked/worked pretty cool. It was pretty fast when somehow I narrowed the sections down to a few only.
Definitely an interesting way to represent data, sort of like the "visualthesaurus".com I'm interested how this turns out. Best -Pete On Thu, Apr 23, 2009 at 10:59 AM, Manic <[email protected]> wrote: > > Hi, I've been fiddling about and found that it was the 'people' > objects that were causing the massive slow down (there's about 400 of > them). I had thought I was removing them, but I was only removing a > part of them. > > I really need to work on detangling my code, I'd release this as open > source when I'm done, but I'm too embarrassed. > > Martin > > On Apr 23, 3:08 pm, Manic <[email protected]> wrote: > > My project has become very slow since a load of extra data got added > > to it, and I'm not really sure why, there's lots of elements, but I'm > > removing them from the scene whenever I don't need them, stopping them > > running the bulk of their onEnterFrame code when they're not > > visible... but it's still going much slower than it was when there was > > less data in there. Is it simply because I've now got more memory used > > in just storing objects in memory, so there's less available for > > processing the frames now? > > > > well here it is;http://uncommonpeople.co.uk/uncommon.html > > > > it'll take a bit of time to load, and will hang for a bit while it > > processes the data as well. > > > > Also, despite all my showing/hiding, as you do more with it, the > > number of render elements goes up anyway > > > > Any ideas would be great > > > > Cheers > > Martin > -- ___________________ Actionscript 3.0 Flash 3D Graphics Engine HTTP://AWAY3D.COM
