Re: Setting VB IDE to MDI permanently
- From: "SME" <smelchuri@xxxxxxxxxxx>
- Date: Thu, 20 Dec 2007 09:53:55 -0500
I don't agree fully.
Whether in milatary or in civil works, discipline only leads to success. And
for a coherent team work, conformance to the rules of the team is very
important.
Actually it is very convinient if you are debugging a program to see the GUI
also as you go through the code. It is more so if you are sending some
messages to another window. So that's how it got into it. But there are
times when it is less confusing if your code window is not a see-through.
That's why I said I don't agree fully with you.
ThanQ...
"Jeff Johnson" <i.get@xxxxxxxxxxx> wrote in message
news:13mkutcgs2ivr7a@xxxxxxxxxxxxxxxxxxxxx
"SME" <smelchuri@xxxxxxxxxxx> wrote in message
news:%23T1irdmQIHA.5264@xxxxxxxxxxxxxxxxxxxxxxx
They were doing it to enforce a common IDE among the team.
...and that common IDE was SDI. I think I would have left skid marks on my
way out the door.
Dear Conformance Nazis: let people work the way they want to work.
.
- Follow-Ups:
- Re: Setting VB IDE to MDI permanently
- From: Ken Halter
- Re: Setting VB IDE to MDI permanently
- References:
- Setting VB IDE to MDI permanently
- From: SME
- Re: Setting VB IDE to MDI permanently
- From: Ralph
- Re: Setting VB IDE to MDI permanently
- From: Ken Halter
- Re: Setting VB IDE to MDI permanently
- From: SME
- Re: Setting VB IDE to MDI permanently
- From: SME
- Re: Setting VB IDE to MDI permanently
- From: Jeff Johnson
- Setting VB IDE to MDI permanently
- Prev by Date: Re: Setting VB IDE to MDI permanently
- Next by Date: Horizontal ScrollBar+ PictureBox + Flickering (how to stop flickering?)
- Previous by thread: Re: Setting VB IDE to MDI permanently
- Next by thread: Re: Setting VB IDE to MDI permanently
- Index(es):