Quantcast
Channel: Extended WPF Toolkit™ Community Edition
Viewing all 4964 articles
Browse latest View live

New Comment on "RichTextBoxFormatBar"

$
0
0
I am unable to get this to display in my wpf application. This needs much better documentation.

New Comment on "RichTextBoxFormatBar"

$
0
0
Hi, Try something like this : <xctk:RichTextBox Margin="5" Width="350"> <xctk:RichTextBoxFormatBarManager.FormatBar> <xctk:RichTextBoxFormatBar /> </xctk:RichTextBoxFormatBarManager.FormatBar> <xctk:RichTextBox.Document> <FlowDocument> <Paragraph>This is the <Bold>RichTextBox</Bold> ! </Paragraph> </FlowDocument> </xctk:RichTextBox.Document> </xctk:RichTextBox>

Commented Unassigned: PropertyGrid not thread safe for multiple ui threads [22187]

$
0
0
Hi,

I recently discovered a bug in version 2.4.0.0 (I guess newer versions are affected as well):

If you start two property grid instances in two windows with different UI Threads, you will get an InvalidOperationException like the following:

```
System.Windows.Markup.XamlParseException occurred
_HResult=-2146233087
_message=Initialization of 'Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid' threw an exception.
HResult=-2146233087
IsTransient=false
Message=Initialization of 'Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid' threw an exception.
Source=PresentationFramework
LineNumber=0
LinePosition=0
StackTrace: at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
InnerException: System.InvalidOperationException
_HResult=-2146233079
_message=The calling thread cannot access this object because a different thread owns it.
HResult=-2146233079
IsTransient=false
Message=The calling thread cannot access this object because a different thread owns it.
Source=WindowsBase
StackTrace:
at System.Windows.Threading.DispatcherObject.VerifyAccess()
at System.Windows.SystemResources.FindCachedResource(Object key, Object& resource, Boolean mustReturnDeferredResourceReference)
at System.Windows.SystemResources.FindResourceInternal(Object key, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference)
at System.Windows.FrameworkElement.FindResourceInternal(FrameworkElement fe, FrameworkContentElement fce, DependencyProperty dp, Object resourceKey, Object unlinkedParent, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference, DependencyObject boundaryElement, Boolean isImplicitStyleLookup, Object& source)
at System.Windows.FrameworkElement.FindResource(Object resourceKey)
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.UpdateContainerHelper() in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 872
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.EndInit() in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 1121
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(XamlType xamlType, Object obj, Boolean begin)
InnerException:

```

The root cause is the static readonly member "SelectedObjectAdvancedOptionsMenuKey", which is not properly initialized for every UI Thread. This is done just once, as it is static. Depending on which UI thread accesses this member, it may or may not fail.

I'll attach a demo project which demonstrates the issue.
Comments: ** Comment from web user: AndreasBa **

Hi,

I just tested it with v2.6 - the reported issue still exists!

