[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-debug-dev] Default step filtering
|
I agree.
- Jared
Joe_Szurszewski@xxxxxxx
Sent by: jdt-debug-dev-admin@xxxxxxxxxxx
11/15/2001 12:42 PM
Please respond to jdt-debug-dev
To: jdt-debug-dev@xxxxxxxxxxx
cc:
Subject: Re: [jdt-debug-dev] Default step filtering
While we're on the subject, should the defaults for "filter synthetic
methods" & "filter static initializers" also be off? To be consistent, I
would think so . . .
Joe
Jed_Anderson@xxxxxxx
Sent by: jdt-debug-dev-admin@xxxxxxxxxxx
11/15/01 11:00 AM
Please respond to jdt-debug-dev
To: jdt-debug-dev@xxxxxxxxxxx
cc:
Subject: Re: [jdt-debug-dev] Default step filtering
Agreed.
jkca
Jared_Burns@xxxxxxx
Sent by: To:
jdt-debug-dev@xxxxxxxxxxx
jdt-debug-dev-admin@e cc:
clipse.org Subject: [jdt-debug-dev]
Default step filtering
11/15/2001 09:58 AM
Please respond to
jdt-debug-dev
We've had a number of "bug reports" on the Corner that turned out to be
cases of Step Filtering blind-siding the user. The step filtering behavior
is neither expected nor intuitive to a new
user; thus it should not be on by default. If a developer wants to avoid
stepping into certain libraries, they'll go looking through the
preferences for a way to filter. If you're hit with this behavior without
asking for it, there's no reason to suspect that it's the result of a
preference somewhere.
- Jared
_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-debug-dev
_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-debug-dev
