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

Commented Issue: CheckComboBox doesn't bind SelectedValue when placed in a DataTemplate [20091]

$
0
0
Based on discussion https://wpftoolkit.codeplex.com/discussions/453536
Comments: ** Comment from web user: emartin **

When the sources will be releases, the binaries will also be releases, so you could also only grab the binaries without the need to compile the sources


New Post: Problem with Propertygrid and fonts

New Post: Propertygrid password

$
0
0
I ended up using an ITypeEditor:
public class PasswordEditor : Xceed.Wpf.Toolkit.PropertyGrid.Editors.ITypeEditor
{
    Xceed.Wpf.Toolkit.PropertyGrid.PropertyItem m_PropertyItem;
    PasswordBox m_PasswordBox;

    public FrameworkElement ResolveEditor(Xceed.Wpf.Toolkit.PropertyGrid.PropertyItem propertyItem)
    {
        m_PropertyItem = propertyItem;
        m_PasswordBox = new PasswordBox();
        m_PasswordBox.Password = (String)propertyItem.Value;
        m_PasswordBox.LostFocus += OnLostFocus; 
        return m_PasswordBox;
    }

    void OnLostFocus(object sender, RoutedEventArgs e)
    {
        if (0 != m_PasswordBox.Password.CompareTo((string)m_PropertyItem.Value))
        {
            m_PropertyItem.Value = m_PasswordBox.Password;
        }
    }
}

Closed Feature: Setting Min Date and Max Date for DatePicker Control [20088]

$
0
0
Hello All,


Need help on setting Minimum Date and Maximum Date in Xceed DateTimePicker Control.


Thanks and Regards
Parth Patel
Comments: Please use the discussion tab to request for help.

Created Issue: DateTimePicker Min/Max are not reflected in dropdown calendar [20490]

$
0
0
If I set a min and a max on the DateTimePicker, The drop down calendar still allows to select a date behond the maximum.

Closed Unassigned: Unable to commit changes [20113]

$
0
0
Hello,

I'm unable to commit changes that I've made.

I keep receiving a Commit Failed error. I've attached a screenshot of the error.

I'm using Visual Studio 2010 with VisualSVN.

Thank you
Comments: Public checkin are not allowed on the toolkit.

Created Issue: Review the PropertyGrid Documentation [20492]

$
0
0
The documentation page of the PropertyGrid need to be updated.
The custom Editor example still refer to the Obsolete "EditorDefinition" as an example.

Commented Issue: Review the PropertyGrid Documentation [20492]

$
0
0
The documentation page of the PropertyGrid need to be updated.
The custom Editor example still refer to the Obsolete "EditorDefinition" as an example.
Comments: ** Comment from web user: emartin **

URL:

https://wpftoolkit.codeplex.com/wikipage?title=PropertyGrid&referringTitle=Documentation#custom_editors_dataTempates


Commented Unassigned: PropertyGrid.EditorDefinitions Broken [20120]

$
0
0
Not sure how this hasn't been noticed, but EditorDefinitions no longer work in 2.0. To reproduce, take the following code and stick it in a project:

__MainWindow.xaml__:
```
<Window x:Class="PropertyGridTest.MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit"
xmlns:sys="clr-namespace:System;assembly=mscorlib"
Title="PropertyGrid Test">
<xctk:PropertyGrid x:Name="propertyGrid">
<xctk:PropertyGrid.EditorDefinitions>
<xctk:EditorDefinition TargetType="{x:Type sys:String}">
<xctk:EditorDefinition.EditorTemplate>
<DataTemplate>
<Border Background="Red">
<TextBlock>Here!</TextBlock>
</Border>
</DataTemplate>
</xctk:EditorDefinition.EditorTemplate>
</xctk:EditorDefinition>
</xctk:PropertyGrid.EditorDefinitions>
</xctk:PropertyGrid>
</Window>
```
__MainWindow.xaml.cs__:
```
using System.Windows;

namespace PropertyGridTest
{
public partial class MainWindow : Window
{
public MainWindow()
{
InitializeComponent();

this.propertyGrid.SelectedObject = new Data();
}
}

public class Data
{
public string Name
{
get;
set;
}

public int Age
{
get;
set;
}
}
}
```
Then install 1.9.0:
```
Install-Package Extended.Wpf.Toolkit -Version 1.9.0
```
Run this and you will see a red border for the name entry, as expected. Now do this:
```
Uninstall-Package Extended.Wpf.Toolkit
Install-Package Extended.Wpf.Toolkit -Version 2.0.0
```
Run this again and you won't see the custom editor.
Comments: ** Comment from web user: emartin **