* I am starting a window in its own UI thread.
* The window contains a propertygrid. At some time I close the window and stop the dispatcher.
* At a later stage I decide to start a new instance of the same window class in new UI Thread (with it's own dispatcher).
* When this window is created, I get the exception reported below

```
exception Details (key=value): (System.Object=) System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
at System.Windows.Threading.Dispatcher.VerifyAccess()
at System.Windows.Threading.DispatcherObject.VerifyAccess()
at System.Windows.SystemResources.FindCachedResource(Object key, Object& resource, Boolean mustReturnDeferredResourceReference)
at System.Windows.SystemResources.FindResourceInternal(Object key, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference)
at System.Windows.FrameworkElement.FindResourceInternal(FrameworkElement fe, FrameworkContentElement fce, DependencyProperty dp, Object resourceKey, Object unlinkedParent, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference, DependencyObject boundaryElement, Boolean isImplicitStyleLookup, Object& source)
at System.Windows.FrameworkElement.FindResource(Object resourceKey)
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.UpdateContainerHelper() in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 888
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.OnSelectedObjectChanged(Object oldValue, Object newValue) in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 452
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.OnSelectedObjectChanged(DependencyObject o, DependencyPropertyChangedEventArgs e) in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 440
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.OnPropertyChanged(DependencyPropertyChangedEventArgs e) in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 807
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.InvalidateProperty(DependencyProperty dp, Boolean preserveCurrentValue)
at System.Windows.Data.BindingExpressionBase.Invalidate(Boolean isASubPropertyChange)
at System.Windows.Data.BindingExpression.TransferValue(Object newValue, Boolean isASubPropertyChange)
at System.Windows.Data.BindingExpression.Activate(Object item)
at System.Windows.Data.BindingExpression.AttachToContext(AttachAttempt attempt)
at System.Windows.Data.BindingExpression.MS.Internal.Data.IDataBindEngineClient.AttachToContext(Boolean lastChance)
at MS.Internal.Data.DataBindEngine.Task.Run(Boolean lastChance)
at MS.Internal.Data.DataBindEngine.Run(Object arg)
at MS.Internal.Data.DataBindEngine.OnLayoutUpdated(Object sender, EventArgs e)
at System.Windows.ContextLayoutManager.fireLayoutUpdateEvent()
at System.Windows.ContextLayoutManager.UpdateLayout()
at System.Windows.ContextLayoutManager.UpdateLayoutCallback(Object arg)
at System.Windows.Media.MediaContext.InvokeOnRenderCallback.DoWork()
at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.Resize(ICompositionTarget resizedCompositionTarget)
at System.Windows.Interop.HwndTarget.OnResize()
at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
```

For me it seems like the new property grid in the window is caching some data created by the previous UI thread. I just cannot find out what it is.

Could you probably re-open this issue?

Reopened Unassigned: PropertyGrid not thread safe for multiple ui threads [22187]

$
0
0
Hi,

I recently discovered a bug in version 2.4.0.0 (I guess newer versions are affected as well):

If you start two property grid instances in two windows with different UI Threads, you will get an InvalidOperationException like the following:

```
System.Windows.Markup.XamlParseException occurred
_HResult=-2146233087
_message=Initialization of 'Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid' threw an exception.
HResult=-2146233087
IsTransient=false
Message=Initialization of 'Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid' threw an exception.
Source=PresentationFramework
LineNumber=0
LinePosition=0
StackTrace: at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
InnerException: System.InvalidOperationException
_HResult=-2146233079
_message=The calling thread cannot access this object because a different thread owns it.
HResult=-2146233079
IsTransient=false
Message=The calling thread cannot access this object because a different thread owns it.
Source=WindowsBase
StackTrace:
at System.Windows.Threading.DispatcherObject.VerifyAccess()
at System.Windows.SystemResources.FindCachedResource(Object key, Object& resource, Boolean mustReturnDeferredResourceReference)
at System.Windows.SystemResources.FindResourceInternal(Object key, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference)
at System.Windows.FrameworkElement.FindResourceInternal(FrameworkElement fe, FrameworkContentElement fce, DependencyProperty dp, Object resourceKey, Object unlinkedParent, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference, DependencyObject boundaryElement, Boolean isImplicitStyleLookup, Object& source)
at System.Windows.FrameworkElement.FindResource(Object resourceKey)
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.UpdateContainerHelper() in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 872
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.EndInit() in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 1121
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(XamlType xamlType, Object obj, Boolean begin)
InnerException:

```

The root cause is the static readonly member "SelectedObjectAdvancedOptionsMenuKey", which is not properly initialized for every UI Thread. This is done just once, as it is static. Depending on which UI thread accesses this member, it may or may not fail.

I'll attach a demo project which demonstrates the issue.

Commented Issue: How to get Keyboard Focus on the textbox of the TokenizedTextbox [22185]

$
0
0
How do we programmatically assign Keyboard focus to the textbox component of the TokenizedTextbox control?
Comments: ** Comment from web user: poocherelo **

Thanks for your response and for your workaround. Any idea when version 3.0 is coming out?

Commented Issue: How to get Keyboard Focus on the textbox of the TokenizedTextbox [22185]

$
0
0
How do we programmatically assign Keyboard focus to the textbox component of the TokenizedTextbox control?
Comments: ** Comment from web user: BoucherS **

Hi,

Current users for Community edition have v2.6.
Current users for Plus Edition have v2.9.

Release v3.0 for "Plus" users should be released soon (in weeks).
realease v2.7 for "Community" users should be released at about the same time as v3.0.

Created Unassigned: Messagebox hidden [22192]

$
0
0
I have a WPF application embedded in a third-party software. My WPF app only has user controls and no windows at all. What does happen is if I call XCeed.Wpf.Toolki.Messagebox.Show(...), click on any other opened app and come back to mine, then the messagebox is hidden behind and it is pretty hard to bring it back. I must kill my app because it his waiting for the user to take action on a hidden messagebox.

I then tried to create an instance of the class and call ShowDialog and play with events, but there is no button, icon and defaultButton properties???

How could I get this messagebox working like the default Windows one? It is almost perfect, unless we click on another app and then we must kill it.

Thank you

Created Unassigned: TimeSpanUpDown allows letters and long numbers [22193]

$
0
0
TimeSpanUpDown allows letters and long numbers when typing into input areas. That should be generally blocked. It really has no sense to allow the user to change 00:08:00 to 00:0aaaabbbbbccccc:00.

Edited Issue: Messagebox hidden [22192]

$
0
0
I have a WPF application embedded in a third-party software. My WPF app only has user controls and no windows at all. What does happen is if I call XCeed.Wpf.Toolki.Messagebox.Show(...), click on any other opened app and come back to mine, then the messagebox is hidden behind and it is pretty hard to bring it back. I must kill my app because it his waiting for the user to take action on a hidden messagebox.

I then tried to create an instance of the class and call ShowDialog and play with events, but there is no button, icon and defaultButton properties???

How could I get this messagebox working like the default Windows one? It is almost perfect, unless we click on another app and then we must kill it.

Thank you
Comments: ** Comment from web user: BoucherS **

Hi,

This is fixed in v2.7. The MessageBox is not hidden anymore.

Current users of the Plus version have Toolkit v2.9.
Current users of the Community edition have Toolkit v2.6.

Next versions will be
-For Plus users : Toolkit v3.0
-For Community users : Toolkit v2.7

Commented Unassigned: PropertyGrid not thread safe for multiple ui threads [22187]

$
0
0
Hi,

I'll just reopend this issue - I just tested it with v2.6 but the reported issue still exists!

* I am starting a window in its own UI thread.
* The window contains a propertygrid. At some time I close the window and stop the dispatcher.
* At a later stage I decide to start a new instance of the same window class in new UI Thread (with it's own dispatcher).
* When this window is created, I get the exception reported below
```
exception Details (key=value): (System.Object=) System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
at System.Windows.Threading.Dispatcher.VerifyAccess()
at System.Windows.Threading.DispatcherObject.VerifyAccess()
at System.Windows.SystemResources.FindCachedResource(Object key, Object& resource, Boolean mustReturnDeferredResourceReference)
at System.Windows.SystemResources.FindResourceInternal(Object key, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference)
at System.Windows.FrameworkElement.FindResourceInternal(FrameworkElement fe, FrameworkContentElement fce, DependencyProperty dp, Object resourceKey, Object unlinkedParent, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference, DependencyObject boundaryElement, Boolean isImplicitStyleLookup, Object& source)
at System.Windows.FrameworkElement.FindResource(Object resourceKey)
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.UpdateContainerHelper() in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 888
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.OnSelectedObjectChanged(Object oldValue, Object newValue) in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 452
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.OnSelectedObjectChanged(DependencyObject o, DependencyPropertyChangedEventArgs e) in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 440
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at Xceed.Wpf.Toolkit.PropertyGrid.PropertyGrid.OnPropertyChanged(DependencyPropertyChangedEventArgs e) in z:\Test\PropertyGridTest\ToolkitSrc\Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\PropertyGrid\Implementation\PropertyGrid.cs:line 807
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.InvalidateProperty(DependencyProperty dp, Boolean preserveCurrentValue)
at System.Windows.Data.BindingExpressionBase.Invalidate(Boolean isASubPropertyChange)
at System.Windows.Data.BindingExpression.TransferValue(Object newValue, Boolean isASubPropertyChange)
at System.Windows.Data.BindingExpression.Activate(Object item)
at System.Windows.Data.BindingExpression.AttachToContext(AttachAttempt attempt)
at System.Windows.Data.BindingExpression.MS.Internal.Data.IDataBindEngineClient.AttachToContext(Boolean lastChance)
at MS.Internal.Data.DataBindEngine.Task.Run(Boolean lastChance)
at MS.Internal.Data.DataBindEngine.Run(Object arg)
at MS.Internal.Data.DataBindEngine.OnLayoutUpdated(Object sender, EventArgs e)
at System.Windows.ContextLayoutManager.fireLayoutUpdateEvent()
at System.Windows.ContextLayoutManager.UpdateLayout()
at System.Windows.ContextLayoutManager.UpdateLayoutCallback(Object arg)
at System.Windows.Media.MediaContext.InvokeOnRenderCallback.DoWork()
at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.Resize(ICompositionTarget resizedCompositionTarget)
at System.Windows.Interop.HwndTarget.OnResize()
at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
```

For me it seems like the new property grid in the window is caching some data created by the previous UI thread. I just cannot find out what it is.

Do you have any idea?
Comments: ** Comment from web user: BoucherS **

Hi,

I tried your sample in v2.6 and you are right, I got the exception.
Same thing in v2.7.
But for v2.8 and up, the sample is working normally.

Edited Issue: TimeSpanUpDown allows letters and long numbers [22193]

$
0
0
TimeSpanUpDown allows letters and long numbers when typing into input areas. That should be generally blocked. It really has no sense to allow the user to change 00:08:00 to 00:0aaaabbbbbccccc:00.
Comments: ** Comment from web user: BoucherS **

Hi,

This will be fixed in v3.0.
Thanks.

Commented Issue: Messagebox hidden [22192]

$
0
0
I have a WPF application embedded in a third-party software. My WPF app only has user controls and no windows at all. What does happen is if I call XCeed.Wpf.Toolki.Messagebox.Show(...), click on any other opened app and come back to mine, then the messagebox is hidden behind and it is pretty hard to bring it back. I must kill my app because it his waiting for the user to take action on a hidden messagebox.

I then tried to create an instance of the class and call ShowDialog and play with events, but there is no button, icon and defaultButton properties???

How could I get this messagebox working like the default Windows one? It is almost perfect, unless we click on another app and then we must kill it.

Thank you
Comments: ** Comment from web user: ericpapa **

Those are great news! At my previous position we were having the Plus Edition. At actual job we use the Community one. I found a work-around by creating a window at runtime with topmost property in my XCeedDialogService class I've implemented, added a WindowContainer in which I put my messagebox and had to create a lambda local to set the result on close and close the window within the save method to mimic the regular behavior of a messagebox.

With my trick, I was able to use the dialog as follow : this.DialogService.Show(....), but inside the definition of the method, instead of using directly XCeed.WPF.ToolKit.Messagebox.Show, i had to to the tricks mentionned above.

I'm happy to hear that this will be fixed. Do you know when that release is planned?
Thank you so much for your help.

Commented Issue: Messagebox hidden [22192]

$
0
0
I have a WPF application embedded in a third-party software. My WPF app only has user controls and no windows at all. What does happen is if I call XCeed.Wpf.Toolki.Messagebox.Show(...), click on any other opened app and come back to mine, then the messagebox is hidden behind and it is pretty hard to bring it back. I must kill my app because it his waiting for the user to take action on a hidden messagebox.

I then tried to create an instance of the class and call ShowDialog and play with events, but there is no button, icon and defaultButton properties???

How could I get this messagebox working like the default Windows one? It is almost perfect, unless we click on another app and then we must kill it.

Thank you
Comments: ** Comment from web user: BoucherS **

Hi,

We don't have the exact release dates, but it shouldn't be too long. In weeks.
Thanks.

New Comment on "Documentation"

$
0
0
is it possible to download "BusyIndicator" lib only?

New Comment on "CheckListBox"

$
0
0
If i add item to SelectedItems by use SelectedItems.Add(object) , the ItemSelectionChanged event raise , this is fine but when i check SelectedValue i do not find the value of this object. This also apply when i remove an item SelectedItems.Remove(object)

New Comment on "ValueRangeTextBox"

$
0
0
What are valid ValueDataTypes? I cannot set anything (string, Int32, etc.) in XAML or code)

New Comment on "Documentation"

$
0
0
Hi, The BusyIndicator is part of the Toolkit library. You cannot download only the busyIndicator.

New Post: CheckListBox : SelectedValue not updated on SelectedItems.Add/Remove

$
0
0
A user wrote :
"If i add item to SelectedItems by use SelectedItems.Add(object) , the ItemSelectionChanged event raise , this is fine but when i check SelectedValue i do not find the value of this object.

This also apply when i remove an item SelectedItems.Remove(object)"

New Post: CheckListBox : SelectedValue not updated on SelectedItems.Add/Remove

$
0
0
I cannot reproduce the bug. Can you submit a sample ?
Here's one that works :
<StackPanel>
        <xctk:CheckListBox x:Name="_checkListBox"/>
       <TextBlock Text="{Binding SelectedValue, ElementName=_checkListBox}"/>
       <Button Content="ADD" Click="Button_Click"/>
    </StackPanel>
 public MainWindow()
    {
      InitializeComponent();

      _checkListBox.ItemsSource = new ObservableCollection<string>()
      {
         "Price",
        "Subban",
        "Galchenyuk",
      };
    }

    private void Button_Click( object sender, RoutedEventArgs e )
    {
      _checkListBox.SelectedItems.Add( "Subban" );
    }

New Comment on "ValueRangeTextBox"

$
0
0
Hi, here are examples : <xctk:ValueRangeTextBox MinValue="10" MaxValue="20" ValueDataType="{x:Type s:Int32}"/> <xctk:ValueRangeTextBox MinValue="0" MaxValue="10" ValueDataType="{x:Type s:Double}"/> <xctk:ValueRangeTextBox MinValue="0" MaxValue="10" ValueDataType="{x:Type s:String}"/>
Viewing all 4964 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>