> On Jul 2, 2020, at 4:04 PM, Mattias Gaertner via fpc-pascal
> wrote:
>
> Maybe something like this:
>
> List:=CodeToolBoss.IdentifierList;
> for i:=0 to List.GetFilteredCountCnt-1 do
> begin
> Item:=List.FilteredItems[i];
> if (Item.Tool<>nil) then begin
>if
>RightStr(Item.Tool.Ma
On Thu, 2 Jul 2020 12:55:24 +0700
Ryan Joseph via fpc-pascal wrote:
>[...]What would be more helpful is knowing which identifiers are
> from those large units and opting out of additional processing. Is
> that something which can be quickly known?
Maybe something like this:
List:=CodeToolBoss.I
> On Jul 2, 2020, at 8:05 AM, Ryan Joseph wrote:
>
> The majority of the work takes place in GatherIdentifiers. This is because
> MacOSAll and CocoaAll units. They're just massive files so I'm not sure what
> we can do about them.
I think I was wrong about this being the root of the problem
> On Jul 2, 2020, at 2:04 AM, Mattias Gaertner via fpc-pascal
> wrote:
>
>> One option would be return
>> results in partial batches (Language Server Protocol) supports this
>> but again I'm not sure if CodeTools supports this or not.
>
> Codetools provide a list of identifiers. Since you loo
On Wed, 1 Jul 2020 17:50:50 +0700
Ryan Joseph via fpc-pascal wrote:
> I'm using CodeToolBoss.GatherIdentifiers to get completions but with
> some units I'm getting 50k identifiers which is simply too much and
> too slow. Maybe of these are coming from the RTL I think and I would
> be ok with limi
I'm using CodeToolBoss.GatherIdentifiers to get completions but with some units
I'm getting 50k identifiers which is simply too much and too slow. Maybe of
these are coming from the RTL I think and I would be ok with limited some of
these results if possible.
Is there anyway to tell CodeTools t
