HOWTO: XTPPropertyGridItem with drop down tree

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

   Hi;

In our most recent project I need a property grid item with dropdown tree support.
Has anyone ever done this? Whats the (best) design to realize this. 
I prefer to use the CXTPPropertyGridItemConstraints* collection to hold the tree items data, due to minimize the break of the existing grid item design.

Any help is appreciated

Martin

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
mgampi Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 14 July 2003 Status: Offline Points: 1201	Post Options Post Reply Quote mgampi Report Post Thanks(0) Quote Reply Topic: HOWTO: XTPPropertyGridItem with drop down tree Posted: 20 November 2006 at 7:58am
	Hi; In our most recent project I need a property grid item with dropdown tree support. Has anyone ever done this? Whats the (best) design to realize this. I prefer to use the CXTPPropertyGridItemConstraints* collection to hold the tree items data, due to minimize the break of the existing grid item design. Any help is appreciated Martin

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 20 November 2006 at 9:19am
	Hi, The best design is to create new class derived from CXTPPropertyGridItem, override its OnInplaceButtonDown and show your tree.
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS

mgampi Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 14 July 2003 Status: Offline Points: 1201	Post Options Post Reply Quote mgampi Report Post Thanks(0) Quote Reply Posted: 20 November 2006 at 9:46am
	Hi Oleg; I have done this already but I'm having troubles in using the control as if it's an item with a simple list where the constraints container determines the tree nodes. I looked into the internal grid item / constraints design and found out, that its not possible to create my own XTPPropertyGridItemConstraints derived collection, since the m_arrConstraints member is private and no protected or public function exists to insert my own constraint into this list. All I wanted to do is to provide a somehow standard interface to reusable property tree items like shown in this "pseudo" code sequence: pItem=grid.AddChildItem(new CMyPropertyGridItemTree(...)) pConstraints=pItem->GetConstraints() pConstraints.AddConstraint("Item text", new MyItemConstraintData(...)); I need this additional constraint item data to provide such informations as 'parent', 'internal key', ... My problem is, that I can't find a - only coded once - solution to delete my constraint item data on shutdown. In my opinion, the right place to do this is in the dtor of the CXTPPropertyGridItemConstraints() class, which I have to override because I use the m_dwData member to store the additional MyItemConstraintData pointer. And now the hidden m_ArrConstraints member comes in once again... I know, that I could change the source of you library, but thats an maintenance issue, and therefore not allowed in our company. Martin

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 20 November 2006 at 10:40am
	Hi, why so difficult... why you can't just add this Tree as member and use pItem->GetTreeCtrl() method to retrieve tree and add nodes.
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS

mgampi Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 14 July 2003 Status: Offline Points: 1201	Post Options Post Reply Quote mgampi Report Post Thanks(0) Quote Reply Posted: 20 November 2006 at 1:28pm
	Hello Oleg; you're absolutely right. First I did it the wrong way. I tried to find a somehow 'universal' solution that encapsulates the detail of the tree portion. On the other hand I wanted to minimize the amount of source code needed to implement tree items with different content. Martin

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 20 November 2006 at 1:56pm
	:)
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS