[fusion-dev] Re: Recursion issue? with the legend updates

[Zac Spitzer]

The Basic MapGuide Viewer handles this differently as well,
when there are a lot of themes, it only shows the first and last theme
icon seperated by ... instead

On 16 July 2010 13:30, Zac Spitzer <zac.spitzer at gmail.com> wrote:
> logged in trac
>
> http://trac.osgeo.org/fusion/ticket/400
>
> On 15 July 2010 12:17, Paul Spencer <pspencer at dmsolutions.ca> wrote:
>> Hey Zac
>>
>> the next version of fusion/jxlib that Mike has been working on has a more reasonable approach to populating the tree to accommodate this kind of situation (although I'm still not sure it would handle your case that gracefully ;)).  I don't believe that we looked at delaying the actual insert, I should go back and see if we can gain some performance by setting a flag that says don't insert the tree, just build it.  I know that the found the style updates excessive and added a freeze/thaw rendering pattern to prevent updates to the whole tree on every insert and that proved to be a huge performance gain.
>>
>> Cheers
>>
>> Paul
>>
>>
>> On 2010-07-14, at 9:46 PM, Zac Spitzer wrote:
>>
>>> Ok, I found what was causing the issue... a database generated theme
>>> had 891 layers which is obviously a bit ridiculous...
>>>
>>> the lock up was being caused by excessive dom inserts and style updates
>>>
>>> a solution to this would be to make all the style elements just one block
>>> and insert that once, rather than a theme at a time. I'm not familiar with JX
>>> enough to know if that's possible
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 14 July 2010 18:06, Zac Spitzer <zac.spitzer at gmail.com> wrote:
>>>> I am working thru an issue with a map i have, using the mapguide 2.2 beta
>>>> at the moment.
>>>>
>>>> Basically when i drop below the scale of 20k, the browser will lock up
>>>> for upwards
>>>> of 35-60 seconds in the update legend.js code.
>>>>
>>>> So far after some profiling pain, i have worked out that commenting out the
>>>> line below stops the problem
>>>>
>>>>    _update: function() {
>>>>            //this.updateGroupLayers(map.layerRoot.groups[i], currentScale);
>>>>
>>>> I will continue my digging to see if I can work out what is causing the issue.
>>>>
>>>> Looks like some kind of nasty recursion or something
>>>>
>>>> Thought I'd touch base to see if anyone else has seen this
>>>>
>>>> regards
>>>>
>>>> z
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Zac Spitzer
>>>> Solution Architect / Director
>>>> Ennoble Consultancy Australia
>>>> http://www.ennoble.com.au
>>>> http://zacster.blogspot.com
>>>> +61 405 847 168
>>>>
>>>
>>>
>>>
>>> --
>>> Zac Spitzer
>>> Solution Architect / Director
>>> Ennoble Consultancy Australia
>>> http://www.ennoble.com.au
>>> http://zacster.blogspot.com
>>> +61 405 847 168
>>> _______________________________________________
>>> fusion-dev mailing list
>>> fusion-dev at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/fusion-dev
>>
>>
>> __________________________________________
>>
>>   Paul Spencer
>>   Chief Technology Officer
>>   DM Solutions Group Inc
>>   http://research.dmsolutions.ca/
>>
>>
>
>
>
> --
> Zac Spitzer
> Solution Architect / Director
> Ennoble Consultancy Australia
> http://www.ennoble.com.au
> http://zacster.blogspot.com
> +61 405 847 168
>



-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168