New Comment on "RichTextBoxFormatBar"
New Comment on "RichTextBoxFormatBar"
New Post: Facing few issues with Richtext formatbar
We are using Richtextcontrol in our project, and
we are facing few issues with Richtext formatbar.
1) If we enter text with line space and then if we do bulleting/Numbering then line space are also bulleted.
2)for bulleting/Numbering Text if change the alignment only text will be alligne not the bulleting.
3)All font changes (Font, Color & Background color) goes off, while selecting text with different background color, font size, text color.
Please let us know how to fix these issues or any workaround.
Regards,
Pavithra
Commented Issue: PropertyGrid of Version 1.9 has problem with float properties [19619]
see attachment.
thanks
Comments: ** Comment from web user: BoucherS **
After trying your sample with v1.9 of the toolkit, The Up/Down keys of the NumericUpDown are not available for float items.
In v2.0 of the toolkit, everything looks good. This version should be available soon.
Edited Issue: MouseWheelActiveOnFocus="True" [19608]
Previous 1.8.0.0 work as expected by update filed with mouse wheel if mousepointer is over field without focus.
But since 1.9.0.0 only "false" mode with focused filed working.
New Post: CalculatorUpDown, how i can update the input field value ?
Created Feature: CalculatorUpDown, how i can update the input field value ? [19627]
The person here
-=-=-=-=-=-=-=-=-=-
Hello,
how i can update corresponding up / down field value with calcualtor value if enter or '=' is pressed ?
PS : without any calculation, only enter number and press enter ('=')
Thanks,
regards
Marcus
Commented Issue: Unable to load several versions of the toolkit into the same AppDomain [19433]
We have a software which allows to add custom features by plugins. Plugins may add their own GUI with own panels, controls, etc. For different reasons it is essential that all plugins and the host software run in the same AppDomain. We recently got into the situation where two plugins used a different version of the WPF toolkit. In this scenario every time a panel was opened which contained a WPF toolkit control the software stopped working because of a missing resource. It turned out that the wrong version of the toolkit was used to resolve the resource.
After digging further into the issue we could locate the root cause in the merged resource dictionary in Main\Source\ExtendedWPFToolkitSolution\Src\Xceed.Wpf.Toolkit\Themes\Generic.xaml:
The merged resource dictionary doesn't specify a specific version for the other resource dictionaries. So the fix which worked for us is to change it from:
```
<ResourceDictionary.MergedDictionaries>
<ResourceDictionary Source="/Xceed.Wpf.Toolkit;component/Themes/Generic/Brushes.xaml" />
<ResourceDictionary Source="/Xceed.Wpf.Toolkit;component/Themes/Generic/Buttons.xaml" />
...
</ResourceDictionary.MergedDictionaries>
```
to:
```
<ResourceDictionary.MergedDictionaries>
<ResourceDictionary Source="/Xceed.Wpf.Toolkit;v1.9.0.0;component/Themes/Generic/Brushes.xaml" />
<ResourceDictionary Source="/Xceed.Wpf.Toolkit;v1.9.0.0;component/Themes/Generic/Buttons.xaml" />
...
</ResourceDictionary.MergedDictionaries>
```
This way the correct version of the resources will be resolved. The full solution would likely include a way to insert the current assembly version where I hard coded 1.9.0.0.
Would it be possible to add this fix to one of the next releases?
Best regards
Christian
Comments: ** Comment from web user: emartin **
The problem is that just adding the "VersionSafeResourceDictionary" to the Generic.xaml file won't make the Toolkit work properly.
Here what the issues we found:
1)
All "absolute" pack uri like <Image Source="/Xceed.Wpf.Toolkit;component/MyRes.png />in the resources files were also referring to the wrong assembly.
2)
Each places were a resource use a static reference to one of the assembly type or value to identify a key (ex. <Style x:Key="{x:Static tk:MyType.MyProp}" ... />) the result may end with the wrong value or a crash if the property doesn't exist in the "wrong" version of the toolkit.
However concerning the issue #1, this has been fixed by replacing all our references to relative uri.
For #2, We didn't had time to review and replace all theses usage with the "{ComponentResourceKey }" syntax that will probably fix the issue. It is not very long but since the tests has already been started this fix won't make the cut for v2.0. We will check this for v2.1.
New Post: Arrow mark is not visble
One more thing is, on assigning ExpandableObject attribute to property, it is not expanding at all... Do we need to write any extra code for happening of the same?
Please help me out here.... Very urgent...
New Post: CheckListBox and ItemsSource
This issue is fixed in v2.0 of the toolkit.Hi,
Could you please indicate when v2.0 will be available? I received the same type of error. Version I'm using: 1.9.0.0
Kind regards,
New Post: CheckListBox and ItemsSource
New Post: DataGrid: Change the "Drag a column ..." text
thank for your comment
Commented Issue: Could not load file or assembly Xceed.Wpf.Toolkit.Aero2 [19506]
-----------
Hi,
I added the DoubleUpDown control to a DataGrid and when the first row is initialized I get following IO Exception:
> Could not load file or assembly 'Xceed.Wpf.Toolkit.Aero2, Version=1.9.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4' or one of its dependencies. The system cannot find the file specified.
When I continue, the application runs anyway and the control is shown and works. Do you have any idea what causes this exception and how I can get rid of it? If you need specific code I can provide it.
I use Caliburn.Micro as the underlying framework. The dll mentioned in the exception is nowhere to be found and it's not available in the zip that is provided on this webpage. I installed Extended WPF Toolkit via NuGet.
Cheers,
Daniel Fox
Comments: ** Comment from web user: shaper **
Hi,
same problem here. Cannot use any of the Xceed controls because of this error. I'm working with VS2012 ultimate.
Updated Wiki: Extended WPF Toolkit Plus
Develop better and faster
Upgrade to Extended WPF Toolkit Plus to get a year's worth of priority support, extra controls, extra features, early access to updates, and more. All for only $180.Not only will you get more features and great support, but you'll support the project. You'll help ensure Xceed can continue to release great updates with new controls, features, and tons of fixes and improvements many times a year. Currently we have two full-time developers that are exclusively working on Extended WPF Toolkit, and as many .NET/WPF technical support engineers as needed to ensure all priority support questions are answered. We can only do this with your support.
<a class="coinbase-button" data-code="c9b292432875c2e71734eeef22203ff0" href="https://coinbase.com/checkouts/c9b292432875c2e71734eeef22203ff0">Pay With Bitcoin</a><script src="https://coinbase.com/assets/button.js" type="text/javascript"></script>
Check out Extended WPF Toolkit Plus
Buy it now: add to cart
Check out Xceed Business Suite for WPF
---Buy it now: add to cart (with $400 coupon applied)
Updated Wiki: Extended WPF Toolkit Plus
Develop better and faster
Upgrade to Extended WPF Toolkit Plus to get a year's worth of priority support, extra controls, extra features, early access to updates, and more. All for only $180.Not only will you get more features and great support, but you'll support the project. You'll help ensure Xceed can continue to release great updates with new controls, features, and tons of fixes and improvements many times a year. Currently we have two full-time developers that are exclusively working on Extended WPF Toolkit, and as many .NET/WPF technical support engineers as needed to ensure all priority support questions are answered. We can only do this with your support.
Check out Extended WPF Toolkit Plus
Buy it now: add to cart
Check out Xceed Business Suite for WPF
---Buy it now: add to cart (with $400 coupon applied)
Closed Issue: WPFToolkit.Extended.classic.dll filenotfoundexception [18971]
Comments: Close as duplicate of 153867
See https://wpftoolkit.codeplex.com/workitem/19517
Reopened Issue: WPFToolkit.Extended.classic.dll filenotfoundexception [18971]
Commented Issue: WPFToolkit.Extended.classic.dll filenotfoundexception [18971]
Comments: ** Comment from web user: emartin **
CORRECTION:
Ignore previous close
Closed Issue: WPFToolkit.Extended.classic.dll filenotfoundexception [18971]
Comments: Duplicate of 19517
https://wpftoolkit.codeplex.com/workitem/19517
Commented Issue: Missing Assembly: Xceed.Wpf.Toolkit.Luna [19517]
Everything seems to work without this assembly.
Comments: ** Comment from web user: emartin **
Theses issues can be considered as duplicates:
[Issue 18971](https://wpftoolkit.codeplex.com/workitem/18971)
[Issue 19506](https://wpftoolkit.codeplex.com/workitem/19506)