FireFly Visual Designer 2.86 October 12, 2007 - Added support for the new .chm PowerBASIC Help file. 2.85 October 8, 2007 - Corrected bug that would generate incorrect MF_GRAYED, MF_CHECKED resource code if a project has more than one top menu. - Corrected code generation bug whereby modeless popup Forms with WS_VISIBLE = FALSE would display. - Corrected code generation bug that outputted wrong LoadImage flags for icons (rather than bitmaps) used as toolbar buttons. - Corrected bug in TB_FFCOM.DLL that would display TLibAttr error when attempting to select ProgID for an ActiveX control. 2.81 March 19, 2007 - Corrected bug whereby captionbar was not painted in active color in the visual designer. 2.80 March 18, 2007 - Tested on Windows Vista Premium. In order to conform to proper security, samples and ini file is used from the applicable AppData folder rather than the application install directory. - Corrected bug whereby Labels with Transparent BackStyle properties would not change color in the Designer when the parent Form changed color. - Corrected code generation for OptionButton IDC_ control ID's to ensure that they are consecutive. - Added the %LR_LOADTRANSPARENT flag for code generation for the "Hot Image" for Toolbar buttons. - Corrected problem whereby IP Control would delete FireFly's internal global font handle. - Corrected code generation problem with projects that contain multiple Tab Controls that use the same "Name" property and that use icons in the tabs. - Corrected problem with StatusBar Editor not setting the Panel AutoSize correctly nor generating correct code. - Cleaned up code from several of the sample programs and set the compiler to default to PBWIN 8. - Several minor cosmetic fixes to the designer and code generation. 2.75 August 19, 2006 - Corrected bug whereby an invalid heap handle could be passed when freeing memory as a control is being destroyed. - Added the SS_OWNERDRAW style for Label controls. - Corrected code generation problem for setting the background color of the MDIClient when a bitmap may have been previously used. - The TAG property is now allowed to be used for 3rd Party controls. The author must define "TAG" as a property in the *.ctl file. - Corrected code generation for Tab Controls on multiple modeless Forms (including TabControls in Control Arrays). - Added code generation code to correctly set the background color of controls when they are disabled (via FF_CONTROL_DISABLE or EnableWindow). - User defined #Includes are now in the code generation process placed immediately after the Win32API and Common Controls Includes lines. A simple text file "User_Includes.inc" is searched for in the Project directory. If found, it is included in the generated code. The user can manually edit this file to place a list of includes in a pre-defined order of the user's choice. - Added a second "Tag" property called "Tag2" that operates in a similar fashion to the existing tag property for Controls/Forms.