KiXforms Forum Index KiXforms
The Forum for the KiXforms Community
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 Quick Links 
Site News
Downloads
Documentation
Donations
Script Archive
Tracking Systems

New features in the next beta release.
Goto page 1, 2, 3  Next
 
Post new topic   Reply to topic    KiXforms Forum Index -> Discussion
View previous topic :: View next topic  
Author Message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 3:41 pm    Post subject: New features in the next beta release. Reply with quote

Just thought I would enumerate some of the new features in the next build. Although the CHM help file is coming along nicely, its not quite ready for primetrime yet, the following are taken right out of the CHM though. I will post them as individual posts:
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 3:43 pm    Post subject: Reply with quote

GroupBox

Description

Adds a GroupBox to the specified object

Syntax

$GroupBox = $Object.Controls.GroupBox ( Text, Left, Top, Width, Height )

Settings

Text - A string expression specifying the text associated with the object.

Left, Top, Width, Height - Numeric expressions specifying the location and size of the control.
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 3:46 pm    Post subject: Reply with quote

The new way of aligning text on controls is by using the TextAlign property. Currently it only applies to the GroupBox object but will be extending it to other controls.

TextAlign

Description
Gets or sets the alignment of text on the object.

Syntax
$Object.TextAlign = Number

Settings
GroupBox:

1 TopLeft Text is vertically aligned at the top, and horizontally aligned on the left.

2 TopCenter Text is vertically aligned at the top, and horizontally aligned at the center.

3 TopRight Text is vertically aligned at the top, and horizontally aligned on the right.


Others:

1 TopLeft Text is vertically aligned at the top, and horizontally aligned on the left.

2 TopCenter Text is vertically aligned at the top, and horizontally aligned at the center.

3 TopRight Text is vertically aligned at the top, and horizontally aligned on the right.

4 MiddleLeft Text is vertically aligned in the middle, and horizontally aligned on the left.

5 MiddleCenter Text is vertically aligned in the middle, and horizontally aligned at the center.

6 MiddleRight Text is vertically aligned in the middle, and horizontally aligned on the right.

7 BottomLeft Text is vertically aligned at the bottom, and horizontally aligned on the left.

8 BottomCenter Text is vertically aligned at the bottom, and horizontally aligned at the center.

9 BottomRight Text is vertically aligned at the bottom, and horizontally aligned on the right.
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 3:48 pm    Post subject: Reply with quote

For CheckBoxes and RadioButtons, the new way of aligning the check box on the control is by using the:

CheckAlign Property

Description
Gets or sets a value specifying the horizontal alignment of the check box in the control.

Syntax
$Object.CheckAlign = Integer

Settings
One of the following values:

Value Member Description
4 MiddleLeft The checkbox is aligned in the middle and to the left.
6 MiddleRight The checkbox is aligned in the middle and to the right.
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 3:50 pm    Post subject: Reply with quote

To check if a CheckBox or RadioButton is in the Checked state, use the:


Checked Property

Description
Gets or sets whether the object is in the checked state.

Syntax
$Object.Checked = Boolean

Settings
True if the object is in the checked state; otherwise, false. The default value is false.
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 3:52 pm    Post subject: Reply with quote

For the ListView, theres now an option to allow you to HIDE or NOT HIDE the selection bar when the ListView looses focus - so that the user can still determine what item was selected:

HideSelection Property

Description
Gets or sets a value indicating whether the selection in the control remains highlighted when the control loses focus.

Syntax
$Object.HideSelection = Boolean

Settings
True if the selection does not appear highlighted when the control loses focus; false if the selection still appears highlighted when the control loses focus. The default is true.

Remarks
When this property is set to false, the selection in the control remains highlighted in a different color than the current selection color specified by the operating system when the control loses focus. You can use this property to keep items that are selected by the user visible when the user clicks a different control on the form or moves to a different window.
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 3:58 pm    Post subject: Reply with quote

This one is a special request:

LabelEdit Property

Description
Gets or sets a value indicating whether the user can edit the labels of items in the control.

Syntax
$Object.LabelEdit = Boolean

Settings
True if the user can edit the labels of items at run time; otherwise, false. The default is false.

Remarks
When the LabelEdit property is set to true, the user is able to modify the text of an item by clicking the item text to select it and then clicking the item text again to put the label text into edit mode. The user can then modify or replace the item's text label. The text of subitems cannot be modified if this property is set to true. To change the text of subitems, you can display a dialog box to users when they double-click a subitem in the control.
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 4:01 pm    Post subject: Reply with quote

Another request, and very usefull for resizable forms:

MinimumSize Property

Description
Gets or sets the minimum size the form can be resized to.

Syntax
$Object.MinimumSize = Width, Height

Settings
A array of two numbers representing the minimum Width and Height of the form.


Last edited by Shawn on Wed Apr 02, 2003 4:03 pm; edited 1 time in total
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 4:02 pm    Post subject: Reply with quote

