Multi-Select, doesn't call datafactory given a sequence of operations

Grids for WPF Forum

Posted 12 years ago by jeff jarrell
Version: 11.2.0560
Platform: .NET 4.0
Environment: Windows 7 (64-bit)

I have an issue with moving between .SelectedObject and .SelectedObjects and seeing the proper calls to the DataFactory.  I use a custom data factory.  

.SelectedObject = "ObjectA"  (updates propertyGrid, ok)

.SelectedObjects = "ObjectA,ObjectB" (updates propertyGrid, ok)

.SelectedObject = "ObjectA" (no call to DataFactory, propertyGrid still thinks its multiple selected, note same object that started sequence)

========== new sequence ====

.SelectedObject = "ObjectA"  (updates propertyGrid, ok)

.SelectedObjects = "ObjectA,ObjectB" (updates propertyGrid, ok)

.SelectedObject = "ObjectB" (works, updates propertyGrid, back to single selection)


In the first case, we've put in a call to set .SelectedObject=null prior to assignment of ObjectA, but it does cause an ugly flicker as the propertyGrid blanks out.

Thanks for any help.


Version 11.2.554.0

Comments (1)

Answer - Posted 12 years ago by Actipro Software Support - Cleveland, OH, USA

Hi Jeff,

Due to how SelectedObject returns the first object when multiple objects are specified in SelectedObjects, its change notification won't kick in for this scenario.  If you plan on using SelectedObjects, then it would be better to always use SelectedObjects only.  For single object selections, just pass an array of one object to it.

Actipro Software Support

The latest build of this product (v24.1.2) was released 28 days ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.