Re: Conversion Problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On 2008-07-11, Ken Halter <Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
"Tom Shelton" <tom_shelton@xxxxxxxxxxxxxxxxxx> wrote in message
news:btqdnQ-VaImePerVnZ2dnUVZ_gydnZ2d@xxxxxxxxxxxxxx


Oh, please. VB6 sixes help sucks rocks. VB5 had the last decent help.
The
internet has been the primary source of real help for years.

...oh... and, if you still have VB6, drop a control on the form, select it
and hit F1. That will take you to the help for that control, showing all
events, properties and methods. Select any property in the property window,
hit F1. Help will open and show sample code to use that property. Open the
object browser and select any property/method/event... hit F1. If that
doesn't show help, your environment's trashed or it's a 3rd party object
that never had context sensitive help.


All of which works in VS as well... What I, thought we were talking about was
the actual quality of the help - not the mechanism for obtaining it.

Duh, I said that was one of the reasons for control arrays? In VB.NET,
they
don't have to be a control array and they don't have to be the same
type.
Or
are you claiming that you can have the same event procedure handle the
TextChanged event of a combobox and a textbox in VB6?

ummm... yes I am... I'm not sure why this is such a surprise. Have you
never
coded a sub to be called from multiple places? What difference does it
make
where the change event's coming from, or even what control fired it? If
that's so important, pass the control to the sub. No big deal. geez.


So, you admit that the SAME event procedure can NOT handle the same event
for
diffent individual controls (not control arrays) or differing types of
controls... Thanks.

So, you admit there's no benefit to using the same event handler for
multiple controls when the functionality has been there for what... 3
decades?... Thanks.


I'm not sure how you got that from my statements... It's definately a benifit
at times.

As for your work around, sure - used to do it all the time, still do as a
matter of fact. It just depends on the task at hand. C#/VB.NET just adds
an
extra tool to my belt.

We all know how a plumber looks when wearing too many tools on his belt.


Is that the best answer that you can come up with?


Yeah, because it makes the code unreadable. My enter key works perfectly
and
I use it all the time.

You think:

Dim i As Integer = 10

Is unreadable? Wow.

Yes I do. When scanning thru hundreds of lines of code, there should be a
declarations section, an initialization section and a "working" section.
Anything else is... well... spaghetti code, at best.


Well, again - it's something if you don't like it you don't have to use it.

Dim i As Integer : I = 10 'is perfectly valid code in VB3,4,5,6 but no
one
uses that syntax because it's unreadable and (or should I say AndAlso)
leads
to bugs.

Because that syntax sucks. The new syntax, is cleaner, highly readable
and
IMHO, more clearly convey's the intent of the author - thereby leading to
less bugs.

That's the key right there.... "by the author"... the author can read it...
right now, that is. In 5 years? A different developer? Maybe, maybe not.


Did I say anything about reading by the author? I think my statements were
clearly intended to reflect the reading of the code by others...

While I'm at it, this "+=" and similar crap they've added to make C
programmers more comfortable. What a mess that is. I can't believe people
would rather save 2 freaking keystrokes than have easy to read code...
but,
I guess when you're in dotNet, every keystroke you can save counts,
right?


Again, you don't like it - don't use it, but don't try to force your
strange
sesne of readability on others.

What ever Mr C programmer.


Yes, on occasion - not as much anymore though. I do, however, do almost 100%
of my day to day coding in C#. So, yes I do like C-style syntax. I might
come back to VB if they ever make it case senstive :)


Again, a valid option. Hope it works for you, when the rest of the world
moves on to distributed systems and 64-bit apps....

Have fun... have you seen the poor excuses for a 64 bit OS? I've had 64 bit
CPUs since they were released... *still* no drivers for most hardware. 128
bit will be available before vendors ever get around to writing 64 bit
drivers.... this is because *they too* don't like anyone to tell them they
need to throw all of their previous work in the trash.


I agree, on the consumer side, the uptake of 64-bit has been slow. I don't
expect it to speed up for quite sometime. But, I think it's a little
different on the server side....


Your oppinion.

Mine and about 5 million others, yep.

Goody for them.

Well... that says a lot. *you're* right and 5 million others are wrong.
That's kinda what I figured. Thanks for clearing that up.


I'm not sure where you even get these numbers... Do you know how many .net
developers there are? 1 million? 2 million? I don't know - it's never really
concerned me. I'm making more money and having more fun then I ever did with
VB.CLASSIC :)


Set theButton = buttons(btnIndex)


Oh yea, Set. Another one of those idiotic VB.CLASSIC'isms, introduced as
a
bandaid to the whole default propety mess. You know, the feature that
most
proffesionals and MVP's discouraged people from using for years.

Yep... default properties are a source of confusion and shouldn't be
encouraged... look what MS did to "Label1.Caption ="... changed that to
"Label1.Text" while 3rd party vendors continued to use .Caption... who's
right? Why the change in the first place?


