Compile-time versions supported by DFL.

To use these versions, you will need to recompile DFL, and you will probably also need to supply these versions when compiling your programs.

An easy way to recompile DFL with different versions is to use the dfl_flags environment variable. For example, at the command line:

   set dfl_flags=-version=dflver1 -version=dflver2
   dfl -dfl-build

Versions

• DFL_UNICODE - Only call Unicode version of Windows API functions that accept strings. This essentially makes a Windows NT-only exe. Cannot be used with DFL_ANSI.

• DFL_ANSI - Only call ANSI version of Windows API functions that accept strings. This limits the Unicode capabilities on Windows NT. This essentially makes a Windows 9x exe, which also runs on NT. Cannot be used with DFL_UNICODE.

• NO_DRAG_DROP - Excludes Control drag/drop capabilities. Makes Control lighter weight.

• SUPPORTS_OPACITY - Layered windows are supported by the target platform. Disables a runtime check. Layered windows are supported on Windows 2000/XP and above.

• SUPPORTS_MOUSE_TRACKING - Windows API function TrackMouseEvent is definitely supported in user32 by the target platform. Disables a runtime check.

• SUPPORTS_COMMON_CONTROLS_EX - Windows API function InitCommonControlsEx is definitely supported by the target platform. Disables a runtime check. This function is supported on Windows 95 with IE 4 and above.

• NO_MDI - Excludes MDI support. Makes Form lighter weight.

• SET_DFL_092 - DFL 0.9.7: this version is obsolete, use DflCompat.MENU_092

• SET_DFL_095 - DFL 0.9.7: this version is obsolete, use DflCompat.CONTROL_RECREATE_095

• DFL_EXE - Set by dfl.exe. Do not set this version manually.

• Tango - Required when using the Tango library.

• Also see DflCompat