Well, I figured out how to add the images when I add strings to the autocomplete:
alist.AddObject('PROCEDURE blabla',tobject(ttProc));
If I don't use my own imagelist this works, however, if I use my own imagelist it first writes the built in images, then the user defined ones over them, so you end up with two overlayed images in the list. I seem to remember I reported this as a bug years ago, but it's been so long I might be missing something.
Ideas?
If the examples only showed how to do this I could have saved a bunch of time digging through the code to figure this out.
Ok, thiis is really looks like a bug.
TAutoCompletionListBox.Create it's loading the images from the resource file:
{$IFNDEF TMSDOTNET}
FBmpVar.LoadFromResourceName(HInstance, 'TMS_VAR');
FBmpProp.LoadFromResourceName(HInstance, 'TMS_PROP');
FBmpEvent.LoadFromResourceName(HInstance, 'TMS_EVENT');
FBmpProc.LoadFromResourceName(HInstance, 'TMS_PROC');
FBmpMethod.LoadFromResourceName(HInstance, 'TMS_METHOD');
{$ENDIF}
If I comment this section out,it does not do the overlayed images. This same code is used again in the
TAutoCompletionListBox.SetImages if the imagelist is not assigned.
It works as it should with that block commented out from the create event, if the user defined image list is not set it uses the ones in the resource file and if the user defined one is set it uses those.
Can anyone from TMS comment on this and get it fixed in the production code?
The problem was solved. An incremental source update for this issue was sent.