m_nTopIndex in CXTPPropertyGridUpdateContext

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi, currently the algorithm in CXTPPropertyGrid::BeginUpdate/EndUpdate and SaveExpandingState for storing/restoring the scroll position/top index of the property grid works by storing the ID of the top-most item. However in many cases this item may not have a ID (e.g. child items of PropertyGridItemFlags, etc.) so in this case the scroll position is reset to 0.

I think you should add a flag that the top-index is stored/restored "raw", i.e. just using PropertyGrid->GetTopIndex/SetTopIndex. I really don't like to modify the toolkit library sources. BeginUpdate/EndUpdate is not even virtual.....

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Barto Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 27 February 2005 Location: Germany Status: Offline Points: 60	Post Options Post Reply Quote Barto Report Post Thanks(0) Quote Reply Topic: m_nTopIndex in CXTPPropertyGridUpdateContext Posted: 01 February 2008 at 9:36am
	Hi, currently the algorithm in CXTPPropertyGrid::BeginUpdate/EndUpdate and SaveExpandingState for storing/restoring the scroll position/top index of the property grid works by storing the ID of the top-most item. However in many cases this item may not have a ID (e.g. child items of PropertyGridItemFlags, etc.) so in this case the scroll position is reset to 0. I think you should add a flag that the top-index is stored/restored "raw", i.e. just using PropertyGrid->GetTopIndex/SetTopIndex. I really don't like to modify the toolkit library sources. BeginUpdate/EndUpdate is not even virtual.....