Button Objx Fixed Problems


The problem tracking number appears after the description in parentheses. Where two numbers are given, the new number appears first followed by the original number from the older tracking system.

Select Edit->Find in the browser menu to search for a particular keyword or tracking number.

| Version 2.0.40 | Version 2.0.35 | Version 2.0.30 |
| Version 2.0.20 | Version 2.0.15 | Version 2.0.10 |

Technical Issues Addressed— Release Date 7/24/07—Version 2.0.40

fpBtn control
  • The control no longer stops responding when using the property pages. (19257)

Technical Issues Addressed— Release Date 1/26/06—Version 2.0.35

fpBtn control
  • The button no longer causes the project to stop responding in Windows 98. (18082,17999)

Technical Issues Addressed— Release Date 2/25/05—Version 2.0.30

fpBtn control
  • The Click event now fires correctly when the active border is set. (9714)
  • The tab order now works correctly with the BackColorStyle property. (10669)
  • The correct button click event fires if there are multiple forms with buttons. (15318)
  • Closing the form no longer causes the program to stop responding. (15696)

Technical Issues Addressed— Release Date 10/12/01—Version 2.0.20

fpBtn control
  • Setting the ActiveBorder property to True no longer causes memory leaks. (6130/SCS10337)
  • A button control that has a non-rectangular shape no longer causes a Smart Heap error when used on a Tab control. (6487/JAP7483)
  • Button controls that are sub-classed and made invisible, remain invisible when another dialod opens and closes. (7871/KEM117)
  • The PALETTEINDEX macro now works for the button control with a user-created logical palette. (8126/WEB22949359359)
  • Choosing a button that is part of an index to close a form and set the form to nothing no longer cause Visual Basic to crash. (8380/SCS9110)
  • When you press Alt-T when the pointer is over the fpBtn control, the menu now drops down immediately. (8696/GIC12625)
  • The Click event now occurs when you press the space bar and the button has the focus. (8707/GIC12674)
  • If you set the ButtonState property to 1 (Two State) and click a specific cell, the fpBtn control now paints the inverted state correctly. (9048)
  • If you use the fpBtn control in Windows 98 and Visual Basic, loading and unloading multiple forms no longer causes Visual Basic to crash. (9095)
  • If you use the fpBtn control in Visual C++, the values entered on the Segments property page are now applied correctly. (9200)
  • Using icons in the fpBtn control now longer causes memory leaks. (9278)
  • The MouseOver event no longer occurs if you drag another window over the fpBtn control. (9331)
fpBln control
  • If you use the fpBln control on an Access form, the control will display when you minimize and restore the form. (8508/SCS9474)

Technical Issues Addressed— Release Date 8/3/00—Version 2.0.15

fpBtn control
  • The MouseMove event now returns the correct x- and y-coordinates when the pointer is moved outside the combo box control. (SCS7160)
  • If you use the ActiveX control in Visual C++, using the GetPicture and SetPicture functions to to swap the picture in two buttons no longer causes Button Objx to crash. (SCS9117)
  • The button is now updated when you set drop-shadow related properties for a transparent button. (SEL5045)
  • When you set the CellTransparent property to True within the Click event, the button is now updated. (SEL5051)

Technical Issues Addressed— Release Date 10/28/99—Version 2.0.10

fpBtn control
  • If you set the TabStop property to False in the Visual Basic properties window and run the project, the TabStop property does not change back to True when you close the project. (GIC7939)
  • If you set the GroupSelect property to 3 (One and Only One) for a group of two-state buttons, the Click event fires for each button in which a state change occurs. For example, if Button 1 in a group is down and you click Button 2, the Click event fires for Button 1 and then for Button 2. Note that if you use the mouse to click the button, the Click event fires only if you release the mouse button while the pointer is over the button that is clicked. (GIC8494)
  • If you set the NoPointerFocus property to True and you have a shaped button with a transparent background, the button no longer receives focus when you click the button or gray area. This was a bug in ButtonMaker 1.0 that has been fixed in Button Objx 2.0 only. (SCS6012)
  • In Visual C++ 6.0, if you enter button text using the property pages, the text no longer displays backwards in the button. (SCS7475)
  • If you use the ActiveX control, the IPersistStorage and IPersistStream interface now loads the button properties. (SCS7686)
  • If you use the ActiveX control, you can now access help from the property pages without an error. (SCS7791)
  • Loading an graphic resource in multiple buttons and then releasing the graphic from the buttons no longer causes a memory leak. (SCS8230) (SCS8493) (WEB920547718359)
  • The CellClicked property now returns the correct value when you use a mnemonic to press the button. (SCS8257)
  • When you set the BackStyle property to 0 (Transparent Gray Area) and change the shape of the button segments, the transparent gray area now paints correctly. (TEL54)
  • Using Visual Basic in Windows 95 or later, if you have multiple transparent buttons on a form, the buttons no longer have a paint problem when you stop the project and return to design time. (TIB284)

© 1999-2007, FarPoint Technologies, Inc. All rights reserved.