Source code |
|
1 2 3 4 |
Public Sub Form_Resize() Command1.Left = Me.Width - 250 Command1.Top = Me.Height - 150 End Sub |
Source code |
|
1 2 3 |
Public Sub Command2_Click() Command1.Anchor = vbBottomRight End Sub |
I worry about it, too. But since some month I have no longer an old machine. So it is nice to hear (or to read) that you have one and so you can test it on it on a machine with limitit resources.Since I am on an old machine I allways worry about speed and resources.
No difference in the performance? That is nice.Quoted
How do you think this will affect loading of Forms and Dialogs?
Of course I did not notice any difference, still I'd like to know.
Ok. I have now created a minor Update:Quoted
Would you mind posting an updated FrameworkTest-rev90 source!?
Source code |
|
1 |
cd Desktop |
Source code |
|
1 |
mkdir jabacosrc |
Source code |
|
1 |
cd jabacosrc |
Source code |
|
1 |
svn checkout http://jabacoframework.googlecode.com/svn/trunk/ jabacoframework |
Is integrated in Revision 91.Quoted
Maybe for the next version you could fix the ComboBox Bug
Jabaco Source |
|
1 2 3 4 5 |
Public Property Let ListIndex(val As Integer) If val >= -1 And val < ListCount Then Call Parent.setSelectedIndex(val) End If End Property |
Uuups. Sorry. Haven't seen it.About the little BugFix - what do you not like about '>=' ...
Jabaco Source |
|
1 2 3 4 5 6 7 |
'->ListBox.jsrc ' ******************************** SPECIAL FUNCTIONS ******************************** Public Sub RemoveItemAt(Index As Integer) myModel.removeElementAt(Index) Call fireChange() End Sub |
Thanks.I think it would be nice to have this in the framework:
Jabaco Source |
|
1 |
System.out.println(List1.Index) |
Jabaco Source |
|
1 2 3 4 5 6 7 8 9 10 |
Private Sub Form_Load() List1.AddItem ("First Entry") List1.AddItem ("Second Entry") List1.AddItem ("Third Entry") List1.AddItem ("Fourth Entry") End Sub Private Sub Command1_Click() List1.RemoveItem (1) End Sub |
Jabaco Source |
|
1 2 3 4 5 6 7 8 9 10 11 12 |
Public Class Form1 Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load ListBox1.Items.Add("First Entry") ListBox1.Items.Add("Second Entry") ListBox1.Items.Add("Third Entry") ListBox1.Items.Add("Fourth Entry") End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click ListBox1.Items.RemoveAt(1) End Sub End Class |
Jabaco Source |
|
1 2 3 |
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click ListBox1.Items.Remove("Third Entry") End Sub |
Jabaco Source |
|
1 |
Public Sub RemoveItemAt(Index As Integer) |
Jabaco Source |
|
1 |
Public Sub RemoveItem(v As Integer) |
Jabaco Source |
|
1 |
(Index As Integer) |
Jabaco Source |
|
1 |
RemoveItem(Index As Integer) |
I suppose that is not intentionally!?
Because I was unsure of side effects, when using Index, which already is internal used.Why not
Jabaco Source
1 (Index As Integer)
Ok, then there don't exsiting side-effects.Quoted
since for example in ComboBox.jsrc it also is
Jabaco Source
1 RemoveItem(Index As Integer)
Ok, you can change it to Index, if you want.Quoted
I don't mind naming it 'v' but maybe the user is more guided towards using the ListIndex otherwise
If the new features are nice and don't break compatiblity to VB6, why not?Quoted
It is a tough decision whether to add a feature or not!?
Should I set up polls?
Should I post the code before committing?
Should I commit and wait for replies?
I guess these questions are not new