I want to request expansion of ctrlCreate command to allow passing of CONFIG types instead of STRING class so we can create controls from insides of existing UI config structures. Having to define createable controls outside of destination display config is inconvenient because you want to group your createable controls alongside the display they will be used in. It is somewhat bearable in case of displays because you can include one fine and define both createable controls and display alongside each other, but becomes an issue when displays are inside RscTitles, you have to have 2 separate files describing the title display and its createable controls. Example of an inconvenience:

#include "my_title_display_ctrlCreate_stuff.hpp"
class RscTitles {
	#include "my_title_display.hpp";
};

With this feature you'd be able to define createable controls in display itself, in custom class or already existing in its intended place in display controls:

class MyTitleDisplay {
	idd = 123;
	...
	class Controls {
		class ControlWeCopyWithCtrlCreate:RscWhatever {...};
	};

	class ControlsToolbox {
		class ControlWeUseInCtrlCreate:RscWhatever {...};
	};
};

and then do:

_ctrl_copy = _display ctrlCreate [missionConfigFile >> "RscTitles " >> "MyTitleDisplay" >> "Controls" >> "ControlWeCopyWithCtrlCreate", -1];
_ctrl_new = _display ctrlCreate [missionConfigFile >> "RscTitles " >> "MyTitleDisplay" >> "ControlsToolbox" >> "ControlWeUseInCtrlCreate", -1];