Thanks for your comment, [this issue](https://wpftoolkit.codeplex.com/workitem/20492) has been created to update the documentaion.

Closed Unassigned: Remove Xceed.Wpf.AvalonDock [20153]

$
0
0
Hello,

Is there any way to remove the localization folders containing a single Xceed.Wpf.AvalonDock.resources.dll file when building a project?
Especially since I am not even using AvalonDock, it does not look very clean.

Thanks
Comments: Question answered.

Commented Unassigned: xceed.wpf.toolkit ColorPicker XAML loading error in windows server 2008 [20156]

$
0
0
Hi ,

I am using xceed.wpf.toolkit version 1.9.0 on a wpf project. it causes a xamlParseException when trying to load the colorPicker.

This is my xaml: <Viewbox Margin="3">
<Xceed:ColorPicker Name="BtFontColor" Width="30"
SelectedColorChanged="FontColorSelectedColorChanged"
ToolTip="Font Color" />
</Viewbox>

And the exception is : {"'Initialization of 'Xceed.Wpf.Toolkit.ColorPicker' threw an exception.' Line number '121' and line position '48'."}

The inner exception : {"Could not load file or assembly 'Xceed.Wpf.Toolkit.classic, Version=1.9.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4' or one of its dependencies. General Exception (Exception from HRESULT: 0x80131500)":"Xceed.Wpf.Toolkit.classic, Version=1.9.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4"}



When I remove that XAML portion everything works fine.

This problem seems to occur only on machines running Windows Server 2008 R2, I tried it on various other windows OS's and I dont get that error.

My dll is in the correct place and the path is referenced correctly.

Regards,

A
Comments: ** Comment from web user: emartin **

Is the ColorPicker the only toolkit control in your XAML tree ?

Commented Issue: Missing Assembly: Xceed.Wpf.Toolkit.Luna [19517]

$
0
0
I added Xceed Extended WPF Toolkit via Nuget and I get a "A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll" which when I looked into it, found that it was looking for Xceed.Wpf.Toolkit.Luna.

Everything seems to work without this assembly.
Comments: ** Comment from web user: emartin **

Another [issue here](https://wpftoolkit.codeplex.com/workitem/20156)

Closed Unassigned: xceed.wpf.toolkit ColorPicker XAML loading error in windows server 2008 [20156]

$
0
0
Hi ,

I am using xceed.wpf.toolkit version 1.9.0 on a wpf project. it causes a xamlParseException when trying to load the colorPicker.

This is my xaml: <Viewbox Margin="3">
<Xceed:ColorPicker Name="BtFontColor" Width="30"
SelectedColorChanged="FontColorSelectedColorChanged"
ToolTip="Font Color" />
</Viewbox>

And the exception is : {"'Initialization of 'Xceed.Wpf.Toolkit.ColorPicker' threw an exception.' Line number '121' and line position '48'."}

The inner exception : {"Could not load file or assembly 'Xceed.Wpf.Toolkit.classic, Version=1.9.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4' or one of its dependencies. General Exception (Exception from HRESULT: 0x80131500)":"Xceed.Wpf.Toolkit.classic, Version=1.9.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4"}



When I remove that XAML portion everything works fine.

This problem seems to occur only on machines running Windows Server 2008 R2, I tried it on various other windows OS's and I dont get that error.

My dll is in the correct place and the path is referenced correctly.

Regards,

A
Comments: Duplicate of 19517: http://wpftoolkit.codeplex.com/workitem/19517

New Post: WPF Toolkit Propertygrid - how to use a property collection

$
0
0
The Plus edition of the PropetyGrid support to provide properties as a "list" instead of having to provide a compile-time static definition.

New Post: DecimalUpDown FormatString


New Post: SplitButton drop down content and relative data binding

Created Unassigned: Button inside AvalonDock LayoutAnchorable focus problem [20496]

$
0
0
Buttons inside a LayoutAnchorable pane do not work if another Anchorable pane was active when the button is clicked. There seems to be some focus problem.

This is caused by the check for "!(focusedElement is ICommandSource)" in FocusElementManager.cs. The check causes buttons (and all other ICommandSources) not to be registered as the last focused element for the containing parent LayoutAnchorableControl. When a button is clicked and the buttons container LayoutAnchorableControl is not active, it is implictly activated by the DockingManager. The DockingManager eventually calls FocusElementManager.SetFocusOnLastElement from a deferred (BeginInvoke) handler. This causes the focus to be "stolen" away from the clicked button. If the click is "slow", the button's command does not get executed.

Removing the "!(focusedElement is ICommandSource)" condition from the if-clause fixes the problem, but I don't know if this introduces other issues. What's the point of excluding ICommandSources from the normal controller logic?

Created Unassigned: Cannot Load Assembly [20498]

$
0
0
I downloaded the ExtendedWPFToolkit. Unzipped it. Added the references to Exceed.Wpf.Toolkit.dll (and the other five dlls) to my WPF C# 2010 project. Adding the appropriate using statement.

Then I went to the Toolbox from the Designer view, added a new tab (WPF Extended) and then went to Add items. On the Choose Toolbox Dialog box, on the WPF tab, I pressed Browse, and went to the folder where I unzipped the DLLs. When I tried to add one I get a message that the Assembly which was downloaded from the web cannot be loaded, and was directed to this page:

http://msdn.microsoft.com/en-us/library/ee890038(VS.100).aspx

but under Properties there is no unblocking section meaning, according to that page, the assembly is not blocked.

Really all I wanted was an IntegerUpDown control, which, by the way, I don't find at all.

What am I doing wrong?

Thanks.

RON

Commented Unassigned: Button inside AvalonDock LayoutAnchorable focus problem [20496]

$
0
0
Buttons inside a LayoutAnchorable pane do not work if another Anchorable pane was active when the button is clicked. There seems to be some focus problem.

This is caused by the check for "!(focusedElement is ICommandSource)" in FocusElementManager.cs. The check causes buttons (and all other ICommandSources) not to be registered as the last focused element for the containing parent LayoutAnchorableControl. When a button is clicked and the buttons container LayoutAnchorableControl is not active, it is implictly activated by the DockingManager. The DockingManager eventually calls FocusElementManager.SetFocusOnLastElement from a deferred (BeginInvoke) handler. This causes the focus to be "stolen" away from the clicked button. If the click is "slow", the button's command does not get executed.

Removing the "!(focusedElement is ICommandSource)" condition from the if-clause fixes the problem, but I don't know if this introduces other issues. What's the point of excluding ICommandSources from the normal controller logic?
Comments: ** Comment from web user: BoucherS **

this is fixed in v2.1.

New Post: Property Grid with ComboBox

$
0
0
Hi,

1) Please do the following :
[ItemsSource( typeof( MyValuesItemsSource ) )]
    public string MyValues
    {
      get;
      set;
    }
<xctk:PropertyGrid x:Name="_propertyGrid"
                           Width="450"
                           Margin="10">
            <xctk:PropertyGrid.EditorDefinitions>
                <xctk:EditorTemplateDefinition TargetProperties="MyValues">
                    <xctk:EditorTemplateDefinition.EditingTemplate>
                        <DataTemplate>
                            <ComboBox SelectedItem="{Binding Value}"
                                               IsEditable="True" />
                        </DataTemplate>
                    </xctk:EditorTemplateDefinition.EditingTemplate>
                </xctk:EditorTemplateDefinition>
            </xctk:PropertyGrid.EditorDefinitions>
</xctk:PropertyGrid>
2) Please have a look at the sample "PropertyGrid/Editors/More EditorDefinitions" from the "Live Explorer app" available here : https://wpftoolkit.codeplex.com/.

This sample uses an EditorComboBoxDefinition to display a ComboBox of colors with an ItemsSource that can be a binding.

This is available in the "Plus" version of the toolkit, v2.0.
Viewing all 4964 articles
Browse latest View live


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