Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

Eclipse Plug-in Developer Guide
Previous Page Home Next Page


Eclipse Platform
Release 3.5

Package org.eclipse.debug.ui.contexts

Provides a set of interfaces and classes for debug context management.

See:
           Description

Interface Summary
IDebugContextListener A debug context listener is notified of debug context events.
IDebugContextManager Manages debug context services.
IDebugContextProvider Interface common to all objects that provide a debug context.
IDebugContextService Debug context service for a window.
ISuspendTrigger A suspend trigger notifies listeners when a launch suspends at a context where debugging should begin.
ISuspendTriggerListener Listeners are notified when a launch has suspended at a context where debugging should begin.
 

Class Summary
AbstractDebugContextProvider Abstract implementation of a debug context provider.
DebugContextEvent A debug context event.
 

Package org.eclipse.debug.ui.contexts Description

Provides a set of interfaces and classes for debug context management.

Package Specification

This package provides a set interfaces and classes to manage debug contexts.

A debug context represents an active state of a program being debugged. The active debug context drives the enabled state of debug actions (step, terminate, etc.), source lookup, visible variables, watch expression values, etc. The debug platform allows clients to register for context change notification in order to respond to changes in the active debug state, as well as register context providers that drive the active debug state. The debug platform has context listeners and providers itself. For example, the debug platform's stepping actions register for context change notification to update enabled state and the Debug view registers as a context provider.

There can be any number of debug contexts within a workbench window, but at any one time there is only one active debug context within a part and one active context within a workbench window. The debug platform provides a debug context service per window (IDebugContextService) that allows clients to register context providers for that window, and register for change notification within the window or a specific part in the window. If there is only one context provider in a window, it provides the context for the entire window as well as its part. If there is more than one context provider for a window, the context provider associated with the most recently active part provides the context for that window. It is possible to register a context provider that has no associated part. Only one such context provider can be registered with each service (window). A context provider that has no associated part provides context for its window only if there are no other context providers registered for that window.

A debug context is represented by a selection (ISelection). This allows for single or multi-element selections as well as text selections to provide context. Listeners are notified of context changes with debug context events (DebugContextEvent) . An event specifies the context that has changed and a bit mask describing how the context has changed. The platform defines two types of changes - activation and state change. An activated state indicates a new context - for example a thread suspending at a breakpoint or after a step. An activation triggers variables to refresh, source lookup, etc. A state change indicates that a previously activated state has changed. For example, a stack frame or thread that was activated has completed an implicit evaluation. A state change triggers action enabled states to update.


Eclipse Platform
Release 3.5

Guidelines for using Eclipse APIs.

Copyright (c) Eclipse contributors and others 2000, 2008. All rights reserved.


 
 
  Published under the terms of the Eclipse Public License Version 1.0 ("EPL") Design by Interspire