#88710 - 2002-10-16 05:35 PM
Kixforms - Version 2.1.1 (Build 35) Pre-Release Round Up
|
Shawn
Administrator
Registered: 1999-08-13
Posts: 8611
|
Just another checkpoint in terms of whats cooking in the Kixforms oven. Version 2.1.1 will be released this weekend - a maintenance build mostly - a few bug fixes - the big change is with ListView sorting. Build 35 has a totally new revamped sorting engine - more accurate and little faster too boot. But mostly wanted to enumerate the work items that are still on table though ... I'm trying to keep a running list of suggestions and issues and will keep rolling them into each round-up until they all get done. As always - please feel free to add any items or comments.
code:
1) View-only TextBoxes 2) Masked TextBoxes 3) Multiline Tooltip Support 4) Support for complete suite of Mouse events
- OnMouseEnter - OnMouseHover - OnMouseLeave 5) RichEdit control 6) Enhanced (Automatic) handling of ListBox horizontal scrollbar. 7) ListView Enhancements - HideColumnHeaders property - Programatically set FocusedItem - Set Items.Count in one-shot (Done) - Sort method (sort by alpha or numeric) - Implement Items.Insert method. 8) Fix file filter for FileOpenDialog and FileSaveDialog 9) Enhanced ProgressBar - support for embedded textual display of progress message fe. "60% complete". Some other goodies as well. 10) TabStrip/MultiPage support 11) Fix image control resizing problem re: BorderStyle. 12) Fix set focus to textbox for InputBox (Done) 13) Be able to remove/customize frame borders. 14) Bring back support for Menus and Menu Items 15) Timer Reset method. 16) Implement BrowseForFolderDialog. 17) Fix Spinner long duration click issue. 18) TreeView support. 19) Running Kixforms from the System Tray. 20) Implement FIND for ListBox,ComboBox and ListView. 21) Implement dynamic form resizng framework. 22) CheckBoxes that support the third undetermined state. 23) ... Your request here ...
By the way - after much offline discussion and debate and soul-searching - decided to stick with the existing dotnet ListView interface (Items/SubItems) ... feel that its best to keep to the new VB standard ... not just for ListView but for all objects going forward. Some stuff, like enhanced ProgressBar, isn't even implemented in dotnet - but we'll cross those bridges when we get to them. AS well - the RichEdit control is called RichTextBox in VB ... not crazy about the name but going to bite the bullet on that one too [ 22. October 2002, 18:32: Message edited by: Shawn ]
|
Top
|
|
|
|
#88713 - 2002-10-16 10:40 PM
Re: Kixforms - Version 2.1.1 (Build 35) Pre-Release Round Up
|
Shawn
Administrator
Registered: 1999-08-13
Posts: 8611
|
wah - you don't like my little clock there Jooel ? I scoured the Internet for ages looking for that icon - one of the few icons embedded as a resource inside Kixforms DLL (which would lead me to another suggestion that I will postpone for the time being ).
Krabourn - the TextBox .Default thingy has already been fixed think what I will do is email you the pre-release and you can check it out for yourself. The behavior of the textbox has changed in this regard - the text box will only eat the enter key (not trigger default) if it has the AcceptsReturn property set to TRUE.
The timer reset thingy might need some talk - not too sure what you wanted to do ... reset (pause) the timer or reset the timer to its original interval ... this can always be achieved by just re-setting the interval to its original value. In other words ... everytime you set the interval, it kills the existing timer and resets it to whatever you set it to. Thoughts ?
More on the timer icon thingy ... if I had to do it all over again, i probably would NOT have made the timer a seperate object (window). Its implemented as a simple LABEL control with an embedded picture of an alarm clock. Probably should have made it just a method of any given form or control object, fe.
$form.timer = 2000 $form.ontimer = "form_timer()"
and if one really wanted a seperate object to act as a timer - could just create a hidden label control and use that ... eh water under the bridge as they say!
-Funja
|
Top
|
|
|
|
#88721 - 2002-10-17 04:56 AM
Re: Kixforms - Version 2.1.1 (Build 35) Pre-Release Round Up
|
Shawn
Administrator
Registered: 1999-08-13
Posts: 8611
|
ok - so the gut feel was correct:
quote:
TextBox.AcceptsReturn Property Gets or sets a value indicating whether pressing ENTER in a multiline TextBox control creates a new line of text in the control or activates the default button for the form. Property Value TRUE if the ENTER key creates a new line of text in a multiline version of the control; false if the ENTER key activates the default button for the form. The default is true.
Remarks If the value of this property is false, the user must press CTRL+ENTER to create a new line in a multiline TextBox control. If there is no default button for the form, then the ENTER key will always create a new line of text in the control, no matter what the value of this property.
The deal is a follows - with VB in this scenario - even if you have AcceptsReturn set to FALSE, one can still enter a carriage return using ^ENTER ... but I haven't managed to have Forms reproduce this behavior yet - im still trying and I will get there - just not in the near term ... will this be a problem, ex. if you have a default button configured - you will never be able to hit enter into a MULTI-LINE textbox. Single-line textboxes this all doesn't matter anyways. And like I say - all this just until I do manage to get it working.
|
Top
|
|
|
|
Moderator: Shawn, ShaneEP, Ruud van Velsen, Arend_, Jochen, Radimus, Glenn Barnas, Allen, Mart
|
0 registered
and 248 anonymous users online.
|
|
|