legend.currentRange JavaScript Error?

11 messages Options
Embed this post
Permalink
GordonL

legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
Hi All, does anyone know how to get rid of the legend.currentRange error?

I can't see to see where it is coming from.  All my layers seem to work.


thanks
gordon
GordonL

Re: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
Just to follow up.  This error shows in the JavaScript at the bottom of the browser when using FUSION.  


GordonL wrote:
Hi All, does anyone know how to get rid of the legend.currentRange error?

I can't see to see where it is coming from.  All my layers seem to work.


thanks
gordon
Paul Spencer-2

Re: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
sounds familiar, I think this is/was a problem in Legend.js but I  
can't remember if it was fixed or not.  Do you have a line number?

Paul

On 19-Jun-09, at 3:46 PM, GordonL wrote:

>
> Just to follow up.  This error shows in the JavaScript at the bottom  
> of the
> browser when using FUSION.
>
>
>
> GordonL wrote:
>>
>> Hi All, does anyone know how to get rid of the legend.currentRange  
>> error?
>>
>> I can't see to see where it is coming from.  All my layers seem to  
>> work.
>>
>>
>> thanks
>> gordon
>>
>
> --
> View this message in context: http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3121772.html
> Sent from the Fusion Users mailing list archive at Nabble.com.
>
> _______________________________________________
> fusion-users mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/fusion-users


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
fusion-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fusion-users
GordonL

Re: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
Sure, the error is in the template INDEX.HTML

LINE 2
CHAR 562901

thanks
gordon



Paul Spencer-2 wrote:
sounds familiar, I think this is/was a problem in Legend.js but I  
can't remember if it was fixed or not.  Do you have a line number?

Paul

On 19-Jun-09, at 3:46 PM, GordonL wrote:

>
> Just to follow up.  This error shows in the JavaScript at the bottom  
> of the
> browser when using FUSION.
>
>
>
> GordonL wrote:
>>
>> Hi All, does anyone know how to get rid of the legend.currentRange  
>> error?
>>
>> I can't see to see where it is coming from.  All my layers seem to  
>> work.
>>
>>
>> thanks
>> gordon
>>
>
> --
> View this message in context: http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3121772.html
> Sent from the Fusion Users mailing list archive at Nabble.com.
>
> _______________________________________________
> fusion-users mailing list
> fusion-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fusion-users


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
fusion-users mailing list
fusion-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fusion-users
Paul Spencer-2

Re: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
um, the ever unhelpful single file compressed build :)

On 19-Jun-09, at 6:14 PM, GordonL wrote:

>
> Sure, the error is in the template INDEX.HTML
>
> LINE 2
> CHAR 562901
>
> thanks
> gordon
>
>
>
>
> Paul Spencer-2 wrote:
>>
>> sounds familiar, I think this is/was a problem in Legend.js but I
>> can't remember if it was fixed or not.  Do you have a line number?
>>
>> Paul
>>
>> On 19-Jun-09, at 3:46 PM, GordonL wrote:
>>
>>>
>>> Just to follow up.  This error shows in the JavaScript at the bottom
>>> of the
>>> browser when using FUSION.
>>>
>>>
>>>
>>> GordonL wrote:
>>>>
>>>> Hi All, does anyone know how to get rid of the legend.currentRange
>>>> error?
>>>>
>>>> I can't see to see where it is coming from.  All my layers seem to
>>>> work.
>>>>
>>>>
>>>> thanks
>>>> gordon
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3121772.html
>>> Sent from the Fusion Users mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> fusion-users mailing list
>>> [hidden email]
>>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>> __________________________________________
>>
>>    Paul Spencer
>>    Chief Technology Officer
>>    DM Solutions Group Inc
>>    http://research.dmsolutions.ca/
>>
>> _______________________________________________
>> fusion-users mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>
> --
> View this message in context: http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3122442.html
> Sent from the Fusion Users mailing list archive at Nabble.com.
>
> _______________________________________________
> fusion-users mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/fusion-users


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
fusion-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fusion-users
GordonL

Re: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
Thanks Paul, actually, I tried the non-compressed build, here is the error:
Webpage error details


Message: 'legend.currentRange' is null or not an object
Line: 523
Char: 9
Code: 0
URI: http://squamish2010.ca/mapguide2010/fusion/widgets/Legend.js

thanks
gordon


ps,  here is line 222 on...
var range = layer.getScaleRange(fScale);
        if (range == layer.legend.currentRange && layer.legend.treeItem) {
            return;
        }


