Annoyingly we need to have two separate projects in two separate directories,
since Framework WPF projects aren't supported in sdk-style csprojs. The
Framework and Core projects also stamp over each others' bin and obj
directories, even if you set IntermediateFilePath, hence the need to put
them in entirely separate places
CommandBinding isn't a DependencyObject, so we can't get its DataContext
or View.ActionTarget -- we can only use the
IRootObjectProvider.RootObject. This should be good enough for most cases,
as these tend to get installed at the root of a window.
Fixes#50
VS2015 now throws an error (it thinks Stylet.Start doesn't exist), and VS2017
deadlocks. Neither is a great outcome.
The best we can do is to ask the user to uninstall Stylet.Start
Fixes#32
We checked to see whether Top or Left were set, but not if they had a
DataBinding. This meant you couldn't explicitly set the location through
a binding.
Fixes#31
This is the encoding which VS uses, so let's be consistent. We were
previously saving as UTF-8 without a BOM, which VS seemed to be interpreting
as ASCII, and was throwing a wobbly if non-ASCII characters were later
added.
Fixes#30
As a result of being activated/deactivated/closed, a child of a conductor
might do something which results in the conductor changing its items
collection. Therefore make sure that this collection is copied before
calling into the children while iterating.
Fixes#13
This removes the MessageBoxOptions input to MessageBoxViewModel, and
replaces it with explicit FlowDirection and TextAlignment inputs.
I think this is fair enough - we weren't using most of the members
of MessageBoxOptions, so allowing them to be provided was misleading.
Fixes#12
This can be used to manually change the state of properties, without using
the IModelValidator stuff. This handles more niche use-cases which don't
fit the pattern established by the IModelValidator.
There's no nice way to make it work alongside CanCloseAsync when you're
in a conductor hierarchy. There will always be difference between how
CanClose and CanCloseAsync behave when there are children which need
to be interrogated as well, and that's confusing.
Antony Male
Felipe Martínez