It seems that there was a little bit of a misunderstanding about this
change when we discussed it on the mailing list.
Option 1:
Remove refresh buttons from all debugger views (this is what I thought
we were doing).
Option 2:
Remove the refresh button from Debug view only (this is what Navid
requested when this thread opened).
Option 3:
Link the refresh buttons to the Debug Update Modes action set (so that
they appear only when the action set is active). This is what my
original intention for this feature was IMO a reasonable compromise.
If you have a strong opinion, please weigh in in bug 299834.
Cheers,
Pawel
Marc Khouzam wrote:
+1 on what John said below.
My main argument is for giving the user the general ability to refresh
debugger views on demand, as I feel the need for it was being
questioned. I think it's a valid need and a feature CDT should provide.
I think it's useful to have that control on a per-view granularity, but
I don't feel terribly strongly about that. If it were made optional,
that seems fine to me; and if the per-view control wasn't there, oh
well. But what I do feel strongly about is that the capability be there
at a minimum as a global action (refresh all views) that is by default
hidden. When I first responded to this thread, I believed the action in
the Debug view refreshed all views.
At 11:16 AM 1/17/2010, Doug Schaefer wrote:
On Sun, Jan 17, 2010
at 9:13 AM, Daniel Jacobowitz <dan@xxxxxxxxxxxxxxxx> wrote:
- On Sat, Jan 16, 2010 at 03:53:06PM -0600, John Cortell
wrote:
- > "basic debugging" category. Embedded debuggers fall
into the "advanced"
- > one. My guess is CDT is used more in the embedded
world than the desktop
- > one.
- I really have to disagree. There are advanced and basic
users in both
- embedded and desktop environments, and supporting the basic
users is
- very important. The more buttons you give a new user the
less they
- like your product in my experience.
+1 My pet peeve is UIs that are overloaded with buttons. It's very
intimidating for new users. Buttons should only be provided for the
most basic operations that are used most often. Everything else should
be in a menu. And even then it should only be shown when and where
applicable.
- If the main - not only, but main - way to get in trouble is
using the
- debug console, then maybe the debug console is where the
action should
- be? Even if it's not only useful for the console, that
seems like a
- reasonable place for it.
- --
- Daniel Jacobowitz
- CodeSourcery
- _______________________________________________
- cdt-dev mailing list
- cdt-dev@xxxxxxxxxxx
- https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|