[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] How to prevent PDT to return unfiltered list of all possible proposals

Hi Karl,

Actually this is a good point for the way PDT suggests the proposals list today. I don't see any point in providing the full list in case no "hint" is provided to the selection mechanism. Maybe we should add a more sophisticated way to guess what the user really wants in these cases.

Anyway to answer your question - have you considered to use a goal/evaluator pruner. So in this cases that too much time is required you can just halt the selection mechanism and get a partial list.

Best regards,
-----Original Message-----
From: pdt-dev-bounces@xxxxxxxxxxx [mailto:pdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Karol Gusak
Sent: Wednesday, July 20, 2011 7:28 PM
To: pdt-dev@xxxxxxxxxxx
Subject: [pdt-dev] How to prevent PDT to return unfiltered list of all possible proposals


I'm using codeComplete() method from ISourceModule to get the
completion proposals for a PHP script. It works great, but in some
occasions PDT returns a big list of all proposals (for example, when
the caret position is just after the semicolon, or at the beginning of
empty line, and so on). Can I change this behavior? I'd like it to
return proposals only when the user already typed a part of the
method/field/keyword etc (or when he at least typed the dollar sign in
order to complete a variable), and return an empty array in each
situation when PDT would return all proposals it knows about. Is it


Best Regards,
pdt-dev mailing list