Re: App Shutdown Slooooow

"Karl E. Peterson" <karl@xxxxxxxx> wrote in message
news:u0oFqw2hHHA.2368@xxxxxxxxxxxxxxxxxxxxxxx
I won't say *only* a complete idiot would care about such trivium, but my
life's got quite enough intrique already to even begin to care about the
likes of that. If the form's too small to resize controls properly, who
the hell cares? It's visible. I'd rather put my efforts into something
that actually matters. This sort of anal obsession is best described as
"pounding sand."

It's may be trivial but so is the solution. It takes 3 characters are 2
seconds to solve the problem and then the resize code functions correctly
all the way to zero. I really don't see Form_Resize as anything special, if
you don't put On Error Resume Next anywhere else then I don't see any
special reason to put it here.

I don't use "Break On All Errors."

Seems to be a sure sign of weakness to me. <sniff>

This is something you've failed to understand for many years and it's time I
explained why I use Break On All Errors most of the time.

We use an error addin that will give us specific details of the error
including the call stack and the exact line the error ocurred on. The
client/testers can then send this error report to us which makes fixing bugs
very easy. The behaviour is pretty much the same as what dotnet does (I know
you don't like dotnet but the error handling is top notch). This addin has
been absolutely fantastic and was so successful it was adopted across all
vb6 projects in the company without me even mentioning it to anyone.

Anyway, if we don't have Break On All Errors set then this addin activates
telling us where the error ocurred. Then you have to match up the text to
find the line that it ocurred on. Then you've got to get back to that line
if you want to check any variable values. It's much easier just to have it
break on all errors and have it break on the correct line. This means that
programmers need to program in such a way as to avoid having errors raised.
This isn't that difficult as there's only a handful of cases which need to
be handled and we've found ways to handle them. For example, getting an item
out of a collection that may not exist.

You'll probably think this is a bad way to program but this has been very
successful in this company and does work VERY well. It's so similar to the
way dot net works that I joke at work that MS stole my idea. Many other
programmers on these groups use similar addins. The end result is that
having On Error Resume Next in Form_Resize would turn out to be a complete
PITA.

Michael


.

Relevant Pages

  • Re: Intro to Programming w/ Machine Language
    ... I don't really care if vi is optimized for my AMD ... WIth certain obvious exceptions for Java, ... Most C programmers I know use it for "close to bare ... I don't think they have a "social responsibility" to write, ...
    (comp.programming)
  • Re: Intro to Programming w/ Machine Language
    ... I don't really care if vi is optimized for my AMD ... WIth certain obvious exceptions for Java, ... Most C programmers I know use it for "close to bare ... I don't think they have a "social responsibility" to write, ...
    (alt.lang.asm)
  • Re: Visual SourceSafe considered harmful
    ... > applications I have worked with in the past as a fulltime employee or as ... an extension of your contract period. ... You will find that some programmers are interested in programming, ... Those that are really into this stuff, care about it, even if their ...
    (comp.programming)
  • Re: ADA Popularity Discussion Request
    ... many programmers (and even many software engineers) do not ... care much abour military use of their software, but they do care much about ... And this is exactly the reputation of the military and the weapon makers ...
    (comp.lang.ada)
  • Re: addin/addon?
    ... Looks a bit overkill but might worth (better independance and AFAIK also ... takes care of running the addin at a lower trust level if you want). ...
    (microsoft.public.dotnet.languages.csharp)