Paul Spencer-2 wrote:
um, the ever unhelpful single file compressed build :)

On 19-Jun-09, at 6:14 PM, GordonL wrote:

>
> Sure, the error is in the template INDEX.HTML
>
> LINE 2
> CHAR 562901
>
> thanks
> gordon
>
>
>
>
> Paul Spencer-2 wrote:
>>
>> sounds familiar, I think this is/was a problem in Legend.js but I
>> can't remember if it was fixed or not.  Do you have a line number?
>>
>> Paul
>>
>> On 19-Jun-09, at 3:46 PM, GordonL wrote:
>>
>>>
>>> Just to follow up.  This error shows in the JavaScript at the bottom
>>> of the
>>> browser when using FUSION.
>>>
>>>
>>>
>>> GordonL wrote:
>>>>
>>>> Hi All, does anyone know how to get rid of the legend.currentRange
>>>> error?
>>>>
>>>> I can't see to see where it is coming from.  All my layers seem to
>>>> work.
>>>>
>>>>
>>>> thanks
>>>> gordon
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3121772.html
>>> Sent from the Fusion Users mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> fusion-users mailing list
>>> fusion-users@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>> __________________________________________
>>
>>    Paul Spencer
>>    Chief Technology Officer
>>    DM Solutions Group Inc
>>    http://research.dmsolutions.ca/
>>
>> _______________________________________________
>> fusion-users mailing list
>> fusion-users@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>
> --
> View this message in context: http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3122442.html
> Sent from the Fusion Users mailing list archive at Nabble.com.
>
> _______________________________________________
> fusion-users mailing list
> fusion-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fusion-users


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
fusion-users mailing list
fusion-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fusion-users
GordonL

Re: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Paul Spencer-2
Thanks Paul, actually, I tried the non-compressed build, here is the error:
Webpage error details


Message: 'legend.currentRange' is null or not an object
Line: 523
Char: 9
Code: 0
URI: http://squamish2010.ca/mapguide2010/fusion/widgets/Legend.js

thanks
gordon


ps,  here is line 222 on...
var range = layer.getScaleRange(fScale);
        if (range == layer.legend.currentRange && layer.legend.treeItem) {
            return;
        }


Paul Spencer-2 wrote:
um, the ever unhelpful single file compressed build :)

On 19-Jun-09, at 6:14 PM, GordonL wrote:

>
> Sure, the error is in the template INDEX.HTML
>
> LINE 2
> CHAR 562901
>
> thanks
> gordon
>
>
>
>
> Paul Spencer-2 wrote:
>>
>> sounds familiar, I think this is/was a problem in Legend.js but I
>> can't remember if it was fixed or not.  Do you have a line number?
>>
>> Paul
>>
>> On 19-Jun-09, at 3:46 PM, GordonL wrote:
>>
>>>
>>> Just to follow up.  This error shows in the JavaScript at the bottom
>>> of the
>>> browser when using FUSION.
>>>
>>>
>>>
>>> GordonL wrote:
>>>>
>>>> Hi All, does anyone know how to get rid of the legend.currentRange
>>>> error?
>>>>
>>>> I can't see to see where it is coming from.  All my layers seem to
>>>> work.
>>>>
>>>>
>>>> thanks
>>>> gordon
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3121772.html
>>> Sent from the Fusion Users mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> fusion-users mailing list
>>> fusion-users@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>> __________________________________________
>>
>>    Paul Spencer
>>    Chief Technology Officer
>>    DM Solutions Group Inc
>>    http://research.dmsolutions.ca/
>>
>> _______________________________________________
>> fusion-users mailing list
>> fusion-users@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>
> --
> View this message in context: http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3122442.html
> Sent from the Fusion Users mailing list archive at Nabble.com.
>
> _______________________________________________
> fusion-users mailing list
> fusion-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fusion-users


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
fusion-users mailing list
fusion-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fusion-users
Paul Spencer-2

Re: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
I'm not seeing anything obviously wrong here, it will require some  
debugging and follow.  Can you file a bug for this please?  Just  
include the text below.

Paul

On 22-Jun-09, at 2:11 PM, GordonL wrote:

