Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 82987 - 3.1 M4 can cause overview ruler to disappear forever
Summary: 3.1 M4 can cause overview ruler to disappear forever
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P2 major (vote)
Target Milestone: 3.1 M5   Edit
Assignee: Tom Hofmann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 85319 (view as bug list)
Depends on:
Blocks: 566667
  Show dependency tree
 
Reported: 2005-01-17 11:52 EST by Dani Megert CLA
Modified: 2020-09-04 04:03 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2005-01-17 11:52:47 EST
I20050112-1200

The overview ruler preferences (UI) for Text and JDT editor have been removed.
This can result in lost overview ruler if the text editor preference has been
set to false.
Comment 1 Dani Megert CLA 2005-01-17 11:53:07 EST
would be good to have for M5
Comment 2 Tom Hofmann CLA 2005-02-09 08:32:27 EST
Fixed > 20050209

-- 

The preference still exists in code, but is not surfaced to the user.

The solution is to add migration code that checks once per workspace whether the
preference is off and then re-enables it. Once that check has been made, set
another preference that the migration has happened, so that if a geek tool
manipulates the preference later, it does not get modified by the migration code
any more.
Comment 3 Tom Hofmann CLA 2005-02-09 08:33:01 EST
Dani, please verify.
Comment 4 Dani Megert CLA 2005-02-10 04:28:31 EST
Verified in code ==> OK.

Verified the following scenario:
1. started 3.0
2. disabled overview ruler for text editor
3. started 3.1 without fix
   ==> no overview ruler in text and Java editor
4. started 3.1 with fix
   ==> overview ruler in text and Java editor
Comment 5 Dani Megert CLA 2005-02-15 15:21:24 EST
*** Bug 85319 has been marked as a duplicate of this bug. ***