|
Perhaps in your case it isn't useful. However, there are many times when
I'm in a program and have set a watch breakpoint and several other
breakpoints--sometimes even other watch breakpoints. I've found the
dialog to be helpful in these cases--I immediately know exactly why the
program stopped. There are times when my monitor view has too many
fields/variables being monitored to immediately see the watch which
triggered the break. Also, I work with some other developers who are
challenged enough by WDSC that it just might put them over the edge if the
dialog were gone. Maybe an option to suppress the dialog in specific
cases would make sense. Personally, I would rather see the development
efforts put into other areas of the product.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.