New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run MahApps 1.5.0 Caliburn Demos on VS2015 #2953

Closed
oschwab opened this Issue May 3, 2017 · 17 comments

Comments

Projects
None yet
6 participants
@oschwab

oschwab commented May 3, 2017

Hello,

I can't run Caliburn demo projects (4.0 and 4.5) from my VS2015 workstation.
Both fails on AppBootstrapper GetInstance method , finding no contract for settings

image

Environment

  • MahApps.Metro 1.5.0
  • Windows 10
  • Visual Studio 2015
  • .NET Framework 4.0 && 4.5
@punker76

This comment has been minimized.

Member

punker76 commented May 3, 2017

@oschwab Saw this too after 1.5.0 release, but I'm not a good Caliburn user

@oschwab

This comment has been minimized.

oschwab commented May 3, 2017

@punker76 I had an issue on my own project with flyouts after mahapps update ; as I used Caliburn sample as a basis, I tried to see how it was done in it, and boom !

@Eternal21

This comment has been minimized.

Eternal21 commented May 4, 2017

Looks like caliburn can't locate views for the flyout viewmodels. I got the project to run by commenting out all fly-outs inside OnInitialize() function. Kind of defeats the purpose, since fly-outs are all there is to the demo. I will look into actually fixing the problem when I get some spare time.

image

@oschwab

This comment has been minimized.

oschwab commented May 5, 2017

I think it might be linked to this change :

Change Flyout from ContentControl to HeaderedContentControl which has the correct properties for headers.

2874108

@Eternal21

This comment has been minimized.

Eternal21 commented May 5, 2017

There's a related stackoverflow question, with no answers so far: http://stackoverflow.com/questions/43735278/wpf-mahapps-metro-caliburn-micro-flyout-headeredcontentcontrol

I've gotten the flyouts to work by commenting out 'this.Header = "' inside each Flyout constructor:

image

Obviously, that still doesn't help with locating and binding to their views, as you just end up with this:

image

@oschwab

This comment has been minimized.

oschwab commented May 5, 2017

@Eternal21 We're both exactly at the same point ...

@oschwab

This comment has been minimized.

oschwab commented May 5, 2017

@Eternal21 @punker76 Commenting the Binding to Header in ShellView.xaml makes the demo work again
image

@Eternal21

This comment has been minimized.

Eternal21 commented May 5, 2017

Yes it does. The only problem now is, it displays the path to viewmodel now instead of the header title:

image

@seb30

This comment has been minimized.

seb30 commented May 8, 2017

There's a related stackoverflow question, with no answers so far

Hey guys, it's me.

@seb30

This comment has been minimized.

seb30 commented May 8, 2017

unbenannt

This works, but only if 1 Flyout is opened. If you're going to open another one, only the Header of the old one will be visible.

@punker76

This comment has been minimized.

Member

punker76 commented May 9, 2017

It seems it is a generally problem of Caliburn and HeaderedContentControl and/or the sample must be rewritten to work correctly.

@jamithiran

This comment has been minimized.

jamithiran commented Jun 10, 2017

@seb30 , your suggestion (setting the content) finally brought the agony of many hours to an end but as you mentioned the second one has problems. It shows only the header.

The one that shows the content is usually the first flyout added in viewmodel. I'm referring to my development project in VS2017. Did you have any success in resolving this situation? I chose to use CM only because I could not open/close flyout from viewmodel.

Thanks

@seb30

This comment has been minimized.

seb30 commented Jun 12, 2017

Not really. In the end I'm showing only one Flyout and the other stuff in a dialog.

@jamithiran

This comment has been minimized.

jamithiran commented Jun 12, 2017

@seb30 Thank you for the reply. I have dropped the idea of using CM and going the normal way. Just to clarify to others on previous message, only the last added flyout shows the content and previous flyouts (1 or more) ones the header.
Cheers

@nigel-sampson

This comment has been minimized.

nigel-sampson commented Jun 15, 2017

I've dropped a work around in Caliburn-Micro/Caliburn.Micro#451 for the sample along with an explanation of what's happening.

Short story is that it appears that the ItemTemplate on the FlyoutsControl ends up as the HeaderTemplate of the Flyout. My gut says this part isn't related to Caliburn.Micro, but I need to spike a sample to test that out.

@jamithiran

This comment has been minimized.

jamithiran commented Jun 15, 2017