>
> Thanks Paul, actually, I tried the non-compressed build, here is the  
> error:
> Webpage error details
>
>
> Message: 'legend.currentRange' is null or not an object
> Line: 523
> Char: 9
> Code: 0
> URI: http://squamish2010.ca/mapguide2010/fusion/widgets/Legend.js
>
> thanks
> gordon
>
>
> ps,  here is line 222 on...
> var range = layer.getScaleRange(fScale);
>        if (range == layer.legend.currentRange &&  
> layer.legend.treeItem) {
>            return;
>        }
>
>
>
> Paul Spencer-2 wrote:
>>
>> um, the ever unhelpful single file compressed build :)
>>
>> On 19-Jun-09, at 6:14 PM, GordonL wrote:
>>
>>>
>>> Sure, the error is in the template INDEX.HTML
>>>
>>> LINE 2
>>> CHAR 562901
>>>
>>> thanks
>>> gordon
>>>
>>>
>>>
>>>
>>> Paul Spencer-2 wrote:
>>>>
>>>> sounds familiar, I think this is/was a problem in Legend.js but I
>>>> can't remember if it was fixed or not.  Do you have a line number?
>>>>
>>>> Paul
>>>>
>>>> On 19-Jun-09, at 3:46 PM, GordonL wrote:
>>>>
>>>>>
>>>>> Just to follow up.  This error shows in the JavaScript at the  
>>>>> bottom
>>>>> of the
>>>>> browser when using FUSION.
>>>>>
>>>>>
>>>>>
>>>>> GordonL wrote:
>>>>>>
>>>>>> Hi All, does anyone know how to get rid of the  
>>>>>> legend.currentRange
>>>>>> error?
>>>>>>
>>>>>> I can't see to see where it is coming from.  All my layers seem  
>>>>>> to
>>>>>> work.
>>>>>>
>>>>>>
>>>>>> thanks
>>>>>> gordon
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3121772.html
>>>>> Sent from the Fusion Users mailing list archive at Nabble.com.
>>>>>
>>>>> _______________________________________________
>>>>> fusion-users mailing list
>>>>> [hidden email]
>>>>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>>>
>>>>
>>>> __________________________________________
>>>>
>>>>   Paul Spencer
>>>>   Chief Technology Officer
>>>>   DM Solutions Group Inc
>>>>   http://research.dmsolutions.ca/
>>>>
>>>> _______________________________________________
>>>> fusion-users mailing list
>>>> [hidden email]
>>>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3122442.html
>>> Sent from the Fusion Users mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> fusion-users mailing list
>>> [hidden email]
>>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>> __________________________________________
>>
>>    Paul Spencer
>>    Chief Technology Officer
>>    DM Solutions Group Inc
>>    http://research.dmsolutions.ca/
>>
>> _______________________________________________
>> fusion-users mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>
> --
> View this message in context: http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3137825.html
> Sent from the Fusion Users mailing list archive at Nabble.com.
>
> _______________________________________________
> fusion-users mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/fusion-users


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
fusion-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fusion-users
GordonL

Re: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
HI Paul, I think I found the root cause of the error.  I have been tricky with my Layer Names .

For example rather than the Legend Label showing:

Parcel Polygons

I have:

<b>Parcel</b> Polygons


This works great with the Basic AJAX viewer but causes havoc with FUSION.. No funky legends for me!

thanks
gordon



Paul Spencer-2 wrote:
I'm not seeing anything obviously wrong here, it will require some  
debugging and follow.  Can you file a bug for this please?  Just  
include the text below.

Paul

On 22-Jun-09, at 2:11 PM, GordonL wrote:

