"will_456" <wi;EMAIL REMOVED> skrev i en meddelelse
news:7dGFh.5564$EMAIL REMOVED...
> 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.

Never seen that problem.

And a "large number of control" does - in my ears - sound like a
design-problem ;-)

"Randy Birch" <EMAIL REMOVED>'s wild thoughts were
released on Sat, 3 Mar 2007 09:43:03 -0500 bearing the
following fruit:

>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.

It certainly has been a problem - it used to drive me crazy.
I've encountered the problem very rarely since SP3.

"preben nielsen" <EMAIL REMOVED> wrote in message
news:45ebb7cc$0$845$EMAIL REMOVED. ..
>
> "will_456" <wi;EMAIL REMOVED> skrev i en meddelelse
> news:7dGFh.5564$EMAIL REMOVED...
>> 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.
>
> Never seen that problem.
>
> And a "large number of control" does - in my ears - sound like a
> design-problem ;-)
>
>
>
Just tried it then:
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)

> Just tried it then:
> 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?

Rick

"Rick Rothstein \(MVP - VB\)"
<EMAIL REMOVED>'s wild thoughts were
released on Mon, 5 Mar 2007 05:34:45 -0500 bearing the
following fruit:

>> Just tried it then:
>> 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.

J

>> 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

"Rick Rothstein \(MVP - VB\)"
<EMAIL REMOVED>'s wild thoughts were
released on Mon, 5 Mar 2007 10:37:45 -0500 bearing the
following fruit:

>>> 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.

True, but as we know, some people here see the SDI interface
as evil ;-)

Jan Hyde wrote:
> "Rick Rothstein \(MVP - VB\)"
>>> 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.
>
> True, but as we know, some people here see the SDI interface
> as evil ;-)

But a necessity if you want to (sensibly) use multiple monitors

--
Dean Earley (EMAIL REMOVED)
i-Catcher Development Team

iCode Systems

Dean Earley <EMAIL REMOVED>'s wild thoughts were
released on Tue, 06 Mar 2007 09:36:15 +0000 bearing the
following fruit:

>Jan Hyde wrote:
>> "Rick Rothstein \(MVP - VB\)"
>>>> 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.
>>
>> True, but as we know, some people here see the SDI interface
>> as evil ;-)
>
>But a necessity if you want to (sensibly) use multiple monitors

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" <EMAIL REMOVED> wrote in message
news:EMAIL REMOVED...
> Dean Earley <EMAIL REMOVED>'s wild thoughts were
> released on Tue, 06 Mar 2007 09:36:15 +0000 bearing the
> following fruit:
>
>>Jan Hyde wrote:
>>> "Rick Rothstein \(MVP - VB\)"
>>>>> 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.
>>>
>>> True, but as we know, some people here see the SDI interface
>>> as evil ;-)
>>
>>But a necessity if you want to (sensibly) use multiple monitors
>
> 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?
>

You can connect it to something like Matrox Dualhead to go..
http://sewelldirect.com/DualHead2Go-Matrox.asp