From:  mac
|
On: 2006/11/15 22:26:39
|
the usuals seem to be "btn" and "cmd".
what's your preferred prefix for a command button?
|
|
|
From: coral47
|
On: 2006/11/15 22:35:28
|
|
What you talkin' 'bout, Willis?
|
|
|
From: StevenB
|
On: 2006/11/15 22:53:03
|
|
"btn" since you ask, but then I'm Delphish.
|
|
|
From: Pino Carafa
|
On: 2006/11/16 02:07:28
|
"cmd" since I'm a VB nerd
Indeed. It depends on the language.
|
|
|
From: Baldrick
|
On: 2006/11/16 02:38:07
|
"cmd" since I'm a C# wanquer with a VB6 past. And I have a nasty habit of engineering my style to something subtly different every 6 months...
I don't think that's strictly Hungarian though (rather it's a sensible coding style convention). I always thought Hungarian notation was reasonably strictly defined and only of real use in C/C++ (and then maybe only 16-bit Win16 API code, I only ever saw it in books like Charles Petzold's "Programming Windows") since it conveyed specific type information, eg.
int iCount; // Integer
int* piCount; // Pointer to an integer
int** ppiCount; // Pointer to a pointer to an integer
char far * lpszName; // Far (long) pointer to a zero-terminated string
The theory was that the style would avert certain compile-time errors by making them stick out like a sore thumb - particularly when involving C pointers. I also believe it was named "Hungarian" in recognition of the nationality of legendary Microsoft programmer Charles Simonyi, who devised it. I think this style has been mostly debunked and is now considered obsolete.
|
|
|
From: mac
|
On: 2006/11/16 05:25:55
|
i'm an Access/SQL Server guy and i never saw "btn" until early this year when i took over a project from a developer in the uk. he used "btn". so i figured it was atlantic ocean dependant. but now the Wrox Visual Basic 2005 book i'm reading uses "btn". the author's name is Willis, so i think coral is on to something.
that's 3 for "cmd" and 1 for "btn", but the dogs just got out of the gate!
|
|
|
From: Hooligan
|
On: 2006/11/16 06:45:08
|
I thought Hungarian notation was out these days.
I use 'but'.
|
|
|
From: PaulHews
|
On: 2006/11/16 11:33:57
|
|
cmd for me. I used to use the int, str, dbl etc. prefixes in VB, but in VB.NET gave it up according to fashion. Now when I maintain code in VB 6, I'm wildly inconsistent (as opposed to being just mildly inconsistent.)
|
|
|
From: Pino Carafa
|
On: 2006/11/16 14:22:01
|
|
Yup. Same here. In VB6 it now is whatever the hell I please on the day.
|
|
|
From: mac
|
On: 2006/11/16 15:45:38
|
|
and... how's that workin' for ya?
|
|
|
From: dragontooth
|
On: 2006/11/16 16:43:06
|
Command1 That was the last time I used a command button, I got curious and looked at some previous projects and the majority followed suite.
The only thing I follow is m for local variables, i for input, o for output, io for input/output, t for Type. Otherwise if the vaiable is mCntr it is what I dim it as, look :), subs/functions call it what it does SetRFSheets set the panel lengths adds to and existing count if there ... I can't spell to good so that helps a lot also
|
|
|
From: stone5150
|
On: 2006/11/16 17:51:12
|
|
I prefer bctmnd
|
|
|
From: coral47
|
On: 2006/11/16 22:12:45
|
>> so i think coral is on to something.
Crap. It's so irritating when a SA remark, backfires. <sigh>
|
|
|
From: mac
|
On: 2006/12/26 13:43:40
|
|
This conversation is now closed.
|
|
