Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 243
  • Last Modified:

Interface / Pointer GUI Association

Hello All

I would like to know the best way to store an interface reference in an assocaited pointer.

For example, in a listbox containing cats, with each item representing an ICat reference, I would like to store the ICat reference in the Objects property of the list item. Another example is using a TTreeView (cats in a tree?) and the Node's Data property.

I have accomplished this in the past using records (one sole member of type ICat and using the record pointer), and also by bypassing reference counting by typecasting the interface to a void pointer. The first method is tedious, and the second one is dangerous.

Is there some elegant construct or alternate method out there that I do not know about? Sure, one can use TInterfaceList to maintain a list of references, but there is still no way of directly associating that reference with the Objects or Data properties, so this discussion is not further advanced by such an observation.

What do you do?

Regards,

Edo
0
Edo082297
Asked:
Edo082297
  • 4
  • 2
1 Solution
 
MadshiCommented:
You can do this:

var obj : TObject;
    cat : ICat;
begin
  ICat(obj) := cat;
  ICat(obj) := nil;

This will work perfectly, even with incrementing and decrementing the reference count. Of course you have to assign "nil" to all objects before freeing them, because otherwise the reference count is never decremented.

Regards, Madshi.
0
 
MadshiCommented:
The type of obj doesn't really matter, it just has to be a 4-byte type. You can also use integer/cardinal/pchar/pointer/whatEver instead of TObject.
0
 
Edo082297Author Commented:
Madshi,

Please re-read my question.

Wouldn't this be nice:

var
  ACat: ICat;
  ANode: TTreeNode;
begin
  ACat := CoCat.Create;
  ICat(ANode.Data) := ACat;
end;

Sorry, left side can't be assigned to.

Or:

AListBox.Items.AddObject(ACat.Name, IUnknown(ACat));

Of course, the compiler will swallow casting ACat to a void pointer, but that is dangerous!

We are back at square one.

Edo
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
MadshiCommented:
I thought this one would be possible:

var
  ACat: ICat;
  ANode: TTreeNode;
begin
  ACat := CoCat.Create;
  ICat(ANode.Data) := ACat;
end;

Okay, let's change it like this:

var
  ACat: ICat;
  APtr: pointer;
  ANode: TTreeNode;
begin
  ACat := CoCat.Create;
  ICat(APtr) := ACat;
  ICat(ANode.Data) := APtrt;
end;

To free it, do this:

  APtr := ANode.Data;
  ANode.Free;
  ICat(APtr) := nil;

Regards, Madshi.
0
 
Edo082297Author Commented:
ICat(ANode.Data) := APtr;

....left side cannot be assigned to

However, I can get the compiler to take the following:

ACat := CoCat.Create;

ICat(APtr) := ACat;
ANode.Data := APtr;

However, I'm not sure if ACat is reference counted properly in this last case; using the void pointer bothers me (should it?). I'll give you full points if you check that, or once I get around to checking it and see that it does indeed correctly increment the reference count on ACat (which could be in a couple of weeks at this point).

Thanks, Madshi

Edo
0
 
MadshiCommented:
Oooooops - ****!! Yes, you changed it exactly the way I meant it...   :-)

The reference count is incremented in the line "ICat(APtr) := ACat". So this solution has no flaws.

Regards, Madshi.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now