mirror of
https://github.com/TorqueGameEngines/Torque3D.git
synced 2026-01-20 04:34:48 +00:00
c2d1e9d654
Shifts "Help" menubar entry in world editor to use new API structure as example/test Removes extraneous 'MainEditor' Adds EditorCore module Moved Menubuilder to EditorCore module Fixes Help Menu editor settings so they properly point at modern documentation and forum URLs Fixes handling of MenuBar so when inserting new items, ensures the menubar refreshes as would be expected Adds remove function to menubar to remove a menu Removes old commented console methods from menubar file Adds checks for onMouseDown and onMouseUp for PopupMenu so items that are submenus aren't clickable like normal items
26 lines
1.1 KiB
Plaintext
26 lines
1.1 KiB
Plaintext
|
|
function ToolsModule::onCreate(%this)
|
|
{
|
|
// ----------------------------------------------------------------------------
|
|
// Initialize core sub system functionality such as audio, the Canvas, PostFX,
|
|
// rendermanager, light managers, etc.
|
|
//
|
|
// Note that not all of these need to be initialized before the client, although
|
|
// the audio should and the canvas definitely needs to be. I've put things here
|
|
// to distinguish between the purpose and functionality of the various client
|
|
// scripts. Game specific script isn't needed until we reach the shell menus
|
|
// and start a game or connect to a server. We get the various subsystems ready
|
|
// to go, and then use initClient() to handle the rest of the startup sequence.
|
|
//
|
|
// If this is too convoluted we can reduce this complexity after futher testing
|
|
// to find exactly which subsystems should be readied before kicking things off.
|
|
// ----------------------------------------------------------------------------
|
|
|
|
ModuleDatabase.LoadExplicit( "EditorCore" );
|
|
//ModuleDatabase.LoadExplicit( "Tools_ObjectViewer" );
|
|
}
|
|
|
|
function ToolsModule::onDestroy(%this)
|
|
{
|
|
|
|
} |