![]() With the desktop as a parent, so when it is shown, a PVGUI_ViewWindow instance is passed to its setParent() method. It is created initally by pqMainWindowCore The PVViewer follows otherwise the standard structure of a Salome’s view (SUIT model).Ī special trick is used to make PVGUI_ViewWindow the parent of the pqViewManager widget. The class PVViewer_GUIElements is in charge of this. We hence create those elementsĪny way, but hide them, so that we can later show them again, once the ParaVis module is activated. However not wanted when the user just requested a 3D view, outside the ParaVis interface. Writing the pipeline, some menus, and other elements are very hard to connect after having set up a 3D view. the initialization of all the GUI elements needed for a later activation of the ParaVis interface: at the time of.the initialization of ParaView’s desired behaviors (class PVViewer_GUIElements).the initialization of the ParaView application ( pqApplicationCore).In the GUI module of SALOME, the folder src/PVViewer contains all the code needed to activate a minimal ParaViewģD view, without activating the ParaVis module itself. Historically the pvserver was not able to receive the connections from multiple clients, but this has been changed from or a Python script, using for example the module paraview.simple and the Connect() method.Seen by looking at the top element in the pipeline widget) either the standard ParaView GUI (where the name and type of the current server can be.detached, in which case, one has to launch the server first (possibly on another host) and then connect.built-in, in which case, launching ParaView suffices to activate it automatically.The pvserver represents the main visualisation server, and can be either: ) and a client part serves to control this server, and obviously visualize the final rendering. In two words, a server part (the pvserver) takes care of the ‘intensive’Ĭomputations (filter, etc. ParaView application ( pqCoreApplication). PVViewer_ViewManager: this class centralizes all the initialization logic (see method ParaviewInitApp) of the.the model imposed by SALOME’s GUI architecture to define a new type of view): Native 3D view (a pqTabbedMultiViewWidget) fit into the SUIT ![]() The folder also contain the adaptor classes needed to make the ParaView PVViewer_LogWindowAdapter: an adapter to redirect VTK and ParaView’s output messages to the SALOME’s message.PVViewer_GUIElements: see Viewer part (in GUI module).PVViewer_EngineWrapper: encapsulates the calls to the PVSERVER CORBA service in a dynamic fashion, so that GUI can beĬompiled without having a link dependency to the ParaVis module.Should automatically reconnect to the server if a disconnection occurs) PVViewer_Behaviors: re-instanciates the desired ParaView behaviors (a behavior defines for example the fact that ParaView.This folder contains the following classes: To make this work, a specific type of viewer ( PVViewer, short for ParaView viewer) has been created in the GUI module itself. For example the MED module now integratesĪ control visualization which is in fact a ParaView view. One can request a ParaView view without activating the ParaVis module itself. The CORBA engine and the graphical interface of the ParaVis module are located in the ParaVis module of SALOME. (ParaView’s viewer) located in the GUI module in the src/PVViewer folder. In terms of code structure, the main, all the initialization logic of ParaView is attached to the PVViewer The picture below summarizes the architecture: Or from a Python script, using for example the methods provided in the Python module pvsimple). Use the standard ParaView’s API to interact with the server (either from the C++ side, within SALOME’s GUI invokation of the standard ParaView’s API to connect to the pvserver (e.g.invokation of the method FindOrStartPVServer(): launches the pvserver process and returns its URL.activation of the PVSERVER CORBA service.request activation of PARAVIS (or request activation of a Paraview’s View).The standard ParaView mechanisms) to retrieve those objects. It only serves to establish the link with the pvserver. Hence, we emphazise the fact that the CORBA engine does not provide any access to the objects or the visualisation provide the URL of the pvserver, so that a client can connect to it.control the start and stop of the pvserver process.SALOME uses by default the detached server mode of ParaView: the pvserver is launched outside the main Salome processĪnd the ParaVis module, or the PVViewer view (Window -> ParaView view) connects to it.įollowing this logic, the PVSERVER CORBA service has a very restrained role. The PARAVIS module represents the integration of ParaView inside SALOME. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |