Recent changes to Replacing_usage_of_BWCC

Replacing_usage_of_BWCC modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 16 Mar 2018 09:50:36 -0000

--- v13
+++ v14
@@ -22,6 +22,8 @@
   * Replace the BWCC control classes by standard Windows classes. 
   * Correct the dialog look-and-feel, editing controls as needed. 
   * Optionally, use TGlyphButton in the dialog class to have similar buttons with icons. 
+
+


 ---
 ## An example of BWCC dialog conversion

Replacing_usage_of_BWCC modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 16 Mar 2018 09:49:56 -0000

--- v12
+++ v13
@@ -4,10 +4,13 @@

 [TOC]

+

+
 ---
 ## What is BWCC?

 BWCC stands for Borland Windows Custom Controls. It is a library developed by Borland to give controls a nicer 3D look for applications running on Windows 3. Borland C++ 4 made use of it, but with the coming of Windows 95, which introduced it's own 3D look, BWCC became outdated. As a replacement, OWL 5 introduced TGlyphButton for adding icons to buttons. 
+


 ---
 ## Converting BWCC dialogs

Replacing_usage_of_BWCC modified by Vidar Hasfjord

Vidar Hasfjord — Mon, 26 Feb 2018 15:02:01 -0000

--- v11
+++ v12
@@ -49,7 +49,7 @@
        CONTROL "", 998, "BorBtn", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 98, 74, 37, 25
      END

-
Here is how the dialog looks: 
+Here is how the dialog looks: 

 [[img src=Bwcc1.png]] 

@@ -76,7 +76,7 @@
        CONTROL "", 998, "Button", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 98, 74, 37, 25
      END

-
Unfortunately, after recompiling, the dialog looks pretty awful: 
+Unfortunately, after recompiling, the dialog looks pretty awful: 

 [[img src=Bwcc2.png]] 

@@ -97,7 +97,7 @@
      CONTROL "Cancel", 2, "Button", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 53, 74, 37, 25
      CONTROL "Help", 998, "Button", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 98, 74, 37, 25

-
The dialog now looks better: 
+The dialog now looks better: 

 [[img src=Bwcc3.png]] 

@@ -118,8 +118,7 @@
        new TGlyphButton(this, 998, TGlyphButton::btHelp);
      }

-
-
Now the buttons will have icons: 
+Now the buttons will have icons: 

 [[img src=Bwcc4.png]]

Replacing_usage_of_BWCC modified by Vidar Hasfjord

Vidar Hasfjord — Thu, 09 Oct 2014 11:46:29 -0000

--- v10
+++ v11
@@ -1,11 +1,15 @@
+# Replacing the Borland Windows Custom Controls (BWCC)
+
 OWLNext 6.30 is the last version that supports usage of BWCC. Since version 6.32 it is no longer available, and the function TApplication::EnableBWCC has been removed. Legacy applications that still make use of BWCC will have to be converted to use the standard dialog controls instead. TGlyphButton can be used to put icons on buttons.

 [TOC]

+---
 ## What is BWCC?

 BWCC stands for Borland Windows Custom Controls. It is a library developed by Borland to give controls a nicer 3D look for applications running on Windows 3. Borland C++ 4 made use of it, but with the coming of Windows 95, which introduced it's own 3D look, BWCC became outdated. As a replacement, OWL 5 introduced TGlyphButton for adding icons to buttons. 

+---
 ## Converting BWCC dialogs

 There are several steps that must be taken to remove the usage of BWCC in a legacy OWL application: 
@@ -16,10 +20,12 @@
   * Correct the dialog look-and-feel, editing controls as needed. 
   * Optionally, use TGlyphButton in the dialog class to have similar buttons with icons. 

+---
 ## An example of BWCC dialog conversion

 This example illustrates the steps needed to convert a simple BWCC dialog to the native style. 

+

 ### The original BWCC dialog created with Borland C++ 5.02

 Code for the dialog resource: 