@nigel-sampson Thanks Nigel. Your workout seems to fix it. Cheers

@nigel-sampson

This comment has been minimized.

nigel-sampson commented Jun 15, 2017

So I was able to recreate the problem outside of Caliburn.Micro with the following.

<ma:MetroWindow.Resources>
    <Style x:Key="CustomFlyoutStyle"
       BasedOn="{StaticResource {x:Type ma:Flyout}}"
       TargetType="{x:Type ma:Flyout}">
        <Setter Property="Header" Value="{Binding Title}" />
    </Style>
</ma:MetroWindow.Resources>

<ma:MetroWindow.Flyouts>
    <ma:FlyoutsControl x:Name="MyFlyouts" ItemContainerStyle="{StaticResource CustomFlyoutStyle}">
        <ma:FlyoutsControl.ItemTemplate>
            <DataTemplate>
                <StackPanel Orientation="Horizontal">
                    <TextBlock Text="Item Template" />
                    <TextBlock Text="{Binding}" />
                </StackPanel>
            </DataTemplate>
        </ma:FlyoutsControl.ItemTemplate>
    </ma:FlyoutsControl>
</ma:MetroWindow.Flyouts>

<StackPanel>
    <Button x:Name="OpenFlyout" Content="Open" />
</StackPanel>
public class FlyoutViewModel
{
	public FlyoutViewModel(string title, string content)
	{
		Title = title;
		Content = content;
	}

	public string Title { get; }
	public string Content { get; }
}

public partial class MainWindow
{
	public MainWindow()
	{
		InitializeComponent();

		Loaded += (s, e) =>
		{
			MyFlyouts.ItemsSource = Enumerable.Range(0, 10).Select(i => new FlyoutViewModel($"Title {i}", "Content for the flyout"));
		};

		OpenFlyout.Click += (s, e) =>
		{
			var flyout = MyFlyouts.ItemContainerGenerator.ContainerFromIndex(0) as Flyout;

			if (flyout == null)
				return;

			flyout.IsOpen = !flyout.IsOpen;
		};
	}
}

Which results in the following:

flyout

As you an see the ItemTemplate of the FlyoutsControl is being applied to the HeaderTemplate of the child Flyouts. Can't see anything immediately obvious in the code about why this is though.

@punker76 punker76 self-assigned this Jan 28, 2018

@punker76 punker76 added this to the 1.6.0 milestone Jan 28, 2018

punker76 added a commit that referenced this issue Jan 28, 2018

(GH-2953) Can't run MahApps 1.5.0 Caliburn Demos on VS2015
- The `PrepareContainerForItemOverride` overrides the header properties with the `ItemTemplate`, `ItemTemplateSelector` and `ItemStringFormat` values. But in our case we want keep this values and want use the item template stuff for the content of the Flyout.

K3UL added a commit to K3UL/MahApps.Metro that referenced this issue Sep 21, 2018

