New Post: AvalonDock - overlaying a floating window; zIndex issue

February 26, 2016, 2:23 pm

≪ Previous: New Post: AvalonDock - overlaying a floating window; zIndex issue

Great, thanks again for your input! I will go down this route then, and remove the HwndHost / FloatingWindowContentHost.
I'll post in here in case I encounter any bugs or side effects related to this in case anyone ever faces the same issue, but for now this way looks rather promising.
Have a great weekend

↧

New Comment on "PropertyGrid"

February 27, 2016, 1:05 pm

≫ Next: Commented Unassigned: How to get Keyboard Focus on the textbox of the TokenizedTextbox [22185]

≪ Previous: New Post: AvalonDock - overlaying a floating window; zIndex issue

BoucherS, I got it working. I think I made a mistake applying the correction you posted yesterday, but I've got that fixed and now everything is working as it is supposed to. Much thanks for your help.

↧

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

February 28, 2016, 3:04 pm

≫ Next: Edited Issue: How to get Keyboard Focus on the textbox of the TokenizedTextbox [22185]

≪ Previous: New Comment on "PropertyGrid"

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

See description for issue content.

↧

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

February 29, 2016, 7:27 am

≫ Next: Created Unassigned: PropertyGrid not thread safe for multiple ui threads [22187]

≪ Previous: Commented Unassigned: How to get Keyboard Focus on the textbox of the TokenizedTextbox [22185]

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

Hi,

This issue will be fixed in v3.0.
You will be able to call _tokenizedTextBox.Focus() and see the caret in the TokenizedTextBox.

In the meantime, you can go in file :
-Xceed/Wpf.Toolkit/TokenizedTextBox/Themes/Aero2.NormalColor.xaml (in windows 8)
-Xceed/Wpf.Toolkit/TokenizedTextBox/Themes/Generic.xaml (in other windows)
A) In the style for TokenizedTextBox,
Remove :
```
<Setter Property="Focusable"
Value="False"/>
```
Add
```
<Setter Property="IsTabStop"
Value="False"/>
```

B) In the ControlTemplate for TokenizedTextBox
In the triggers section, in the trigger "IsFocused == true",
Add the setter :
```
<Setter TargetName="PART_RichTextBox"
Property="FocusManager.FocusedElement"
Value="{Binding ElementName=PART_RichTextBox}" />
```

↧

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

March 1, 2016, 2:41 am

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

≪ Previous: Edited Issue: How to get Keyboard Focus on the textbox of the TokenizedTextbox [22185]

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 Unassigned: PropertyGrid not thread safe for multiple ui threads [22187]

March 1, 2016, 4:41 am

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

≪ Previous: Created Unassigned: PropertyGrid not thread safe for multiple ui threads [22187]

I tried to change the static readonly SelectedObjectAdvancedOptionsMenuKey to a normal member, but I still get the same exception when this.FindResource(...) is called.

↧

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

March 1, 2016, 8:31 am

≫ Next: Closed Unassigned: PropertyGrid not thread safe for multiple ui threads [22187]

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

Hi,

This is fixed in v2.5.

↧

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

March 1, 2016, 8:31 am

≫ Next: Edited Issue: NullReferenceException trying to use Zoombox [22079]

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

↧

Edited Issue: NullReferenceException trying to use Zoombox [22079]

March 1, 2016, 8:34 am

≫ Next: Edited Issue: 'Initialization of 'Xceed.Wpf.Toolkit.RangeSlider' threw an exception in VS2015 CTP6 [21739]

≪ Previous: Closed Unassigned: PropertyGrid not thread safe for multiple ui threads [22187]

Not sure why I'm getting this exception trying to use the Zoombox control. It is throwing the NullReferenceException because the parent grid is Colapsed.

