Bug 216647 - [Workbench] Closed heap status reopens on restart
Summary: [Workbench] Closed heap status reopens on restart
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows Vista
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-25 16:58 EST by Willian Mitsuda CLA
Modified: 2019-09-06 16:17 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 Willian Mitsuda CLA 2008-01-25 16:58:54 EST 
Eclipse 3.4 M4:

If you have the heap status active in the trim area, and select "Close" from its context menu, the "Show Heap Status" preference, in General preference page is not updated. So, in the next Eclipse restart, the heap status is shown again.
Comment 1 Paul Webster CLA 2008-01-28 10:28:56 EST 
So make the close reset the preference as well?

PW
Comment 2 Tod Creasey CLA 2008-01-28 10:31:33 EST 
Changing a preference on closing something is not a work flow we generally use - I think this would confuse people.
Comment 3 Willian Mitsuda CLA 2008-01-28 12:23:36 EST 
Don't you think having the heap status restored in next workbench restart, after having closed it is more confusing?
Comment 4 Willian Mitsuda CLA 2008-01-28 12:26:08 EST 
Also, the "Always run in background" checkbox in progress dialog updates the "Always run in background" preference as well.
Comment 5 Tod Creasey CLA 2008-01-28 12:29:24 EST 
I think the real issue is that it re-opens on you correct? I'm not sure if this is a trim issue or a heap status issue but it is clearly the wrong behaviour
Comment 6 Willian Mitsuda CLA 2008-01-28 15:16:03 EST 
Exactly.
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:17:35 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.