Long time bug in VB6

>
On a form where you have many controls hold down your Ctrl key and select
a large number of them at random. Now keep the Ctrl key down and click a
control again to unselect it. Your VB6 IDE will crash.
>
It's annoying because you'll be selecting sometimes small labels and
you'll accidentally select the wrong one or what's behind it. I've had
this problem in spite of every service pack.

I've always found this extremely annoying, anyone else?
>
On a form where you have many controls hold down your Ctrl key and select
a large number of them at random. Now keep the Ctrl key down and click a
control again to unselect it. Your VB6 IDE will crash.
>
It's annoying because you'll be selecting sometimes small labels and
you'll accidentally select the wrong one or what's behind it. I've had
this problem in spite of every service pack.

>I've always found this extremely annoying, anyone else?
>
>On a form where you have many controls hold down your Ctrl key and select a
>large number of them at random. Now keep the Ctrl key down and click a
>control again to unselect it. Your VB6 IDE will crash.
>
>It's annoying because you'll be selecting sometimes small labels and you'll
>accidentally select the wrong one or what's behind it. I've had this problem
>in spite of every service pack.
>

"will_456" <wi;ll_456@bigpond.com>'s wild thoughts were
released on Thu, 01 Mar 2007 19:55:47 GMT bearing the
following fruit:
>>
This bug was fixed in a SP, can't recall which one. But I
think and SP from 3-6 should do.
>
>

Found it thanks:
>
http://support.microsoft.com/kb/190039/en-us
>
Apparently all I need to do is open the properties windw first and it
won't crash.
>
Hm-m-m wish I'd known that before adding 20 controls to a form, lining
them up and getting them looking just right before selecting them all and
trying to select them all so I can set a common property (without saving
first). Make one mistake selecting so need to deselect one control and
Crash !!! - start again with a blank form. I've done this so many times
Arg-h-h-h-h !!!!!!
>
>
>
"Jan Hyde" <StellaDrinker@REMOVE.ME.uboot.comwrote in message
news:pnpfu257bqk0fb5fmrc19srvpptb36a7b5@4ax.com...>
>

>I've always found this extremely annoying, anyone else?
>
>On a form where you have many controls hold down your Ctrl key and select a
>large number of them at random. Now keep the Ctrl key down and click a
>control again to unselect it. Your VB6 IDE will crash.
>
>It's annoying because you'll be selecting sometimes small labels and you'll
>accidentally select the wrong one or what's behind it. I've had this
>problem
>in spite of every service pack.
>

Still can't reproduce the problem, even following the steps in the KB
article. And that's on a box with vb6 and NO service pack installed.
>

Still can't reproduce the problem, even following the steps in the KB
article. And that's on a box with vb6 and NO service pack installed.
>

I've always found this extremely annoying, anyone else?
>
On a form where you have many controls hold down your Ctrl key
and select a large number of them at random. Now keep the Ctrl
key down and click a control again to unselect it. Your VB6 IDE
will crash.

>Still can't reproduce the problem, even following the steps in the KB
>article. And that's on a box with vb6 and NO service pack installed.

>
"will_456" <wi;ll_456@bigpond.comskrev i en meddelelse
news:7dGFh.5564$8U4.4891@news-server.bigpond.net.au...>
Never seen that problem.
>
And a "large number of control" does - in my ears - sound like a
design-problem ;-)
>
>
>

1. New project - one form
2. Add 4 buttons
3. Close properties window
4. Hold down Ctrl and click on each one until 4 selected
5. Click one again to deselect
>
Houston - we have a problem !!!! ... well on my system anyway (and the
last three computers I've owned)

>
>Yep! That procedure (and using the Shift key instead of the Control key)
>crashes my copy of VB also. I guess I never saw this problem before because
>I never close the Properties window. Just out of curiosity, why would
>someone close the Properties window anyway?

>
Before I got a flat screen my eyes could only cope with
800x600 - Not a lot of screen real estate to work with.
>
I can see why there might be occasions where you need to
close things down.

>
>Maybe if you were using the MDI interface; but if things were that crowded,
>switching to the SDI interface would have solved that... no need to turn
>individual "tool" windows off as the Form, when selected, would sit above
>them.

"Rick Rothstein \(MVP - VB\)">
True, but as we know, some people here see the SDI interface
as evil ;-)

>Jan Hyde wrote:>
>But a necessity if you want to (sensibly) use multiple monitors :)

Dean Earley <dean.earley@icode.co.uk>'s wild thoughts were
released on Tue, 06 Mar 2007 09:36:15 +0000 bearing the
following fruit:
>>
I've never used multiple monitors, can you answer me this.
My graphics card only has one output so I can only plug in
one monitor, is there any way I can use the on board
graphics card to run the second monitor?
>

I've never used multiple monitors, can you answer me this.
My graphics card only has one output so I can only plug in
one monitor, is there any way I can use the on board
graphics card to run the second monitor?

>Jan Hyde wrote:>
>It depends on the motherboard.
>
>Some see an extra graphics card and completely disable the on board,
>some have an option to enable it as well.
>
>Failing that, a Matrox or NVidia dual head card as Raoul suggested.

>
Maybe if you were using the MDI interface; but if things were that
crowded, switching to the SDI interface would have solved that... no need
to turn individual "tool" windows off as the Form, when selected, would
sit above them.
>
Rick
>