| Age | Commit message (Collapse) | Author |
|---|
|
Fixes #525
When we moved to the new panel group system, the grouped editors weren't
accounted for and so when we try to remove their child property from the
container group it's not found since they're inside the group editor VM.
This also meant that even if removal had worked, we wouldn't properly
add new shared view model types to the group.
|
|
PR526 introduced a crash in named arrange mode and exposed a hole in our tests. All tests pass, but no properties are shown in either mode.
|
|
Fixes #525
When we moved to the new panel group system, the grouped editors weren't
accounted for and so when we try to remove their child property from the
container group it's not found since they're inside the group editor VM.
This also meant that even if removal had worked, we wouldn't properly
add new shared view model types to the group.
|
|
|
|
|
|
|
|
|
|
This should ensure that exceptions thrown inside async void
methods do get rethrown as part of the Teardown of a given test.
This removes the eventhandlers on AppDomain.UnhandledException
and also removes the second SyncContext implementation which
did not capture/propagate the exceptions.
|
|
|
|
|
|
This moves away from a straight name on the IObjectEditor to a ITypeInfo
describing the type. As this is currently expect to be non-null, it was
added to the tests (as well as some missing .Target assignments).
Caught up in this change were some tests being moved down a rank from
PanelViewModelTests to PropertiesViewModelTests.
|
|
Fixes #296
|
|
|
|
|
|
|
|
Fixes #213
|
|
|
|
- Fixes an ordering issue for a grouped category when null categories
are present.
- Fixes a crash when null categories are present.
|
|
|
|
There's certain feature support levels that are better defined at a
target platform level than on individual properties. In addition to this
there are some needs to configure certain presentations on a
per-platform basis. TargetPlatform will serve these needs.
|
|
Functionality largely hasn't changed but with group editors the
panel-wide VMs need to be thinking about children in terms of editors
and not individual properties. This is largely only manifest in the
group editor.
|
|
|
|
|
|
|
|
|
|
changes.
|
|
|
|
In the rare case that selected objects change before object editors can
be retrieved for them, we need to ensure that we're finished with prior
changes first as we're dealing with NotifyCollectionChangedEventArgs.
|
|
|
|
This scenario was unlikely to ever arise, but reducing duplicated code
is always a positive.
|
|
Since some objects we'll be editing may come from custom classes, we
will need to be able to update their list of properties as the custom
class gets edited. Now we listen for collection changes on the property
list itself from the object editor.
|
|
Since IObjectEditors were not equatable, we were adding duplicate
editors every time the selected items list changed. Instead of
implementing equality on object editors (which we may still do for other
reasons) we'll request editors one at a time. This messes with the
current distinction between ObjectViewModel and PanelViewModel, but it's
largely pointless. This way we avoid recreating editors (which might be
expensive) altogether.
We also add a .Target property to the object for identity. This avoids
having to build a map between selected objects to their editors. The
selected items list itself should never be terribly long, so doing a
linear comparison is no big deal.
|
|
|
|
|