>
> Thanks Paul, actually, I tried the non-compressed build, here is the  
> error:
> Webpage error details
>
>
> Message: 'legend.currentRange' is null or not an object
> Line: 523
> Char: 9
> Code: 0
> URI: http://squamish2010.ca/mapguide2010/fusion/widgets/Legend.js
>
> thanks
> gordon
>
>
> ps,  here is line 222 on...
> var range = layer.getScaleRange(fScale);
>        if (range == layer.legend.currentRange &&  
> layer.legend.treeItem) {
>            return;
>        }
>
>
>
> Paul Spencer-2 wrote:
>>
>> um, the ever unhelpful single file compressed build :)
>>
>> On 19-Jun-09, at 6:14 PM, GordonL wrote:
>>
>>>
>>> Sure, the error is in the template INDEX.HTML
>>>
>>> LINE 2
>>> CHAR 562901
>>>
>>> thanks
>>> gordon
>>>
>>>
>>>
>>>
>>> Paul Spencer-2 wrote:
>>>>
>>>> sounds familiar, I think this is/was a problem in Legend.js but I
>>>> can't remember if it was fixed or not.  Do you have a line number?
>>>>
>>>> Paul
>>>>
>>>> On 19-Jun-09, at 3:46 PM, GordonL wrote:
>>>>
>>>>>
>>>>> Just to follow up.  This error shows in the JavaScript at the  
>>>>> bottom
>>>>> of the
>>>>> browser when using FUSION.
>>>>>
>>>>>
>>>>>
>>>>> GordonL wrote:
>>>>>>
>>>>>> Hi All, does anyone know how to get rid of the  
>>>>>> legend.currentRange
>>>>>> error?
>>>>>>
>>>>>> I can't see to see where it is coming from.  All my layers seem  
>>>>>> to
>>>>>> work.
>>>>>>
>>>>>>
>>>>>> thanks
>>>>>> gordon
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3121772.html
>>>>> Sent from the Fusion Users mailing list archive at Nabble.com.
>>>>>
>>>>> _______________________________________________
>>>>> fusion-users mailing list
>>>>> fusion-users@lists.osgeo.org
>>>>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>>>
>>>>
>>>> __________________________________________
>>>>
>>>>   Paul Spencer
>>>>   Chief Technology Officer
>>>>   DM Solutions Group Inc
>>>>   http://research.dmsolutions.ca/
>>>>
>>>> _______________________________________________
>>>> fusion-users mailing list
>>>> fusion-users@lists.osgeo.org
>>>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3122442.html
>>> Sent from the Fusion Users mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> fusion-users mailing list
>>> fusion-users@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>> __________________________________________
>>
>>    Paul Spencer
>>    Chief Technology Officer
>>    DM Solutions Group Inc
>>    http://research.dmsolutions.ca/
>>
>> _______________________________________________
>> fusion-users mailing list
>> fusion-users@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/fusion-users
>>
>>
>
> --
> View this message in context: http://n2.nabble.com/legend.currentRange-JavaScript-Error--tp3058103p3137825.html
> Sent from the Fusion Users mailing list archive at Nabble.com.
>
> _______________________________________________
> fusion-users mailing list
> fusion-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fusion-users


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
fusion-users mailing list
fusion-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fusion-users
Jason Birch

RE: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
I saw this problem crop up on earlier versions of Fusion (like the one I'm currently running) when there are hidden folders in the legend.  I've also seen funky behaviour with themed layers at the top level of the map causing the entire legend not to load.  

I'm refraining from reporting these because they may well have been fixed in the heavily modified legend code in 2.0.  Sounds like we need some kind of testing framework though... How does one do tests against JS, especially a library with a strong server-side requirement.  Sounds tough.

Jason

-----Original Message-----
From: GordonL
Sent: Wednesday, July 22, 2009 2:29 PM
Subject: Re: [fusion-users] legend.currentRange JavaScript Error?

HI Paul, I think I found the root cause of the error.  I have been tricky
with my Layer Names .

For example rather than the Legend Label showing:

Parcel Polygons

I have:

<b>Parcel</b> Polygons


This works great with the Basic AJAX viewer but causes havoc with FUSION..
No funky legends for me!
_______________________________________________
fusion-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fusion-users
Paul Spencer-2

Re: legend.currentRange JavaScript Error?

Reply Threaded More More options
Print post
Permalink
What we need is sample data and map definitions that cause the problem  
in specific templates (the fusion standard one would be best).

I would expect that this would still be a problem with the legend.

On 23-Jul-09, at 4:18 AM, Jason Birch wrote:

> I saw this problem crop up on earlier versions of Fusion (like the  
> one I'm currently running) when there are hidden folders in the  
> legend.  I've also seen funky behaviour with themed layers at the  
> top level of the map causing the entire legend not to load.
>
> I'm refraining from reporting these because they may well have been  
> fixed in the heavily modified legend code in 2.0.  Sounds like we  
> need some kind of testing framework though... How does one do tests  
> against JS, especially a library with a strong server-side  
> requirement.  Sounds tough.
>
> Jason
>
> -----Original Message-----
> From: GordonL
> Sent: Wednesday, July 22, 2009 2:29 PM
> Subject: Re: [fusion-users] legend.currentRange JavaScript Error?
>
> HI Paul, I think I found the root cause of the error.  I have been  
> tricky
> with my Layer Names .
>
> For example rather than the Legend Label showing:
>
> Parcel Polygons
>
> I have:
>
> <b>Parcel</b> Polygons
>
>
> This works great with the Basic AJAX viewer but causes havoc with  
> FUSION..
> No funky legends for me!
> _______________________________________________
> fusion-users mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/fusion-users


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
fusion-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fusion-users