@@ -43,11 +49,11 @@
        CONTROL "", 998, "BorBtn", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 98, 74, 37, 25
      END

-
-Here is how the dialog looks: 
+
Here is how the dialog looks: 

 [[img src=Bwcc1.png]] 

+

 ### Removing BWCC dialog and control classes

 The first step is to remove the BWCC classes. The line `CLASS "BorDlg_Gray"` is removed from the dialog resource, and the control classes are replaced with Windows analogues (which is "Button" in most cases): 
@@ -70,11 +76,11 @@
        CONTROL "", 998, "Button", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 98, 74, 37, 25
      END

-
-Unfortunately, after recompiling, the dialog looks pretty awful: 
+
Unfortunately, after recompiling, the dialog looks pretty awful: 

 [[img src=Bwcc2.png]] 

+

 ### Correcting dialog controls

 There are two obvious problems: (1) the group box caption has moved to the center, underneath the radio buttons, and (2) the push buttons are empty. To fix the group box, add the style BS_GROUPBOX and remove the BSS_* styles, which are BWCC-specific. To fix the second issue, add captions to the buttons: 
@@ -91,16 +97,16 @@
      CONTROL "Cancel", 2, "Button", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 53, 74, 37, 25
      CONTROL "Help", 998, "Button", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 98, 74, 37, 25

-
-The dialog now looks better: 
+
The dialog now looks better: 

 [[img src=Bwcc3.png]] 

+

 ### Adding icons to the buttons

 Use the TGlyphButton class to add icons to the dialog buttons. 

-  * Add the line `#include <owl/glyphbtn.rc>` in the beginning of the resource file. This is required if linking with the static versions of OWLNext libraries. 
+  * Add the line `#include <owl glyphbtn.rc="">` in the beginning of the resource file. This is required if linking with the static versions of OWLNext libraries. 
   * In the dialog class, add TGlyphButton instances for the buttons. If there are already TButton members used to manipulate the buttons, replace them with TGlyphButton. If not, then simply create the new objects in the dialog constructor, without keeping them in member variables. 

 For example: 
@@ -113,12 +119,13 @@
      }

-Now the buttons will have icons: 
+
Now the buttons will have icons: 

 [[img src=Bwcc4.png]] 

+

 ### Further steps

 An additional step may be to redesign the look of the dialog for a more modern style. For instance, the height of the buttons should ideally be reduced, and controls may need to be rearranged for better spacing and layout. 

