Not able to draw lines on certain zoom levels

Nov 11, 2010 at 7:39 PM
Edited Nov 11, 2010 at 8:05 PM

I'm on changeset 50624, branch SL4 using Visual Studio 2.010, and When drawing on levels less than 6, it works fine, but on bigger levels the line is not shown, and throws the exception at the end of this report, in the class PathControlBase when set the StrokeThickness to the Path

        public override void OnApplyTemplate()
        {
            base.OnApplyTemplate();

            _Path = (Path)GetTemplateChild(PART_path);
            _Path.StrokeThickness = StrokeThickness; //The exception is thrown here
            _Path.Stroke = Stroke;

            IsLoaded = true;

            if (Layer != null) Layer.UpdateChildLocation(this);
        }

Follows detail of fired exception.

{System.NullReferenceException: Object reference not set to an instance of an object.
   at DeepEarth.Client.MapControl.Geometries.PathControlBase.OnApplyTemplate()
   at DeepEarth.Client.MapControl.Geometries.PathControlBase.<.ctor>b__0(IEvent`1 event)
   at System.Collections.Generic.AnonymousObserver`1.Next(T value)
   at System.Collections.Generic.AbstractObserver`1.OnNext(T value)
   at System.Collections.Generic.AnonymousObservable`1.AutoDetachObserver.Next(T value)
   at System.Collections.Generic.AbstractObserver`1.OnNext(T value)
   at System.Linq.Observable.<>c__DisplayClass174`1.<>c__DisplayClass176.<FromEvent>b__171(Object sender, TEventArgs eventArgs)
   at System.Windows.RoutedEventHandler.Invoke(Object sender, RoutedEventArgs e)
   at MS.Internal.CoreInvokeHandler.InvokeEventHandler(Int32 typeIndex, Delegate handlerDelegate, Object sender, Object args)
   at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, Int32 actualArgsTypeIndex, String eventName)}
Dec 2, 2010 at 10:00 PM

We found the issue, the problem was not Deepearth, we had bad lat,lon values.

Please mark this as NOT A BUG.

Apr 20, 2011 at 2:45 PM

Hi,

I get the same exception which is thrown randomly. This is apparently not caused by bad lat/long values as we always use the same data set (and there is no known way to reproduce the issue). Could you please give us details about how you found the issue ?

Thanks