You don't need set in VB.NET - that mess has been cleaned up.


Check these groups. How many people say they've set their app for 2.0 but
the installation forces them to install 3.5?

Because they screwed up their installer. What does that have to do with
.NET?

Well... isn't "XCopy Deployment" and that "Click Once" junk part of the .Net
sales pitch?


Yes... And it often works just fine. But, again - nothing is perfect :)

If you're having problems with Binary Compatibility and DLL Hell after
all
these years, I'm very sorry. Most of us have figured out how to deal with
those problems.


Just as most of us have figured out how to deal with framework
installations... But, it didn't stop you from bringing that up, so I
thought
I'd just point out one of the flaws in VB6 installations. Nothing is
perfect.

Now, that's something we can all agree on... nothing's perfect.

Yes, just as your statements were your opinion... It's just that mine are
more grounded in reality and the current market - but, I guess that's what
comes of not shackling myself to a product that's useful lifetime expired
some
time in the last decade.

That "expired" stuff may be true where you work.. but, not here.


To bad... Is that why your so angry? Do you feel left out?

A toy... yep. One that helped MS "rule the world" in the 90's. btw, try
pasting a block of text in anything resembling an immediate window...
what
do you see? What ever it is, it's not what you pasted... now try
selecting
that block and pasting into the code window... didn't work at all, you
say?
Didn't think so.


What are you talking about?

There's a key called Ctrl on your keyboard. There's also a "C" and a "V"

A) Go to your code window
B) Select a block of text. fyi, a "Block" is generally 2 or more lines of
text, separated by CR/LF
C) Copy that block to the clipboard by holding down the key called "Ctrl"
and pressing "C"
D) Find the immediate window
E) Paste that block into the window by holding down the key called "Ctrl"
and pressing "V"

Is it still a block? Unchanged? Didn't think so...

Now, do the reverse

A) Go to your immediate window
B) Select a block of text. fyi, a "Block" is generally 2 or more lines of
text, separated by CR/LF
C) Copy that block to the clipboard by holding down the key called "Ctrl"
and pressing "C"
D) Find the code window
E) Paste that block into the window by holding down the key called "Ctrl"
and pressing "V"

Is it still a block? Unchanged? Didn't think so... in fact, it doesn't work
at all.


Let me rephrase, mr. snotty.... What is the point?

And no it doesn't have single procedure view. I'm sorry that you don't
like
that - but, you know what - I hate single procedure view. But, I'm sure
if
enough people requested it, it would have been added by now... Wait,
maybe
I'm not alone in hating single procedure view.

That's where you're wrong. Plenty of people asked for it... including
Microsoft Employees. How long would it have taken to implement? 30 minutes?
Do they care? No.


FSVO, Plenty... Apparently, "Plenty" wasn't enough to justify the
cost/development time - which I assure you is greater the 30 minutes.


Thanks for that. I appreciate that you've allowed me to continue to work
in
VB6... what happened when Vista was released? Oh yeah... people were
forced
to throw their pre-2005 dotNet stuff away...

No they weren't.... You sure like to exagerate. The frameworks, are
supported under Vista - it's the IDE's that aren't supported. Big
difference.

I agree... big difference... especially when it's the IDE you're paying for,
when you shell out your money.

Upgrade or continue to develop on XP - test on vista. Is the VB6 ide
supported on Vista? 2008 server?



Wasn't Vista supposed to be "The dotNet OS"?... yeah, 2% dotNet, if that.


There was some talk of that in early beta's. Didn't happen. What
difference
does it make. Vista/2008 ship with the 3.0 framework.

Some talk <g> LOL... that was the entire sales pitch... some talk... funny.

It was major pitch at the time, and I was a bit disappointed that it didn't
materialize...

--
Tom Shelton
.

Relevant Pages

  • Re: Conversion Problem
    ... That will take you to the help for that control, ... TextChanged event of a combobox and a textbox in VB6? ... I'd just point out one of the flaws in VB6 installations. ... pasting a block of text in anything resembling an immediate window... ...
    (microsoft.public.dotnet.languages.vb)
  • Re: can shell tell an exe to close
    ... With VB6 and Vista I use this shell to start this pgm.exe ... How would I use Shell to close pgm.exe when it it running. ... You can then close the window via numerous ways ...
    (microsoft.public.vb.winapi)
  • Re: can shell tell an exe to close
    ... With VB6 and Vista I use this shell to start this pgm.exe ... How would I use Shell to close pgm.exe when it it running. ... You can then close the window via numerous ways. ...
    (microsoft.public.vb.winapi)
  • Re: loosing messages leakes my app...
    ... It posts messages to a window, ... why don't you always use PostMessage? ... threads rely on the control, then you should not destroy the control before the ... POSSIBLY know the unique target window for which this is intended. ...
    (microsoft.public.vc.mfc)