Yet another request ... would love to see this feature implemented for the BBChecker Slider window ...

Opacity Property

Description
Gets or sets the opacity level of the form.

Syntax
$Object.Opacity = Number

Settings
The level of opacity for the form. The default is 100.

Remarks
This property enables you to specify a level of transparency for the form and its controls. When this property is set to a value less than 100, the entire form, including borders, is made more transparent. Setting this property to a value of 0 makes the form completely invisible. You can use this property to provide different levels of transparency or to provide effects such as phasing a form in or out of view. For example, you can phase a form into view by setting the Opacity property to a value of 0 and gradually increasing the value until it reaches 100.

Windows 2000 Platform Note: This property has no effect on platforms that cannot display layered windows.
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 4:05 pm    Post subject: Reply with quote

The new way of querying whether a toggle-style tool button is in the "pushed" state is by using the:

Pushed Property

Description
Gets or sets a value indicating whether a toggle-style control is currently in the pushed state.

Syntax
$Object.Pushed = Boolean

Settings
True if a toggle-style control is currently in the pushed state; otherwise, false. The default is false.
Back to top
View user's profile Send private message
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Wed Apr 02, 2003 4:18 pm    Post subject: Reply with quote

There going to be a new property called FormBorderStyle that will allow one to set the BorderStyle of a form. The difference between this property and the older BorderStyle property is that the FormBorderStyle settings (and resulting window adornments) will adhere strictly to the dotnet model.
Back to top
View user's profile Send private message
Sealeopard
KiXforms Aficionado
KiXforms Aficionado


Joined: 05 Mar 2003
Posts: 436
Location: Boston, MA

PostPosted: Thu Apr 03, 2003 2:47 pm    Post subject: Reply with quote

Wow. I think I now really need the CHM file. Way too many features to remember them all.

Thanks, Shawn.

_________________
Jens

'There are two kinds of vessels, submarines and targets.'
Back to top
View user's profile Send private message Send e-mail MSN Messenger
krabourn
KiXforms Aficionado
KiXforms Aficionado


Joined: 05 Mar 2003
Posts: 273
Location: San Antonio. TX

PostPosted: Thu Apr 03, 2003 4:01 pm    Post subject: Reply with quote

Can't wait for that .CHM file. Did BrowseForFolder sneek into the next release?
_________________
Kelly
Back to top
View user's profile Send private message Send e-mail MSN Messenger
Shawn
KiXforms Developer
KiXforms Developer


Joined: 22 Feb 2003
Posts: 1983
Location: Canada

PostPosted: Thu Apr 03, 2003 4:20 pm    Post subject: Reply with quote

I'm going to be making a run for the BrowseForFolderDialog (BrowseFolderDialog ?) (and a couple others) right after the next release. I first had to build the "infrastructure" to support a new "namespace" that will house the dialogs. I want the current namespace (Kixtart.Form) to be dedicate to supporting only Forms and Controls.

The new namespace is called "Kixtart.Forms.Dialogs" but its still implemented out of Kixforms.dll (of course). The current suite of common dialogs supported out of this namespace is as follows:

ColorDialog
FontDialog
MessageBox (yes, a MessageBox object)
OpenFileDialog
SaveFileDialog

Other to be dones include CopyFileDialog (FileOperationDialog), PrintDialog, BrowseNetworkDialog, BrowseDomainDialog, and others.

But currently, there are two ways to instantiate the existing dialogs out of the new namespace:

1) Through the Dialogs property of any control that supports this property (currently the Form object). For example, a new ColorDialog object can be created like this:

$ColorDialog = $Form.Dialogs.ColorDialog()

2) Stand-alone, and without the involvement of a Form object, throught the CreateObject function, like this:

$ColorDialog = CreateObject("Kixtart.Forms.Dialogs").ColorDialog

Which method is used depends on what information is available to the developer at the time, for example if a script already has a Form instantiated it may be just a convience to create it out of the form object, plus, if created out of the form, when the dialog is displayed, the form can be used as a reference point for positioning.

The second method may be more suited to scripts that don't have a form, or maybe more likey, for UDF`s that display a common dialog but that don't want a builtin dependency of requiring a Form.

Anyways, at the end of the preverbial day, all the common dialogs will be supported and even better, a couple of custom dialogs that I would love to see developed, for example a ProgressDialog that works like a MessageBox with a ProgressBar, and some others.

-Shawn
Back to top
View user's profile Send private message
jim
KiXforms Supporter
KiXforms Supporter


Joined: 05 Mar 2003
Posts: 76
Location: Philadelphia, PA

PostPosted: Fri Apr 04, 2003 4:09 pm    Post subject: Reply with quote

Wow! This is really incredible. Excellent work man! Shocked
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    KiXforms Forum Index -> Discussion All times are GMT
Goto page 1, 2, 3  Next
Page 1 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group