|
|
|||||||
See there are some old dawgs on the board tonight ... help ... One of the biggest things that causes me the most grief is trying to devise "names" for new properties. There are the old, legacy names from VB ... there are some standard OLE names for ActiveX controls, and then there are the "new" names from .NET. Case in point ... I'm sitting here wondering if I should call the property that allows TABS in TEXTBOXES, eg: VB: (these aren't even supported in VB): ActiveX/VBA: $TextBox.TabKeyBehavior = True/False $TextBox.EnterKeyBehavior = True/False .NET $TextBox.AcceptsReturn = True/False $TextBox.AcceptsTab = True/False Anyone got an opinion ? Thing is ... if forms ever supported the older embedded OLE controls, then those will require the use of the old ActiveX/VBA name (because we talk directly to the control, not to the form) ... but the new .NET name is better (I think) more understandable and intuitive ... plus newer Controls might use this standard going forward ... errggg ... suggestions ? -Shawn [ 27. August 2002, 03:12: Message edited by: Shawn ] |
||||||||
|
|
|||||||
Didn't we do the .net thing on the mouse pointer thingy? Maybe it should be: $form.tabthingy Huh, no? Ok, the dot net thing then. |
||||||||
|
|
|||||||
Yeah, I remember that "MousePointer" thingy ... its just that I had this mental block against calling it "Cursor" for some reason ... guess I've seen too much code that uses the MousePointer name ... actually, I kinda regret not going with the .NET Cursor name ... is it too late ... can I change my mind ? Going for AcceptsTab and AcceptsReturn ... |
||||||||
|
|
|||||||
I'd say we look forward and use the .NET version. |
||||||||
|
|
|||||||
Dot NET sounds good and yes Shawn, you're entitled to change your mind. Legacy shmegacy, heck with backwards compatability! |
||||||||
|
|
|||||||
Go with the .Net naming. That naming also seems more logical to me. |
||||||||
|
|
|||||||
.net for me too Actually, not only it's .net, but it was used in other languages before .net too... If I recall correctly from my Delphi days, that's the way to do it in Delphi... Later, Madruga {edit} P.S.: About legacy: if you do change stuff from one version to another, please don't forget to include those changes in a readme, so as to make life easier for someone trying to upgrade to a more recent version of KiXForms... {/edit} [ 27. August 2002, 11:16: Message edited by: Fernando Madruga ] |