Advanced Forum Search Results
-
Considering the complexity of the current approach, it sounds to me that this is where you should put your focus. It shouldn't be this hard to get the version number. Your suggested solution using an API sounds more like a workaround than a solution.
Furthermore I question the real use-case here. If I publish an app, all I really need to care ...
-
Check my approach: www.sharpgis.net/.../Doubleclicking-in-Silverlight.aspx
-
It's not a dblclick if the mouse moves between the two clicks, but your code allows for that.
-
So are you saying that while this doesn't work:
<Point X="0" Y="{Binding Size}" />
This will work ?:
<Point X="0" Y="{TemplateBinding Size}" />
I will also need custom value converters to ...
-
Nevermind. It works just fine without typos :-)
-
This seems to work, with respect to that Silverlight is not crashing, but it doesn't seem to have any effect though. Not sure why, because as far as I can tell, this should be how you do it:
<ObjectAnimationUsingKeyFrames BeginTime="00:00:00" Duration="0" Storyboard.TargetName="Root" ...
-
So for whatever reason, you cannot bind to DependencyObjects in Silverlight as you can in WPF (bummer!). Therefore I'm looking for a workaround for doing something like this:
<Polygon Fill="{Binding Symbol.Color}" >
<Polygon.Points>
...
-
I can get this to work if my included namespace are in a different assembly than the one that does the call to Load(xaml). But if I'm referencing the local assembly, it will fail with the same unknown error. Seems stupid that I must declare my custom types in a separate assembly.
This happens both with and without specifying the assembly name ...
-
I couldn't agree more with JackBond. The pattern used above is horrible.
Just to add to the above example. I would use lazy instantiation, as well as making sure it's thread safe (see en.csharp-online.net/Singleton_design_pattern:_Thread-safe_Singleton)
-
So this is how you do it in WPF if Control2 is inside the template of Control1:
Control="{Binding RelativeSource={RelativeSource TemplatedParent}}"
I can do similar RelativeSource bindings if its outside. Why are the bindings in Silverlight so poor compared to WPF? (and don't say because of download size!)
It really seems ...