Abstract: Applications are managed on a computing device using a language independent application object. The computing device receives an indication that an application is to begin execution. Responsive to every indication that an application is to begin execution, a multi-thread aware singleton application object is instantiated within that application. The multi-thread aware singleton application object is configured to create a first application thread and a first application window for that application. The first application thread is associated with the first application window. The multi-thread aware singleton application object is configured to instantiate within an application regardless of a programming language or user interface framework utilized by that application.

Abstract: A volume control may be provided with some integrated graphical indication of the presence and/or level of an audio signal that it controls. For example, a slider-type volume control may be provided with a signal meter within the slider itself. A volume control may be provided with a mechanism for showing the non-mute volume control level of a volume when the volume control is muted. For example, a slider-type volume control may display a ghosted slider tab at the level of volume control in effect before muting while at the same time displaying a regular slider tab at a muted level. A user may be able to glance at a volume control and quickly and intuitively understand aspects of the volume control's state such as the level and condition of the signal that is flowing through or blocked by (if muted) the control.

Abstract: An architecture for customizable applications includes an application object and a customization object. The application object has internal logic that performs a set of fixed or predetermined actions, and a public object model. The public object model includes a set of public methods that are invocable on the application object, and a set of event source which are methods that can be implemented by a programmer and are called by the internal logic of the application object. By implementing methods invocable by the event sources, it is possible to extend and customize the functionality of the application object. The customizations are stored in a customization database for retrieval during the dynamic operation of the application object. Each customization may be identified by a “moniker,” which is a string having a hierarchical format. The moniker is derived partly from fixed data known to the application object, and partly from environmental data that is ascertained by the application object at run time.

Abstract: Specific tasks associated with debugging are performed in the background, prior to a user of an application development tool invoking the debugger. The tasks including (1) starting a hosting process, (2) loading a hosted runtime environment (e.g., .NET runtime) in the process, and (3) attaching a debugger to the hosting process, are performed in the background before the user commences debugging. Once the user invokes the debugger, the user's application is executed and debugged. Thus, the perceived time to start debugging is greatly reduced.

Abstract: A volume control may be provided with some integrated graphical indication of the presence and/or level of an audio signal that it controls. For example, a slider-type volume control may be provided with a signal meter within the slider itself. A volume control may be provided with a mechanism for showing the non-mute volume control level of a volume when the volume control is muted. For example, a slider-type volume control may display a ghosted slider tab at the level of volume control in effect before muting while at the same time displaying a regular slider tab at a muted level. A user may be able to glance at a volume control and quickly and intuitively understand aspects of the volume control's state such as the level and condition of the signal that is flowing through or blocked by (if muted) the control.

Abstract: An architecture for customizable applications includes an application object and a customization object. The application object has internal logic that performs a set of fixed or predetermined actions, and a public object model. The public object model includes a set of public methods that are invocable on the application object, and a set of event source which are methods that can be implemented by a programmer and are called by the internal logic of the application object. By implementing methods invocable by the event sources, it is possible to extend and customize the functionality of the application object. The customizations are stored in a customization database for retrieval during the dynamic operation of the application object. Each customization may be identified by a “moniker,” which is a string having a hierarchical format. The moniker is derived partly from fixed data known to the application object, and partly from environmental data that is ascertained by the application object at run time.

Abstract: A source code editor is used to develop multilanguage documents while providing the advanced editing functionality of secondary editors and without requiring the programmer to explicitly open and interface with the secondary editors. The multilanguage document is presented to the user in a primary application view of the primary editor. Code segments written in different languages are identified and sent to the appropriate secondary editors, which in turn create secondary documents that are transparent to the programmer. As edits are made to the primary application view of the document, the edits are replicated by the secondary editors behind the scene. Functionality that is enabled by the secondary editors, such as syntax coloring, auto-completion, and validation is identified by the primary editor and replicated in the primary application view, so as to appear as if the primary editor is inherently configured with the leveraged functionality of the secondary editors.

Abstract: Specific tasks associated with debugging are performed in the background, prior to a user of an application development tool invoking the debugger. The tasks including (1) starting a hosting process, (2) loading a hosted runtime environment (e.g., .NET runtime) in the process, and (3) attaching a debugger to the hosting process, are performed in the background before the user commences debugging. Once the user invokes the debugger, the user's application is executed and debugged. Thus, the perceived time to start debugging is greatly reduced.

Abstract: A system of the present invention includes a relational database management system (RDBMS), having an object-based, interactive visual-programming language providing programming by "visual inheritance." A user places screen objects (e.g., boxes, screen buttons, table objects, and the like) on an on-screen window or "form," visually attaches selected "properties" and "methods" to the screen objects, and then establishes an containership-based event model that dictates how and when these properties and methods will be invoked. An object inherits (derives) properties and methods from other (parent) objects via its visual containership. In this manner, the task of creating and maintaining application programs is greatly simplified. An alternative embodiment providing an "Object Explorer" is also described. The Explorer collapses object inspector and object tree functionality into a single UI (user interface) element.