-You may also want to enable themes; the visual styles introduced in Windows XP. Otherwise, the Windows controls are rendered in the classic Windows 95 style (as shown in the screenshots in this article). See "How do I enable visual styles (themes) in my application" in the [FAQ](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Frequently_Asked_Questions#How_do_I_enable_visual_styles_.28themes.29_in_my_application.3F). Also, see the example [XPThemes](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Examples#XP_Themes) in the OWLNext installation. Support for themed glyph buttons was added in OWLNext 6.34. See "How do I get themed rendering of TGlyphButton" in the [FAQ](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Frequently_Asked_Questions#How_do_I_get_themed_rendering_of_TGlyphButton.3F). 
+You may also want to enable themes; the visual styles introduced in Windows XP. Otherwise, the Windows controls are rendered in the classic Windows 95 style (as shown in the screenshots in this article). See "[How do I enable visual styles (themes) in my application](http://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#how-do-i-enable-visual-styles-themes-in-my-application)" in the [FAQ](http://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions). Also, see the example [XPThemes](http://sourceforge.net/p/owlnext/wiki/Examples#xp-themes) in the OWLNext installation. Support for themed glyph buttons was added in OWLNext 6.34. See "[How do I get themed rendering of TGlyphButton](http://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#how-do-i-get-themed-rendering-of-tglyphbutton)" in the FAQ.

Replacing_usage_of_BWCC modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 27 Jun 2014 10:09:04 -0000

--- v9
+++ v10
@@ -121,4 +121,4 @@

 An additional step may be to redesign the look of the dialog for a more modern style. For instance, the height of the buttons should ideally be reduced, and controls may need to be rearranged for better spacing and layout. 

-You may also want to enable themes; the visual styles introduced in Windows XP. Otherwise, the Windows controls are rendered in the classic Windows 95 style (as shown in the screenshots in this article). See "How do I enable visual styles (themes) in my application" in the [FAQ](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Frequently_Asked_Questions#How_do_I_enable_visual_styles_.28themes.29_in_my_application.3F). Also, see the example [XPThemes](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Examples#XP_Themes) in the OWLNext installation. 
+You may also want to enable themes; the visual styles introduced in Windows XP. Otherwise, the Windows controls are rendered in the classic Windows 95 style (as shown in the screenshots in this article). See "How do I enable visual styles (themes) in my application" in the [FAQ](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Frequently_Asked_Questions#How_do_I_enable_visual_styles_.28themes.29_in_my_application.3F). Also, see the example [XPThemes](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Examples#XP_Themes) in the OWLNext installation. Support for themed glyph buttons was added in OWLNext 6.34. See "How do I get themed rendering of TGlyphButton" in the [FAQ](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Frequently_Asked_Questions#How_do_I_get_themed_rendering_of_TGlyphButton.3F).

Replacing_usage_of_BWCC modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 27 Jun 2014 10:09:04 -0000

--- v8
+++ v9
@@ -120,3 +120,5 @@
 ### Further steps

 An additional step may be to redesign the look of the dialog for a more modern style. For instance, the height of the buttons should ideally be reduced, and controls may need to be rearranged for better spacing and layout. 
+
+You may also want to enable themes; the visual styles introduced in Windows XP. Otherwise, the Windows controls are rendered in the classic Windows 95 style (as shown in the screenshots in this article). See "How do I enable visual styles (themes) in my application" in the [FAQ](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Frequently_Asked_Questions#How_do_I_enable_visual_styles_.28themes.29_in_my_application.3F). Also, see the example [XPThemes](http://sourceforge.net/apps/mediawiki/owlnext/index.php?title=Examples#XP_Themes) in the OWLNext installation.

Replacing_usage_of_BWCC modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 27 Jun 2014 10:09:03 -0000

--- v7
+++ v8
@@ -1,37 +1,24 @@
+OWLNext 6.30 is the last version that supports usage of BWCC. Since version 6.32 it is no longer available, and the function TApplication::EnableBWCC has been removed. Legacy applications that still make use of BWCC will have to be converted to use the standard dialog controls instead. TGlyphButton can be used to put icons on buttons. 
+
 [TOC]

 ## What is BWCC?

-BWCC stands for Borland Windows Custom Controls. It is a library developed by Borland to give a nicer 3D look of applications under Windows 3.x. Borland C++ 4.x made use of it, but with the coming of Windows 95 and it's own 3D look, BWCC become outdated. Borland C++ 5.x used TGlyphButton istead to add icons to the buttons in dialogs. 
-
-  
-
-
-## Obsoleting BWCC
-
-OWLNext 6.30 is the last version that supports usage of BWCC. In OWLNext 6.32, along with dropping support for Borland C++ 5.02, BWCC is no longer supported and the EnableBWCC() method of TApplication is removed. Legacy applications still making use of BWCC will have to be converted to using standard dialog controls and TGlyphButton can be used to put icons on buttons. 
-
-  
-
+BWCC stands for Borland Windows Custom Controls. It is a library developed by Borland to give controls a nicer 3D look for applications running on Windows 3. Borland C++ 4 made use of it, but with the coming of Windows 95, which introduced it's own 3D look, BWCC became outdated. As a replacement, OWL 5 introduced TGlyphButton for adding icons to buttons. 

 ## Converting BWCC dialogs

-There are several things that must be done in the application to remove the usage of BWCC: 
+There are several steps that must be taken to remove the usage of BWCC in a legacy OWL application: 

-  * Remove calls to TApplication::EnableBWCC() 
-  * Remove the "BorDlg" or "BorDlg_Gray" class from the definition of the dialog resource 
-  * Replace the BWCC classes of the controls in the dialog with standard Windows classes 
-  * Correct the dialog look and feel, editing controls as needed. Optinally add TGlyphButtons in the dialog class to have similar buttons with icons. 
-
-  
-
+  * Remove calls to TApplication::EnableBWCC. 
+  * Remove the "BorDlg" or "BorDlg_Gray" class from dialog resources. 
+  * Replace the BWCC control classes by standard Windows classes. 
+  * Correct the dialog look-and-feel, editing controls as needed. 
+  * Optionally, use TGlyphButton in the dialog class to have similar buttons with icons. 

 ## An example of BWCC dialog conversion

-This is an example of the steps to convert a simple BWCC dialog to a new look. 
-
-  
-
+This example illustrates the steps needed to convert a simple BWCC dialog to the native style. 

 ### The original BWCC dialog created with Borland C++ 5.02

@@ -61,12 +48,9 @@

 [[img src=Bwcc1.png]] 

-  
-
-
 ### Removing BWCC dialog and control classes

-The forst step is to remove the BWCC classes. The line **CLASS "BorDlg_Gray"** is removed from the dialog resource, and the control classes are replaced with Windows analogs (which is "Button" in most cases): 
+The first step is to remove the BWCC classes. The line `CLASS "BorDlg_Gray"` is removed from the dialog resource, and the control classes are replaced with Windows analogues (which is "Button" in most cases): 

      IDD_CLIENT DIALOG 6, 15, 189, 124
      STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION
@@ -87,18 +71,13 @@
      END

-After compiling, the dialog looks pretty awful: 
+Unfortunately, after recompiling, the dialog looks pretty awful: 

 [[img src=Bwcc2.png]] 

-  
-
-
 ### Correcting dialog controls

-There are two obvious problems: the group box caption has moved to the center, underneath the radio buttons, and the push buttons are empty. 
-
-To fix the group box, add the style **BS_GROUPBOX** and remove the BSS_* styles, which are BWCC-specific. Also, add captions to the buttons: 
+There are two obvious problems: (1) the group box caption has moved to the center, underneath the radio buttons, and (2) the push buttons are empty. To fix the group box, add the style BS_GROUPBOX and remove the BSS_* styles, which are BWCC-specific. To fix the second issue, add captions to the buttons: 

      CONTROL "Project file type", -1, "Button", BS_GROUPBOX | WS_CHILD | WS_VISIBLE | WS_GROUP, 8, 8, 128, 48
      CONTROL ".&RC", 151, "Button", BS_AUTORADIOBUTTON | WS_CHILD | WS_VISIBLE | WS_GROUP | WS_TABSTOP, 12, 21, 33, 12
@@ -117,15 +96,14 @@

 [[img src=Bwcc3.png]] 

-  
-
-
 ### Adding icons to the buttons

-With the help of the new TGlyphButton class, icons will be added to the dialog buttons. 
+Use the TGlyphButton class to add icons to the dialog buttons. 

-  * Add the line **#include <owl/glyphbtn.rc>** in the beginning of the resource file. This is required if linking with the static versions of OWLNext libraries. 
-  * In the dialog class, add TGlyphButton instances for the buttons. If there are already TButton members used to manipulate the buttons, replace them with TGlyphButton. If not, then simply create the new objects in the dialog constructor, without keeping them in member variables: 
+  * Add the line `#include <owl/glyphbtn.rc>` in the beginning of the resource file. This is required if linking with the static versions of OWLNext libraries. 
+  * In the dialog class, add TGlyphButton instances for the buttons. If there are already TButton members used to manipulate the buttons, replace them with TGlyphButton. If not, then simply create the new objects in the dialog constructor, without keeping them in member variables. 
+
+For example: 

      TBWCCTestDlgClient::TBWCCTestDlgClient(TWindow* parent, TResId resId, TModule* module) : TDialog(parent, resId, module)
      {
@@ -135,13 +113,10 @@
      }

-Now the buttons will have the new icons: 
+Now the buttons will have icons: 

 [[img src=Bwcc4.png]] 

-  
+### Further steps

-
-### Next steps
-
-The next step can be redesigning the look of the dialog to be more modern. The heigth of the buttons should be decreased and controls may be rearranged. 
+An additional step may be to redesign the look of the dialog for a more modern style. For instance, the height of the buttons should ideally be reduced, and controls may need to be rearranged for better spacing and layout.

Replacing_usage_of_BWCC modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 27 Jun 2014 10:09:03 -0000

--- v6
+++ v7
@@ -28,7 +28,7 @@

 ## An example of BWCC dialog conversion

-This is an exmaple of the steps to convert a simple BWCC dialog to a new look. 
+This is an example of the steps to convert a simple BWCC dialog to a new look.

Replacing_usage_of_BWCC modified by Ognian Tchernokojev

Ognian Tchernokojev — Fri, 27 Jun 2014 10:09:03 -0000

--- v5
+++ v6
@@ -54,8 +54,6 @@
        CONTROL "", 1, "BorBtn", BS_DEFPUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_GROUP | WS_TABSTOP, 8, 74, 37, 25
        CONTROL "", 2, "BorBtn", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 53, 74, 37, 25
        CONTROL "", 998, "BorBtn", BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 98, 74, 37, 25
-    
-    
      END

Replacing_usage_of_BWCC modified by Ognian Tchernokojev

Ognian Tchernokojev — Fri, 27 Jun 2014 10:09:03 -0000

--- v4
+++ v5
@@ -4,9 +4,15 @@

 BWCC stands for Borland Windows Custom Controls. It is a library developed by Borland to give a nicer 3D look of applications under Windows 3.x. Borland C++ 4.x made use of it, but with the coming of Windows 95 and it's own 3D look, BWCC become outdated. Borland C++ 5.x used TGlyphButton istead to add icons to the buttons in dialogs. 

+  
+
+
 ## Obsoleting BWCC

 OWLNext 6.30 is the last version that supports usage of BWCC. In OWLNext 6.32, along with dropping support for Borland C++ 5.02, BWCC is no longer supported and the EnableBWCC() method of TApplication is removed. Legacy applications still making use of BWCC will have to be converted to using standard dialog controls and TGlyphButton can be used to put icons on buttons. 
+
+  
+

 ## Converting BWCC dialogs

@@ -17,9 +23,15 @@
   * Replace the BWCC classes of the controls in the dialog with standard Windows classes 
   * Correct the dialog look and feel, editing controls as needed. Optinally add TGlyphButtons in the dialog class to have similar buttons with icons. 

+  
+
+
 ## An example of BWCC dialog conversion

 This is an exmaple of the steps to convert a simple BWCC dialog to a new look. 
+
+  
+

 ### The original BWCC dialog created with Borland C++ 5.02

@@ -51,6 +63,9 @@

 [[img src=Bwcc1.png]] 

+  
+
+
 ### Removing BWCC dialog and control classes

 The forst step is to remove the BWCC classes. The line **CLASS "BorDlg_Gray"** is removed from the dialog resource, and the control classes are replaced with Windows analogs (which is "Button" in most cases): 
@@ -78,6 +93,9 @@

 [[img src=Bwcc2.png]] 

+  
+
+
 ### Correcting dialog controls

 There are two obvious problems: the group box caption has moved to the center, underneath the radio buttons, and the push buttons are empty. 
@@ -101,6 +119,9 @@

 [[img src=Bwcc3.png]] 

+  
+
+
 ### Adding icons to the buttons

 With the help of the new TGlyphButton class, icons will be added to the dialog buttons. 
@@ -120,6 +141,9 @@

 [[img src=Bwcc4.png]] 

+  
+
+
 ### Next steps

 The next step can be redesigning the look of the dialog to be more modern. The heigth of the buttons should be decreased and controls may be rearranged.