Krakatoa Scripted GUI¶

Technical Information ¶

Krakatoa for 3ds Max has been designed as a hybrid system:
- The render plug-in, the Particle Flow operators and the core of the PRT Loader object have been implemented in C++ using the 3ds Max SDK.
- The User Interface of the Renderer and the PRT Loader object as well as several additional tools have been implemented using MAXScript, the built-in programming language of 3ds Max.
This structure combines the best characteristics of both worlds - C++ plugins are fast and powerful, but developing User Interfaces for them is a rather slow process, while MAXScript is slower and less powerful, but is perfectly suited for generation of User Interfaces in shortest time.
This also implies that the complete User Interface of the renderer is provided as source code and can be explored and modified by the end user or even completely replaced if desired - the User Interface layer and the actual plug-in renderer communicate through a set of string values stored in the renderer instance that can be defined, get and set via simple MAXScript calls.
When you assign the Krakatoa plug-in renderer in the Render Scene Dialog of 3ds Max, the Renderer tab will contain a single button which lets you open the Scripted GUI of Krakatoa.
- Pressing this button simply calls the MAXScript function FranticParticleRenderMXS.OpenGUI() which causes the scripted floater containing all Rollouts to open.

The scripted GUI uses two visible Rollout Floaters (one Primary and an optional Secondary Floater) which are containers of an arbitrary number of rollouts, and one invisible Floater hosting the hidden rollouts.
The visible Primary and Secondary Floaters provide the following features:

The Floater will store its last position and size in the renderer, which means that opening the file later will bring up the dialog at the last position used in that scene.
In addition, the Position of the floater will be stored in the file KrakatoaPreferences.ini in your Local Settings folder.
- You can use the Explore Folder… button in the Presets and History rollout to open a Windows Explorer at that location. Look under the [Dialog] category for the Position key.
- If a new instance of the renderer is being assigned (for example when switching from Scanline to Krakatoa), the last position stored in the INI file will be used for the new instance.
If the INI file could not be found (either because Krakatoa is being run for the first time or because the INI file has been renamed/moved/deleted), the Floater will open in the center of the main monitor.
Since desktop resolutions can vary from computer to computer, when positioning the Krakatoa GUI Floater, the requested position will be compared to the current desktop size and if the dialog is outside of the current desktop, it will be adjusted to remain visible. This means that opening a file saved on dual-monitor system where the floater was placed on the second monitor will automatically place it on the single monitor if there is no second monitor. Same applies to placing the floater too far left, top or bottom.

The Height of both Floaters can be changed by dragging its top or bottom border. The Width cannot be changed interactively.
The Position of the Secondary Floater can be locked to the right corner position of the Primary Floater (it is locked by default).
- This can be turned on and off via the right-click context menu of the [>>] float/dock icon in the upper right corner of every rollout.

The Primary Floater will display the Krakatoa Version string in its title bar - for example Krakatoa v1.5.1.38002.
- The first three digits describe the major, minor and update build numbers.
- The last five digit number is the internal submission ID of the version control system - each code submission to the system by any product increments this number, thus it can be used to distinguish between multiple builds of the same application even within the same day.