System.NullReferenceException was unhandled
HResult=-2147467261
Message=Object reference not set to an instance of an object.
Source=Xceed.Wpf.Toolkit
StackTrace:
at Xceed.Wpf.Toolkit.Zoombox.Zoombox.SetScrollBars()
at Xceed.Wpf.Toolkit.Zoombox.Zoombox.Zoombox_Loaded(Object sender, RoutedEventArgs e)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs e)
at System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent)
at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(Object root)
at MS.Internal.LoadedOrUnloadedOperation.DoWork()
at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()
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 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
InnerException:

↧

Edited Issue: 'Initialization of 'Xceed.Wpf.Toolkit.RangeSlider' threw an exception in VS2015 CTP6 [21739]

March 1, 2016, 8:35 am

≫ Next: Edited Feature: [Feature]Split the controls of library [17736]

≪ Previous: Edited Issue: NullReferenceException trying to use Zoombox [22079]

Since installation of Visual Studion 2015 CTP6 RangeSlider gives as runtime error:

{"'Initialization of 'Xceed.Wpf.Toolkit.RangeSlider' threw an exception.' Line number '87' and line position '189'."}

{pack://application:,,,/Coolblue.Purchasing.CompetitorPricing;component/views/elasticitysettingsview.xaml}

{"Initialization of 'Xceed.Wpf.Toolkit.Core.VersionResourceDictionary' threw an exception."}

{"Cannot locate resource 'xceed.wpf.toolkit;v2.3.0.0;themes/xceed.wpf.toolkit;v2.3.0.0;component/themes/aero/brushes_normalcolor.xaml'."}

This did not happen before in Visual Studio 2015 Preview.

Dit something change in VS2015 CTP6 that broke this?

Thanks in Advance for any answers,
Antoni Dol

↧

Edited Feature: [Feature]Split the controls of library [17736]

March 1, 2016, 8:36 am

≫ Next: Edited Issue: The SelectedColor of ColorPicker is wrong. [21652]

≪ Previous: Edited Issue: 'Initialization of 'Xceed.Wpf.Toolkit.RangeSlider' threw an exception in VS2015 CTP6 [21739]

Split the controls of library in more libraries and create new nuget package for each library.

↧

Edited Issue: The SelectedColor of ColorPicker is wrong. [21652]

March 1, 2016, 8:36 am

≫ Next: Edited Issue: DateTime picker crashes with foreign cultures/custom TimeFormat [21479]

≪ Previous: Edited Feature: [Feature]Split the controls of library [17736]

Hello, I test 2.2.0 and 2.3.0. Both of them have the same issue.

Reproduce steps:
1. Let ColorPicker at the bottom of the screen, so the ColorPanel will extend upward.
2. Click the Colorbox and select a color.
3. The SelectedColor would be changed to the next row of the selected color.

This issue will occur at the first time to click the Colorbox.
I think it's the bug of showing resent color.
If ShowRecentColors is False, this issue will not occur.

↧

Edited Issue: DateTime picker crashes with foreign cultures/custom TimeFormat [21479]

March 1, 2016, 8:37 am

≫ Next: Edited Issue: PropertyName in Xceed.Wpf.Toolkit.PropertyGrid.PropertyItem [21639]

≪ Previous: Edited Issue: The SelectedColor of ColorPicker is wrong. [21652]

The date time picker control crashes when using foreign culture settings in windows e.g. German, Finnish.

These cultures use date stamps like 22.10.2014 1:05:07, 100

Iff you dont provide a custom FormatString the control will display, but wont allow interaction and will throw an uncaught exception if you attempt to open the calendar.

Additionally iff you stipulate a FormatString in XAML the app will crash with an XAML exception.

I tracked this bug in V 2.3 to the following:

DateTimeUpDown.cs line 559 - DateTime date = DateTime.Parse(Value.ToString());

I am not sure why this is there, Value is already a DateTime? so you can easily check if its null and if not extract the date time directly without using parse (an absolute nightmare function btw). Also upstream the Value is checked for null so worrying about null SHOULDN'T be an issue, although this would choke on null anyways.

My fix was: DateTime date = Value.Value;

Would still break on null, but SHOULD be safe to assume thats not an issue.

Maybe I am just having weird issues, but seems to be a bug to me.

Hope this helps :D

↧

Edited Issue: PropertyName in Xceed.Wpf.Toolkit.PropertyGrid.PropertyItem [21639]

March 1, 2016, 8:38 am

≫ Next: Edited Issue: ColorPicker control RecentColors bug [21628]

≪ Previous: Edited Issue: DateTime picker crashes with foreign cultures/custom TimeFormat [21479]

Based on discussion https://wpftoolkit.codeplex.com/discussions/576327.

↧

Edited Issue: ColorPicker control RecentColors bug [21628]

March 1, 2016, 8:38 am

≫ Next: Edited Issue: MessageBox FontSize also affects the caption [21638]

≪ Previous: Edited Issue: PropertyName in Xceed.Wpf.Toolkit.PropertyGrid.PropertyItem [21639]

RecentColors collection on ColorPicker control cannot be bound to in version 2.3.0

It is a simple dependency property default value issue.

Solution:

```
line 211 public static readonly DependencyProperty RecentColorsProperty = DependencyProperty.Register( "RecentColors", typeof( ObservableCollection<ColorItem> ), typeof( ColorPicker ), new UIPropertyMetadata( null ) );
```

should be

```
line 211 public static readonly DependencyProperty RecentColorsProperty = DependencyProperty.Register( "RecentColors", typeof( ObservableCollection<ColorItem> ), typeof( ColorPicker ), new UIPropertyMetadata( new ObservableCollection<ColorItem>() ) );
```

and remove line 452 in the constructor, which is breaking any binding:
```
RecentColors = new ObservableCollection<ColorItem>();
```

↧

Edited Issue: MessageBox FontSize also affects the caption [21638]

March 1, 2016, 8:39 am

≫ Next: Edited Feature: Support TimeSpan up/down negative values [21615]

≪ Previous: Edited Issue: ColorPicker control RecentColors bug [21628]

it shoul only affect the content.
Based on comments in page https://wpftoolkit.codeplex.com/wikipage?title=MessageBox&ANCHOR#C31181

↧

Edited Feature: Support TimeSpan up/down negative values [21615]

March 1, 2016, 8:39 am

≫ Next: Edited Feature: RangeSlider: Deferred update [21580]

≪ Previous: Edited Issue: MessageBox FontSize also affects the caption [21638]

It's a rare corner case, but it does happen. TimeSpans can be negative, so instead of returning null, the format should allow for that.

↧

Edited Feature: RangeSlider: Deferred update [21580]

March 1, 2016, 8:39 am

≫ Next: Edited Issue: Nested AvalonDock - Memory Leak [21567]

≪ Previous: Edited Feature: Support TimeSpan up/down negative values [21615]

In some applications, each update of the LowerValue or UpperValue binding causes expensive operations in the ViewModel. It is thus important that the slider does not update its LowerValue or UpperValue binding until the user releases the mouse button. This is a similar concept to the ScrollViewer's IsDeferredScrollingEnabled property.

↧

Edited Issue: Nested AvalonDock - Memory Leak [21567]

March 1, 2016, 8:40 am

≫ Next: Edited Issue: BusyIndicator size problem with binding [21239]

≪ Previous: Edited Feature: RangeSlider: Deferred update [21580]

I've described this problem already here: https://avalondock.codeplex.com/workitem/16060 and proposed a solution. Please review it.

A have one main docking manager and nested docking manager is displayed as document (in document tab in) main docking manager. If I close document, AutoHideWindow will never be disposed and this is memory leak.

↧

Edited Issue: BusyIndicator size problem with binding [21239]

March 1, 2016, 8:40 am

≫ Next: New Comment on "RichTextBoxFormatBar"

≪ Previous: Edited Issue: Nested AvalonDock - Memory Leak [21567]

The BusyIndicator got a problem with the width and binding.

When you got a big string as BusyContent and then you change it later on with a smaller string.
The width used is still from the long string.

I have made an example demonstrating the issue.
Ignore the button clicks i know normaly you use ICommand etc.

But it should show the problem.

Any workaround that are mvvm usable would be good. :)

↧