Bug 48087 - [OpenModes] OpenStrategy should not use only static var to keep state.
Summary: [OpenModes] OpenStrategy should not use only static var to keep state.
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Boris Bokowski CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2003-12-04 11:43 EST by Eduardo Pereira CLA
Modified: 2021-10-14 09:43 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eduardo Pereira CLA 2003-12-04 11:43:54 EST
I would like to use OpenStrategy on a swt widget that I have in an editor.
It would always use the the OpenStrategy.SINGLE_CLICK.

Since the CURRENTMETHOD is stored in a static var. I can't have an instance of
OpenStrategy that overwrites the default behavior and I can't change the 
current method otherwise it would change the eclipse setting.

Maybe, the OpenStrategy could have an instance var that if set would overwrite 
the setting in the static var.
Comment 1 Nick Edgar CLA 2003-12-08 17:56:50 EST
Eduardo, since you did this work originally (and are still a committer), would 
you be able to make this change yourself.  No breaking API changes please.
Comment 2 Nick Edgar CLA 2006-03-15 11:20:15 EST
Reassigning bugs in component areas that are changing ownership.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:37:14 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 4 Eclipse Genie CLA 2021-10-14 09:43:56 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. 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.