[Lazarus] Object Inspector reuse ?

Michael Van Canneyt michael at freepascal.org
Thu Sep 8 10:45:13 CEST 2016



On Thu, 8 Sep 2016, Mattias Gaertner wrote:

>> > It uses the hint window.
>> > You can use this to show your own hints in your application. 
>> 
>> I suppose you know that the IDEHelpIntf contains a whole lot more than just that ?
>
> Yes. Although no initialization sections.

Luckily, but I don't want all this code in my binary :-)

>> >> IDEWindowIntf is also not really something I want in my end-user binary. 
>> >
>> > IDEWindowIntf? 
>> 
>> From PropEdits:
>>
>>    // Forms with .lfm files
>>    FrmSelectProps, StringsPropEditDlg, KeyValPropEditDlg, CollectionPropEditForm,
>>    FileFilterPropEditor, IDEWindowIntf;
>
> For one call:
>  SetPopupModeParentForPropertyEditor(CollectionForm);
> I'm not sure why this is needed.

If you don't know, I certainly do not know... :/

>
> 
>> From my point of view, none of these should appear in propedits.
>> Some are probably for Delphi compatibility.
>> 
>> I can see that an effort was made to make the OI independent of the IDE,
>> but it is either not sufficient, or it has been watered down over time. 
>
> The later.
>
>> In each case, it pulls in way more than I consider appropriate.
>> (from an IDE point of view, the tight integration makes sense, no discussion
>> there)
>> 
>> So it seems that either I take the whole shebang, or I must roll my own.
>
> Well, a TBaseObjectInspector could reduce the shebang.

When I start my implementation, I will consider it. 
The OI is quite powerful, it would be a shame not to be able to use it.

Michael.


More information about the Lazarus mailing list