The Interface
DxWnd comes with a nice and simple Graphic User Interface: when started, it shows a form pretty muck like the one in the following picture:
In the main window there is the list of hooked programs: DxWnd can currently handle up to 256. Trying to add more than that will give an error message. Keep in mind that DxWnd bundles contain a export subfolder where all supported games have their own default configuration ready to be imported, but because of the program absolute path value, these entries will actually work only after updating the path with the proper local value.
As shown in the picture, each configuration line includes an icon which color tells the general status of the program, as follows:
|
blank icon: the configuration refers to a not existent program's path, so that the entry won't work unless the path is corrected. |
|
grey icon: the hook is not enabled: this program can be activated by the DxWnd menu, but won't be windowed. |
|
green icon: the hook is enabled and the program will be windowed when run either from the DxWnd interface or however else. |
|
red icon: the program requires code injection, then it will need to be activated from the DxWnd interface only. |
You can activate command either via the top menu, or by right clicking on a row in the application list.
DxWnd is also able to operate iconized in the System Tray, from where it shows its state (either IDLE, READY or RUNNING) and run a few useful commands.
DxWnd detects the video settings when is started, and compares it to the current value after killing a task or terminating itself: in case it finds differences, it prompts you asking whether you want the previous screen setting to be restored. This is quite useful to handle all the games that terminates without restoring the previous setting, as it may happen when they die abnormally.
