Latest Contributions by BjørnarSundsbø

Hi I just noticed that when I change an attribute on a Graphic (or just set the value to the same value it was), the event DictionaryChangedEvent is raised from the ObservableDictionary. In the Graphic, the DataContext is reassigned, and it might cause flicker or updates. I have not observed problems like that, but I started to wonder if there might be any penalties and unnecessary rebinding. It seems to me that when the DictionaryChangedEvent is raised, the value should actually have changed. So if newValue and oldValue are equal (Comparer.Default.Compare(e.OldValue, e.NewValue) == 0) the event should not be triggered. Just a suggestion for a future release. ... View more

I tried creating a custom clusterer (derived from GraphicsClusterer) to do the same as the FlareClusterer but without the flare effect. I then noticed that when I change the geometry of Graphics (realtime update from server where the Graphic geometry changes). Whenever this happens, all the Graphic objects on the screen flickers. The FlareClusterer gives the same effect. When removing any clusterer from the layer the rendering is smooth. I can't use clustering if it causes this kind of flickering. Is this the way clusterers works, or is there some inefficiencies in the clusterer that causes this? There are less than 15 graphics in all the layers being displayed, so this should not really cause poor performance. It appears as if the whole layer is cleared when clustering is reapplied after a change of geometry, and then redrawn, instead of only the features that have been affected by the change. I would think that would leave an even better performance perception. And/or when clustering is enabled, draw to a backbuffer in an ascync call, and then replace the entire content of the layer. Clustering as it is does not not perform well in a dynamic context. Are there any workarounds for this, or plans for improving this feature? I use the latest release (2.1). ... View more

Hi I've previously been working on a problem with dynamic centered offset for the symbol of a Graphic where the height and width of the symbol changes based on content. Post is linked to further down. I solved this using a custom IRenderer to produce a new symbol for each Graphic. I then fixed the offset of the symbol using my description from the same post (overrididing ArrangeOverride and measureOverride to calculate the offset of the symbol). However, there is a minor problem. Whenever a new symbol is created where I use i.e. binding to an attribute to the RenderTransform (rotateTransform), I get the following binding warning System.Windows.Data Error: 2 : Cannot find governing FrameworkElement or FrameworkContentElement for target element. BindingExpression:Path=Attributes[Bearing]; DataItem=null; target element is 'RotateTransform' (HashCode=17661557); target property is 'Angle' (type 'Double') the binding itself works, though not on the first attempt. The same is the case if I have i.e. a GradientBrush's GradientStop bind to an attribute. From the different suggestions I've seen for resolving this issue in other scenarios, they all suggest setting the DataContext before InitializeComponent() (in other words before applying the ControlTemplate). Is this something you could perhaps fix? From previous attempts where I don't create a new symbol (with controltemplate) for each Graphic, the same warning is output in visual studio, though only once for each symbol where I use this kind of binding. The following quote is a reminder of a suggestion from the post Location of PictureMarkerSymbol vs MarkerSymbol I was hoping to get some feedback on if it will be included soon or not. I'm looking into the links you sent me. It seems this is a thing more people would be interested in, and perhaps there could be a property on the MarkerSymbol for with an enum with the following values: Manual (uses manual offset values), CenterX (centers on the X axis), CenterY (centers on the Y axis), CenterBoth (center both X and Y). Pretty much like the SizeToContent property of a Window. Also, do you have an estimate for the next pre-release of 2.1? Or final release. I currently use the December build of 2.1. Bjørnar Sundsbø ... View more