Bug 563245 - Add ability to figure out how the IJavaCompletionProposalComputer is triggered
Summary: Add ability to figure out how the IJavaCompletionProposalComputer is triggered
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.16   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-16 04:40 EDT by Gayan Perera CLA
Modified: 2024-05-01 19:51 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gayan Perera CLA 2020-05-16 04:40:59 EDT 
Today when a IJavaCompletionProposalComputer is invoked, there is no way this is invoked by the first CTRL+SPACE or it was part of the cycling of CTRL+SPACE or it was triggered by a shortcut.

This will be important for slow proposal computers to skip some heavy work in the first run but provide the full result when invoked by a shortcut or through cycling.
Comment 1 Eclipse Genie CLA 2022-05-11 07:56:00 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2024-05-01 19:51:34 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.