Updating codebase from official repo (#1)
* Move MetroDialogColorScheme and MetroDialogSettings to it's own files
  Update some xml comments

* Move classes in it's own files

* Update .DotSettings

* Add MetroDialogAutomationPeer

* Remove unnecessary using

* Add Canceled to MessageDialogResult
  Closes MahApps#2467

* Set a selected Item only if there is no content set

* Add `HamburgerMenu` resources to Control styles to allow style manipulation and fix binding expression infos

* Add FlyoutAutomationPeer for better CodedUI support

* Use DialogTitleFontSize and DialogMessageFontSize via DynamicResource at the base MetroDialog style

* Template binding
- to horizontal and vertical alignment
- to all content properties (inner content)
- to SnapsToDevicePixels

* Add AutomationProperties names
Template binding to Padding

* New (readonly) `IsAnyDialogVisible` dependency property
  This property will be updated if a dialog is shown or not

* - Remove internal close command and use the CloseTabItemAction
- Clear style and template for TabItem to prevent nasty binding expression errors
- Allow TabControlHelper dependency properties for TabItem too (brushes and Underlined property)

* TabControlHelper.Underlined makes only sense for TabControl

* Rename: IsAnyDialogVisible -> IsAnyDialogOpen

* - Pass correct dialogs settings to HandleOverlayOnShow
- New `CanCloseDialogOwner` property at `MetroDialogSettings` which can be used to handle how the owner of the dialog can be closed.
- New `IsCloseButtonEnabledWithDialog` property at `MetroWindow` which indicates if the close button should be enabled or not if a dialog is shown.

* - CanCloseDialogOwner -> `OwnerCanCloseWithDialog`
- Add trigger for `IsCloseButtonEnabledWithDialog` at WindowButtonCommands for PART_Close button
- `HandleOverlayOnHide` sets the `IsCloseButtonEnabledWithDialogPropertyKey` and restores focus if needed
- `HandleOverlayOnShow` sets the `IsCloseButtonEnabledWithDialogPropertyKey`

* Need Unwrap at HandleOverlayOnShow

* Fixed issue MahApps#3155 "GridViewColumnHeader uses twice the padding"!

* Closing main demo was wrong (TaskCanceledException)

* Update readme.md

* Set HorizontalScrollBarVisibility and VerticalScrollBarVisibility for HotKeyBox and NumericUpdDown to Hidden, cause the inner TextBox has this as default too

* Add a new property to handle the allowed numeric input:

- Add new `NumericInputMode` property with the new flag enumeration NumericInput (default is NumericInput.All)
- Mark `HasDecimals` as obsolete

* block scientific input if only numbers allowed

* MetroThumbContentControl: Catch exception and trace it

* Fix not focusing custom controls via FocusManager
  Problem: NumericUpDown, HotKeyBox and TimerPickerBase doesn't focus for the first time when the FocusManager will be used.

* HamburgerMenu: correct PanePlacement handling for right aligned
Update first showcase to change PanePlacement on the fly

* MetroWindow: New OverlayFadeIn and OverlayFadeOut properties to set the overlay fade in/out Storyboards

* Fix the fade in and out animation if no duration exists

* Slider: remove linear gradient brush from horizontal and vertical track value style
RangeSlider: fix margin of the middle thumb

* Add new Win10 Slider style
  - Style: `MahApps.Metro.Styles.Slider.Win10`
  - Control template: `MahApps.Metro.Styles.Slider.HorizontalTemplate.Win10`, `MahApps.Metro.Styles.Slider.VerticalTemplate.Win10`
  - RepeatButton: `MahApps.Metro.Styles.Slider.HorizontalTrack.Win10`, `MahApps.Metro.Styles.Slider.VerticalTrack.Win10`
  - Thumb: `MahApps.Metro.Styles.Slider.Thumb.Win10`

* Add new Slider style and mark old as obsolete
  - Style: `MahApps.Metro.Styles.Slider`
  - Control template: `MahApps.Metro.Styles.Slider.HorizontalTemplate`, `MahApps.Metro.Styles.Slider.VerticalTemplate`
  - RepeatButton: `MahApps.Metro.Styles.Slider.HorizontalTrack`, `MahApps.Metro.Styles.Slider.VerticalTrack`
  - Thumb: `MahApps.Metro.Styles.Slider.Thumb`
  - Brushes:
`MahApps.Metro.Brushes.SliderThumbBackground` default `Gray2`
`MahApps.Metro.Brushes.SliderTrackFill` default `Gray3`
`MahApps.Metro.Brushes.SliderTrackValueFill` default `AccentColor`

`MahApps.Metro.Brushes.SliderThumbBackgroundMouseOver` default `Gray5`
`MahApps.Metro.Brushes.SliderTrackFillMouseOver` default `Gray3`
`MahApps.Metro.Brushes.SliderTrackValueFillMouseOver` default `AccentColor`

`MahApps.Metro.Brushes.SliderThumbBackgroundPressed` default `Gray2`
`MahApps.Metro.Brushes.SliderTrackFillPressed` default `Gray3`
`MahApps.Metro.Brushes.SliderTrackValueFillPressed` default `AccentColor`

`MahApps.Metro.Brushes.SliderThumbBackgroundDisabled` default `Gray6`
`MahApps.Metro.Brushes.SliderTrackFillDisabled` default `Gray6`
`MahApps.Metro.Brushes.SliderTrackValueFillDisabled` default `Gray6`

* Remove DataTrigger from MahApps.Metro.Styles.Slider.Thumb

* Add new attached properties to SliderHelper for the Brushes

* Add `MahApps.Metro.Styles.RangeSlider` key
Use `SliderHelper` brush properties also for RangeSlider

* - Thump style for the middle part: `MahApps.Metro.Styles.RangeSlider.HorizontalMiddleThumb`, `MahApps.Metro.Styles.RangeSlider.VerticalMiddleThumb`
- Use `MetroThumb` instead `Thumb`
- Set ReservedSpace for all TickBar controls instead Margin

* New Win10 style for RangeSlider `MahApps.Metro.Styles.RangeSlider.Win10`

* Add FlatSlider resource dictionary to Controls resource dictionary

* DatePicker: add new dependency property `ControlsHelper.IsReadOnly`. This property sets the IsReadOnly property on the inner TextBox and the IsEnabled on the inner popup button.

* NumericUpdOwn:
- Validate and convert new value on lost focus only if the text was manually changed
- Fix interaction between `IsReadOnly` and `InterceptManualEnter`

* MetroWindow: use BorderThickness as Margin for inner window content

* Implements ToolTip on HamburgerMenuItem

* Updates HamburgerMenuItem ToolTip DependencyProperty to typeof(object)

* return (string)GetValue(ToolTipProperty); => return GetValue(ToolTipProperty);

* Add ability to set progress dialog progress bar brush color

* (MahAppsGH-3175) MetroWindow: improve BorderThickness usage

* (MahAppsGH-3175) MetroWindow: forgot the ShotTitleBar trigger to update the Grid rows for the overlays

* GetAncestors method added to TreeHelper.

Added one method to TreeHepler.
In every place where visual tree Ancestors are needed TreeHelper is used.

* MetroProgressBar:
- New style key `MahApps.Metro.Styles.MetroProgressBar`
- Fix layout rounding for both orientations
ProgressBar:
- Change style key to `MahApps.Metro.Styles.ProgressBar` and mark `MetroProgressBar` as obsolete
- Fix layout rounding for vertical orientation

* (MahAppsGH-2953) Can't run MahApps 1.5.0 Caliburn Demos on VS2015
- The `PrepareContainerForItemOverride` overrides the header properties with the `ItemTemplate`, `ItemTemplateSelector` and `ItemStringFormat` values. But in our case we want keep this values and want use the item template stuff for the content of the Flyout.

* SliderHelper: if the PreviewMouseWheel is used then it should also marked as handled, otherwise the event is bubbled to the next control

* Slider: a slider should be reached by tab, so set the IsTabStop property to true

* FlatSlider: fix the height and width of the Slider if the TickBars are visible

* Start reorganize the Sliders and Progress examples (not yet finished)

* FlatSlider: Add new style and mark old styles as obsolete
- Style: `MahApps.Metro.Styles.FlatSlider`
- Templates: `MahApps.Metro.Styles.FlatSlider.HorizontalTemplate`, `MahApps.Metro.Styles.FlatSlider.VerticalTemplate`
- TickBar style: `MahApps.Metro.Styles.FlatSlider.TickBar`
- Thumb style: `MahApps.Metro.Styles.FlatSlider.Thumb`
- Track style: `MahApps.Metro.Styles.FlatSlider.Track`

* RangeSlider: Add `Ticks` property MahApps#2879

* SliderHelper:
- Allow `SliderHelper.EnableMouseWheel` and `SliderHelper.ChangeValueBy` for `RangeSlider` too

* Selection properties for RangeSlider

* RangeSlider Win10: minor changes to pressed triggers for left and right edge

* Finished MahApps#3181
ProgressRing: Fix broken binding after set the IsActive property (must use SetCurrentValue)
ProgressBar: Set MinWidth and MinHeight for default style `MahApps.Metro.Styles.ProgressBar`

* typo

* (MahAppsGH-3039) NumericUpDown
- Fix not correct coerced value if min or max value was reached
- Fix manual change indication (e.g Tab is a non indicator)

* (MahAppsGH-1678) Fix Background for PivotItem in dark theme

Closes MahApps#1678

* appveyor: use GitVersion_NuGetVersion, zip Caliburn sample

* Update pakte and dependencies (Fody 2.3.25)

* Add WpfAnalyzers

* WPF0072: ValueConversion must use correct types.

* WPF0001: Backing field for a DependencyProperty should match registered name.

* WPF0004: CLR method for a DependencyProperty must match registered name.

* warning disable 618
CS0219
CS1573

* WPF0081: MarkupExtensionReturnType must use correct return type.

* WPF0011: Containing type should be used as registered owner.

* WPF0006: Name of CoerceValueCallback should match registered name.
WPF0007: Name of ValidateValueCallback should match registered name.

* WPF0043: Don't set DataContext using SetCurrentValue.

* WPF0016: Default value is shared reference type.
Suppress WPF0036: Avoid side effects in CLR accessors.

* WPF0005: Name of PropertyChangedCallback should match registered name.

* Add new CommandTriggerAction

* Add new CloseFlyoutAction and mark the internal command as obsolete

* WPF0041: Set mutable dependency properties using SetCurrentValue.

* WPF0050: XmlnsPrefix must map to the same url as XmlnsDefinition.
- use `mah` as XmlnsPrefix

* (MahAppsGH-3013) Fix ListView (ListBox) - Undeletable Top Padding
- Collapse `GridViewHeaderRowPresenter` if the TemplatedParent.View.Columns are null
Closes MahApps#3013

* build with cake

* yes, we have a build_script...

* Prepare build for GitReleaseManager

* Update 1.6.0.md

* Use GitVersion.CommandLine 4.0.0-beta0012

* Fix calculating CommitsSinceVersionSource

* Remove release docs from repo (moved to wiki)

* Fix release NuGet pack version

* appveyor: Tag.IsTag

* ComboBox: Remove unnecessary FocusBorder

* Readme: add tool logos, minor text changes

* Update ColorExample

* Readme: update screenshots

* typo

* GitVersion: Minor inc

* Fix NuGet release version

* Fixing branch name for appveyor badges

Branch name was "dev" where it should be "develop".

* (MahAppsGH-3202) Fix NU1602 Build Warning in 1.6.0

* Use VS2017 new project file and multi targeting (net40 - net47).

Change the main class library first (and remove the old ones).

* Minor changes in new csproj file
Update cake script

* Restoring NuGet project.assets.json via MSBuild

* Correct usage of MSBuild.Sdk.Extras

* try to convert MahApps.Metro.Demo

* try the latest tipps, but still not working with latest VS 15.6.3/15.6.4

* only workable with:

MSBuildSdkExtras 1.2.2
Paket 5.153.0
VS 2017 15.6.4
R# 2017.3.5
Self fixed project name vs assembly name

* Handle multiple App.config

* Add Directory.build.*

* TargetFrameworks should be also be added to csproj files

* Move projects directly under solution

* convert MahApps.Metro.Caliburn.Demo

* use MSBuild.Sdk.Extras 1.3.0

* convert MahApps.Metro.Tests

* Update Tests AssemblyInfo, set GlobalSuppressions

* use TargetFramework net40 for now until I know what's going wrong with higher frameworks

* typo: TargetFramework -> TargetFrameworks

* update paket

* (MahAppsGH-3192) Fix setting ShowTitleBar

* (MahAppsGH-3212) Fix Background hit testing for inactive ProgressRing

* (MahAppsGH-3227) ThemeManager: overloaded ctors and methods to allow add accent and theme with resource dictionaries instead URIs

* Use xUnit v2

* net47 and net46 not working for now

* (MahAppsGH-3227) ThemeManager: enable dynamic accents (and themes) to change on the fly

* Fix for Track's height inside Slider.

* (MahAppsGH-3238) fix FlatSlider height usage (works now together with vertical and horizontal content alignement)

* (MahAppsGH-3238) fix Slider and RangeSlider height usage too (works now together with vertical and horizontal content alignement)

* (MahAppsGH-3244) Left-/ RightWindowCommands no more visible when ShowTitleBar is False
  This feature will be there, but the window commands can now be used again to bring these back

* docs: added backers and sponsors from Open Collective

* set new major version to 2.0

* fix the backers avatars

* Remove obsolete marked code like properties and classes (part 1)

* Remove obsolete TestTitleCapsProperty

* Remove obsolete marked code like properties and classes (part 2)

* (MahAppsGH-3248) fix thumb in FlatSlider

(cherry picked from commit e864ee8)

* fix next version

* (MahAppsGH-2289) Rename TitlebarHeight to TitleBarHeight

* Update issue templates

* Fix binding warnings after removing obsolete marked code

* Update issue templates

* Delete ISSUE_TEMPLATE.md

* Update PULL_REQUEST_TEMPLATE.md

* Update PULL_REQUEST_TEMPLATE.md

* (MahAppsGH-2763) DateTime instead TimeSpan for DateTimePicker/TimePicker (from @xxMUROxx)

* Fix IsClockVisible is not hiding the clock selectors (hout, min, sec)

* try to fix hanging tests (ApplicationFixture)

* update paket and dependencies (xunit runner prerelease)

* only .net 4.5 tests

* Removed the handling for non-digits within the textbox and allowed the user to specify the parsing number style.

* MSBuild.Sdk.Extras with global.json

* fix parsing input for numeric / hexadecimal and decimal values

* add tests for NumericUpDown

* (MahAppsGH-3189) Fix NumericUpDown Input Issues with StringFormat and parsing numbers

* (MahAppsGH-3272) Fix Wrong FileVersion and AssemblyVersion for v1.6.4

* (MahAppsGH-3280) Fix NumericUpDown doesn't handle percentages correctly

* update paket and to latest cake (inc. Cake.Paket)

* First step for generated themes

* Adjusting ThemeManager and everything else, except tests

* Fixing possible null-ref exception

* Restoring most ThemeManager tests

* Restoring all tests

* Renaming AccentHelper to ThemeHelper

* Switching to reference to XamlColorSchemeGenerator

* Fix HamburgerMenu IsEnabled false by default
The problem occurred when setting the property 'IsEnabled' to true, the
item became disabled. The problem was the CanExecute property should be true if
the Command is null (as specified in UpdateCanExecute()), but at the
initialization of the control, the local variable canExecute has the
default value false even if the Command is null. That leads to the
IsEnabledCoerceValueCallback returning false by default, so if the
IsEnabled property is set to any value (so the callback is triggered), it defaults to false.

* disable Fody in debug mode

* update paket and dependencies

* (MahAppsGH-3313) Fix for VS 15.8.1 update causes "Package is not compatible"

Closes MahApps#3313

* update editorconfig

* (MahAppsGH-3313) use temporary PackageReference instead Paket to allow VS 2017 build

* Remove NET40 and NET4 directives

* (MahAppsGH-3308) Fix TabItem HeaderFontSize change leads to freeze

* (MahAppsGH-3308) Use new extension method ExecuteWhenLoaded

* Update build cake script

* (MahAppsGH-3307) Change ListView default border thickness to zero

* (MahAppsGH-3265) Fix MetroDialogSettings is not settable within a style

* (MahAppsGH-3275) Fix TransitioningContentControl vs. ContentControl
  Changing ContentTemplate via triggers has no effect, cause the template was only set in code behind.

* no artifacts on PRs

* (MahAppsGH-3323) Fix CloseTabItemAction works only with MetroTabControl

* Use Win10 slider style at HamburgerMenu samples

* (MahAppsGH-3284) Fix Gap between menu items and hamburger icon

- add 2 new properties `PaneMargin` and `PaneHeaderMargin` to set the margin for Pane and PaneHeader (default is `0 0 0 8` for both properties)

* Rename `HamburgerMenuTemplate` to `HamburgerMenuButtonTemplate`

* (MahAppsGH-3239) Fix Customising HamburgerMenu

- rename `HamburgerMenuButtonTemplate` to `HamburgerButtonTemplate`
- add new property `HamburgerButtonStyle`

* Add appveyor nuget link to readme

* TabItem attached properties `HeaderFontSize`, `HeaderFontStretch` and `HeaderFontWeight` can now be set on the TabControl

* add a new attached property `HeaderFontFamily`

* (MahAppsGH-3329) Fix Windows 10 Maximize icon is slightly broken on high res displays

Closes MahApps#3329

* XamlStyler again

* Update readme.md

* (MahAppsGH-3332) Fix TransitioningContentControl defines a CornerRadius of 2 inside style

Use ControlsHelper.CornerRadius attached property for the inner border.

Closes MahApps#3332

* (MahAppsGH-3333) Fix TimePicker

- use SetCurrentValue to set new value for SelectedDateTime property to prevent broken bindings

Closes MahApps#3333

* Update paket

* Update paket dependencies and use ControlzEx v4.0 prerelease

* Use GlowWindowBehavior from ConrolzEx and remove old one

* ControlzEx v4.0.0-alpha0167

* ControlzEx v4.0.0-alpha0170

* Add TryToBeFlickerFree and KeepBorderOnMaximize to MetroWindow and set binding to properties of WindowChromeBehavior
Set TryToBeFlickerFree to true as default

* ControlzEx v4.0.0-alpha0171 (removed unused GlowBrushProperty)

* Remove old accent resource dictionaries

* Adjust version for ControlzEx NuGet dependency
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment