Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 2897

Summary:	[Contributions] Dynamic/Persisted "state" for viewActions (1GKKBCD)
Product:	[Eclipse Project] Platform	Reporter:	Darin Wright <darin.eclipse>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	Darin_Swanson, Michael_Rennie, Tod_Creasey
Version:	2.0	Keywords:	usability
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Darin Wright

2001-10-10 22:45:41 EDT

DW (9/24/2001 9:51:56 AM)
	The java debugger contributes several viewActions to the generic debug UI - 
	for example, show/hide static fields, show/hide final fields, and use step filters.
	These viewActions specify a starting "state" (i.e. they are toggle actions).

	However, the viewActions state is not persisted across workbench invocations.
	When the workbench is restarted, the original toggle state is used, which may not
	be the state in which the user left an action.

	In order to properly synchronize our settings with the presentation of the settings,
	viewActions need to persist their "state" attribute.

Comment 1 Kevin Haaland

2002-02-01 11:06:41 EST

This is a variation on the "saving workbench state" work that you have been 
working on.

Comment 2 Tod Creasey

2005-08-04 08:00:04 EDT

You can now do this via preferences,

Comment 3 Darin Wright

2005-08-04 09:15:51 EDT

Yes - but the action delegates that use the preferences are not instantiated 
until a selection change occurrs. The net effect is that an action delegate 
(toggle) will appear unchecked, when the preference is in fact on, until the 
delegate is instantiated and the action delegate can initialize itself from 
the preference setting.

For example:
* in the variables view, ensure that "Show Qualified Names" and "Show Static 
Variables" toggle actions are on (in the variables view drop down menu).
* Restart the workbench, and realize the menu without launching a debug 
session - the actions appear unchecked when in fact they are "on"
* start a debug session to a breakpoint
* select a variable
* now relaize the menu and see the actions are checked

The user can actually turn the toggles off without knowing it. The actions 
appear unchecked initially, and invoking the toggle has the net effect of 
instantiating the action, initializing from the pref (on), and then toggling 
the action off - which ios *very* confusing for the user.

Comment 4 Darin Wright

2005-08-04 09:16:37 EDT

CC'ing Tod for previous comment.

Comment 5 Darin Wright

2005-08-04 09:18:59 EDT

*** Bug 47995 has been marked as a duplicate of this bug. ***

Comment 6 Douglas Pollock

2005-08-04 14:04:34 EDT

Please see "Handling State" in the contributions proposal 
(http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-home/R3_1/contributions-proposal/requestForComments.html").

Comment 7 Michael Van Meekeren

2006-04-21 13:56:18 EDT

Moving Dougs bugs

Comment 8 Darin Wright

2006-07-25 14:26:34 EDT

*** Bug 139544 has been marked as a duplicate of this bug. ***

Comment 9 Paul Webster

2007-04-05 19:00:59 EDT

Assigning to component owner
PW

Comment 10 Eclipse Webmaster

2019-09-06 15:30:52 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.

Comment 11 Eclipse Genie

2022-01-23 05:56:48 EST

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.