Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322753 - It should be possible to disable the override indicator
Summary: It should be possible to disable the override indicator
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-editor (show other bugs)
Version: 8.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 8.0   Edit
Assignee: Anton Leherbauer CLA
QA Contact: Anton Leherbauer CLA
URL:
Whiteboard:
Keywords:
Depends on: 320561
Blocks:
  Show dependency tree
 
Reported: 2010-08-16 03:57 EDT by Anton Leherbauer CLA
Modified: 2010-09-24 02:44 EDT (History)
3 users (show)

See Also:


Attachments
Disable override indicator (4.56 KB, patch)
2010-09-17 23:46 EDT, Marc-André Laperle CLA
no flags Details | Diff
Disable override indicator (5.22 KB, patch)
2010-09-17 23:51 EDT, Marc-André Laperle CLA
aleherb+eclipse: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Leherbauer CLA 2010-08-16 03:57:53 EDT
Computing the override indicator has an impact on performance, therefore it should be possible to disable it.

JDT does this by checking the visibility preferences of the override indicator annotation type.
Comment 1 Marc-André Laperle CLA 2010-09-17 23:46:05 EDT
Created attachment 179162 [details]
Disable override indicator

Patch inspired by JDT. I had to change ASTProvider.WAIT_NO to ASTProvider.WAIT_ACTIVE_ONLY so that the changes would be applied immediately.
Comment 2 Marc-André Laperle CLA 2010-09-17 23:51:41 EDT
Created attachment 179163 [details]
Disable override indicator

Also copied the comments.
Comment 3 Anton Leherbauer CLA 2010-09-23 08:11:46 EDT
Thanks, I have committed the patch to HEAD with 2 minor changes:
- Don't request an AST on createPartControl
- Use flag ASTProvider.WAIT_NO instead of ASTProvider.WAIT_ACTIVE_ONLY

This is to avoid blocking the UI while computing an AST or waiting for it.
Comment 5 Marc-André Laperle CLA 2010-09-23 12:33:00 EDT
(In reply to comment #3)
> - Use flag ASTProvider.WAIT_NO instead of ASTProvider.WAIT_ACTIVE_ONLY

What I'm seeing is that it's possible to enable the override indicators then apply and the indicators do not appear.
Comment 6 Anton Leherbauer CLA 2010-09-24 02:44:15 EDT
(In reply to comment #5)
> (In reply to comment #3)
> > - Use flag ASTProvider.WAIT_NO instead of ASTProvider.WAIT_ACTIVE_ONLY
> 
> What I'm seeing is that it's possible to enable the override indicators then
> apply and the indicators do not appear.

Right, this can happen when the indexer is running.  In this case the override markers would appear as soon as the indexer has finished.
On the other hand, this is quite unintuitive.  I think we should update immediately.  The override indicators might be incomplete in this case (because of the incomplete index), but this will be fixed when the index has been updated.
I changed the flag back to WAIT_ACTIVE_ONLY.