Advanced Forum Search Results
-
Try Using the WPF "WebBrowser" Control.
Or use the Windows Forms "WebBrowser" Control.
It's basically like running a mini "Internet Explorer" in your app.
Hopefully these can host Silverlight, so then you could interact with the Silverlight component through the HTML DOM, and maybe even javascript.
If you also ...
-
I came up with a workaround. Now I just set the selected index on layout_updated.
-
Line:
134
Char:
9
Error:
Unhandled Error in Silverlight 2 Application
Code: 4004
Category: ManagedRuntimeError
Message: System.ArgumentException: Value does not fall within the expected range.
at MS.Internal.XcpImports.MethodEx(IntPtr ptr, String name, ...
-
Actually,
The Usercontrol does have a background property, aswell as border brush and thickness properties.
If only they worked.
And what sucks most is that the Border Class is Declared NotInheritable!!
Really they should just replace UserControl with Border and Flag it inheritable and fix the xaml rendering ...
-
The Devs made a wrong turn on this one.
Dim BlackStop1 As New GradientStop
BlackStop1.Color = Colors.Black
BlackStop1.Offset = 0.0
Dim TransStop1 As New ...
-
In Silverlight 2 Beta 2. The Loaded event would occur once the control was rendered, now in the Release it seems to Happen before.
This broke my workaround for an issue with the scrollviewer class being rendered with too many child objects at once (causing many height calculations and whatnot)
Silverlight Devs, take these ...
-
I have a solution for all who are using the scroll viewer and recieving this error: "Layout cycle detected. Layout could not complete"
I was recieving this error when I added to many items into the Scroll Viewer at once not sure the exact number or the exact height that triggered it but my solution was to add the next item in the list ...
-
I have a button that appears on an element and is required to show on mouseover, and hide on mouseleave of that element.
-This works fine
When the button is clicked it creates a popup overtop of the area, "This causes the mouseleave event to fire and the button to hide with Visisbility = collapsed.
-This causes the Application ...
-
Thanks again
-
Thanks,
I'll have to look into AcceptsReturn some more, I just assumed it meant the box will fire and event from the return key.