WSF
WsfBrawler.cpp File Reference
Include dependency graph for WsfBrawler.cpp:

Functions

void WSF_BRAWLER_EXPORT Register_wsf_brawler (WsfApplication &aApplication)
UT_PLUGIN_EXPORT void WsfPluginVersion (UtPluginVersion &aVersion)
UT_PLUGIN_EXPORT void WsfPluginSetup (WsfApplication &aApplication)

Function Documentation

◆ Register_wsf_brawler()

void WSF_BRAWLER_EXPORT Register_wsf_brawler ( WsfApplication & aApplication)

Registers the wsf_brawler extension with the application so it is available for use.

References WsfApplication::ExtensionDepends(), WsfApplication::ExtensionIsRegistered(), WsfApplication::RegisterExtension(), WsfApplication::RegisterFeature(), and WSF_REGISTER_EXTENSION.

Referenced by WsfPluginSetup().

◆ WsfPluginSetup()

UT_PLUGIN_EXPORT void WsfPluginSetup ( WsfApplication & aApplication)

This method is called when the plugin is loaded. It must have exactly this signature (name and parameter) to succeed. As we only have an application reference at load time, one usually registers an application extension, within which the ScenarioCreated method can be overridden to gain access to a scenario. If one also needs access to the simulation, one should also instantiate and register a simulation extension by overriding the SimulationCreated method in the scenario extension.

References Register_wsf_brawler().

◆ WsfPluginVersion()

UT_PLUGIN_EXPORT void WsfPluginVersion ( UtPluginVersion & aVersion)

This method is called when the plugin is loaded to ensure that the plugin and the executable loading it were built with the same version of the plugin API.

References WSF_PLUGIN_API_COMPILER_STRING, WSF_PLUGIN_API_MAJOR_VERSION, and WSF_PLUGIN_API_MINOR_VERSION.

Copyrights Multiple, All Rights Reserved