Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357151 - cannot toggle showing/hiding of scripts in Debug view
Summary: cannot toggle showing/hiding of scripts in Debug view
Status: RESOLVED WORKSFORME
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows 7
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Michael Rennie CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-08 15:37 EDT by Grant Gayed CLA
Modified: 2011-09-12 12:23 EDT (History)
1 user (show)

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 Grant Gayed CLA 2011-09-08 15:37:41 EDT 
- observed in the R3_2_maintenance stream and HEAD

- debug JS remotely via Crossfire
- the Debug view's drop-down has item Javascript > Show All Scripts, which should alternately hide/show the "Scripts" node in the view's tree
- however the Scripts node is always shown, regardless of how many times this menu item is selected
Comment 1 Grant Gayed CLA 2011-09-09 11:15:38 EDT 
Actually this is worse than I thought, because I'm now using a new workspace which did not show scripts by default, and I can't get it to start showing them.  So the menu item is failing to toggle this value regardless of whether it's on or off.
Comment 2 Michael Rennie CLA 2011-09-12 09:31:45 EDT 
(In reply to comment #1)
> Actually this is worse than I thought, because I'm now using a new workspace
> which did not show scripts by default, and I can't get it to start showing
> them.  So the menu item is failing to toggle this value regardless of whether
> it's on or off.

This works fine for me using a new or existing workspace.
Comment 3 Grant Gayed CLA 2011-09-12 12:23:59 EDT 
Perhaps I was seeing the problem with the R3_2_maintenance content because I was running it with a 4.2-stream eclipse build.  I went back to 3.6.2 and I don't see the problem with the JSDT R3_2_maintenance content there.

Closing report for now so that it doesn't appear as a R3_2_maintenance stream problem, will reopen if I see this again (I'm guessing it will only happen in the context of Eclipse 4.x).