![]() 'Remove' to remove this window and its hierarchy from the layout (any plugin it contains would then be listed again under the 'Unaffected' node). ![]() 'New tab' to add tabs to the selected window. ![]() This should pop up a menu containing three options : Let's pop up the window contextual menu by right clicking the 'Default window' item in the tree view. Plugins may also be swapped by drag and dropping one from the tree view or window preview and dropping it over another plugin in the preview window.įor further flexibility, one can create custom windows and tabs. The same mechanism is applied on the tree whenever a graphical plugin is deleted from the scenario. The tree structure is then automatically updated and simplified. Plugins can be removed from their hierarchy and placed back under the 'Unaffected' node by selecting them in the tree view and clicking 'Remove' in the context menu that pops up on a right click. Handle positions are saved along with the tree structure and thus The size of a plugin relative to the others lying on the same tab are modifiable by dragging the handles separating one plugin from its neighbours. It is possible to modify the plugins arrangement at any time, even as they have been placed in windows and tabs. One possible way of arranging 4 plugins in a single tab Its preview should appear on the right hand side, with an 'Empty' placeholder widget filling its single tab. By default, a single window is created and selected. Right is a preview of the currently selected window, if any. Left is a tree view containing a list of graphical plugins used in the active scenario and the current window layout. The window manager graphical interface is divided in two sections. Alternate presses on this button will show/hide the window manager. ![]() The window manager is popped up by clicking onto the 'window manager' button in OpenViBE Designer's top toolbar. Let's have a look at the window manager interface.įirst, let's create a new scenario. All that is required is just a little extra time at scenario edition time. It also makes it possible to set relative sizes, so that windows requiring more screen space always do get more than their neighbours. Moreover, by designing a window layout offline, the user ensures graphical plugins will always appear at the same location. all plugins fit in a single window, sparing the user the need to resize or place windows next to each other every time a scenario is played. This is where more clever window layouts can help, by arranging graphical plugins in window hierarchies so that, e.g. While this may work fine for simpler cases, the screen can quickly become cluttered with windows when more complex scenarios are being run. The default behaviour of the window manager consists in popping up as many toplevel, independent windows as required depending on the number of visualisation boxes contained in the active scenario. Examples of such boxes include the Signal Display, Power Spectrum or 3D Topographic Map plugins. They will therefore open one or several windows at scenario playing time. Some of these box algorithms, called visualisation boxes, are meant to display information. Why is this tool needed? OpenViBE scenarios are essentially made up of one or several box algorithms linked together to forward data as it is processed. Window layouts designed with this tool are then saved to disk in scenario files along with other scenario data and settings. It relies on functionalities made available by the OpenViBE Kernel to provide the user with an intuitive tool to arrange windows in space in a very flexible manner. This module is dedicated to the handling of 2D and 3D graphical windows in an OpenViBE scenario. This tutorial covers the role and usage of the designer's built-in window manager functionality. Designer Tutorial 3 : Using the Window Manager
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |