Our company is currently using both the Telerik Silverlight tools and the Silverlight Toolkit to accomplish what we need in our program. Since Silverlight is dying out and the Silverlight Toolkit has not been updated since 2011, we are removing all dependencies on the Silverlight Toolkit and trying to replace those controls with a Telerik Alternative so that we are not using both toolkits. This way our customers only needs to download a 5mb file rather than a 10mb fileI've gone through and removed just about every dependency except two, one of which is the ScrollViewer. We use the Scrollviewer several times to create a scrollable area within another grid etc. I've looked around and found that Telerik doesn't have a direct alternative to the ScrollViewer but they do have some scrolling functionality within their RadGridView. That won't exactly work for us, and either way it will be slow because is we put a RadGridView where the ScrollViewer is, we would be placing it in controls that have auto sizing or measure with infinity. According to Telerik's site: Try not to place RadGridView in controls/panels which will measure it with infinity. Either way that seems like it would be very cluttered in our case.I was wondering if there was some ScrollViewer alternative in Telerik that I'd be able to use. If worst comes to worst, does making our own custom ScrollViewer seem reasonable?Any help is appreciated. Thanks!
EDIT: More specifically, the ScrollIntoView() function in the ScrollViewerExtensions from the Silverlight 5 Toolkit needs replacing. If there is no other control that has the built in functionality to scroll to an object within the control, then I can probably just create the method myself.
I'm not sure if Telerik has similar ScrollViewer extensions, but one solution would be to copy-paste the relevant code from the Silverlight Toolkit source -- the ScrollViewerExtensions class.
Related
Currently I would like to program an application gathering forms that are callable with buttons on the side. For this, I am using the latest build of Visual Studio Community. One way I thought of would be to literally put all the form elements (textboxes, lists, etc.) in the application window and only enable them whenever the according button is clicked on. However, if this is the way to do it, I find it quite messy and unpractical, and I'm pretty sure there's another way around.
After some research, I have learned about the MDI layouts, but they don't suit my taste. I would like to keep everything in one single frame.
Could you give me a hand?
I would like to have a ComboBox that handles large amounts of content by loading them asynchronously inside a Loader, so I can display a little BusyIndicator over the drop-down.
Is it maybe possible to achieve this through a style? I want to avoid having to recreate a ComboBox from scratch.
No. It may be possible in the future, though:
This one is a bit tricky to get right, and is still work in progress. It is not difficult to style the popup background, the same way it's currently doable for MenuStyle. What remains, as you pointed out, is to make that API public.
What we can't promise, is to be able to style the popup window shape. If QtQuick was backing store based, then most platforms support shaping the window. But QtQuick is OpenGL based, and desktop platforms support this in different ways. On mobile and embedded platforms, we can't use a separate window, so we need to build an abstraction that would use Item-based popups.
I'd suggest voting for and watching QTBUG-39476 if you're interested in this feature and don't want to write your own ComboBox.
Im authoring some Windows 8 Metro template (custom) controls and there doesnt seem to me any LayoutTransform properties on anything.
this is a real pain, as I want to rotate some text 90 desgrees, but the grid is sizing to the size of the text before the rotation.
Does anyone have an idea on how to fix this without writing lots of hacks ?
Dean
I modified the Silverlight toolkit version and published it here
Layout transform in Windows 8 XAML
LayoutTransform was gone in Silverlight too. (IMHO) I guess maybe it was usually overused or abused in WPF causing performance issues, so for better perception of the framework - it was never added to Silverlight and by extension - to WinRT.
There seems to be a workaround for that in the Silverlight Toolkit that should be easy to port - check the LayoutTransformer control. I have never used it, but it sounds like what you need.
*Edit 2017-04-24
There's a LayoutTransformControl in WinRT XAML Toolkit you could use.
I am trying to load bulk images and trying to put them as a slideshow and it's working fine.
Now I would like to have some effects like flip out,ease out effect and fade effect on those images when changing them without using any user control as I would like to do with the existing picturebox.Is it possible to do so?
If so can anyone point me to some resources.
As I have done googling and found some useful links and I am placing here that might helpful to someone.And all these have use seperate usercontrols to do, and I am not looking into that.
http://code.google.com/p/dot-net-transitions/
http://www.codeproject.com/KB/cpp/fluid_effect.aspx
The built-in picture box has no such capability. Your solution will require custom-drawing regardless what control you use (assuming you don't get a 3rd party product).
The Silverlight 3 toolkit has a ChildWindow control for model popup like functionality. This is great. Anyone aware of a similar control that can be utilized via XBAP?
http://silverlight.codeplex.com/wikipage?title=Silverlight%20Toolkit%20Overview%20Part%204&referringTitle=Silverlight%20Toolkit%20Overview%20Part%203
The assumption is maybe someone ported the functionality back to WCF/XBAP?
Trying to find a solution without going to 3rd party purchased controls (against current company policy).
Don't know that you'll get this to work without FullTrust (FullTrust XBAPs are a PITA until .NET 4). Here's a psuedo-workaround though- not as nice as SL ChildWindow, but it gets you basic popup functionality.
In theory couldn't you rebuild the ChildWindow source and massage it a little to work on WPF? Most of the controls are WPF compatible, so it would make sense to build ChildWindow for XBAPs.