Pass arguments for plugin initialization. This method must create and register all the services that the plugin wants to offer : system, renderers, materials, Ui ... More...
Tells wether the plugin wants to add a widget (inside the UI tab widget) or not. If it does, it must provide a name for it, and getWidget() will be called. More...
Creates the widget to be added to the ui and then returns it. If connections are needed (between plugin ui and plugin internals) they have to be created here. More...
Tells wether the plugin wants to add actions or not. If it does, getAction() will be called for each ...
Note
Q_RADIUM_PLUGIN_METADATA: we use this macro to load a default metadata files, which sets the basic metadata required by Radium. The macro is defined in RaPluginBase.hpp. If you need to use your own file, you have to extend the filespluginMetaDataXXXX.json, packaged with Radium in the following folder
source tree: src/PluginBase/
install tree: lib/cmake/Radium/ Then, replace Q_RADIUM_PLUGIN_METADATA by Q_PLUGIN_METADATA( IID "RadiumEngine.PluginInterface" FILE "yourPluginMetaDataRelease.json" ) or Q_PLUGIN_METADATA( IID "RadiumEngine.PluginInterface" FILE "yourPluginMetaDataDebug.json" ) depending on the debug mode
Tells wether the plugin wants to add a widget (inside the UI tab widget) or not. If it does, it must provide a name for it, and getWidget() will be called.
Parameters
name
Name of the tab to be added, if needed.
Returns
True if the plugin wants to add a widget, false otherwise
Returns the action to be added to the ui and then returns it.
Returns
The action to add.
Warning
This mechanism implies QAction copies and does not allow to control the appearance of multiple actions with interlocked behaviors, e.g. play/pause and stop buttons.
Creates the widget to be added to the ui and then returns it. If connections are needed (between plugin ui and plugin internals) they have to be created here.
Allocated renderers are given to the application and MUST not be destroyed by the plugin
Note
Plugins that want to manage OpenGL resources MUST ENSURE at the time they create/access these resources that the current openGLContext is the one pass when initializing OpenGL here and stored in the PluginContext ...
When this function is called from the application, The active OpenGL Context is the one that will be used for rendering.
Developers of plugins that need to manage OpenGL resources in a direct way (recommended for plugins that manage OpenGL resources for rendering or interaction with rendering) must implement this method and memorize the viewer of the PluginContext. Each time they need to create or destroy an OpenGL resource, they must activate this context (viewer->makeCurrent()) and realease it after usage (viewer->doneCurrent())
Pass arguments for plugin initialization. This method must create and register all the services that the plugin wants to offer : system, renderers, materials, Ui ...
Parameters
context
: plugin context containing the engine and UI interfaces.
The documentation for this class was generated from the following file: