From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: feature suggestion
Date: Mon, 08 Oct 2001 01:27:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0112041135120.18-100000@makita.cygnus.com> (raw)
In-Reply-To: <87adwz367n.fsf@creche.redhat.com>
On 3 Dec 2001, Tom Tromey wrote:
> It would be helpful to me if the (mouse) cursor changed to a watch
> over the console window when the inferior is executing.
Try this patch. If it works, I'll check something in.
Keith
Index: library/console.itb
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/console.itb,v
retrieving revision 1.14
diff -u -p -r1.14 console.itb
--- library/console.itb 2001/10/17 20:30:29 1.14
+++ library/console.itb 2001/12/04 19:36:22
@@ -205,6 +205,7 @@ body Console::_build_win {} {
body Console::idle {event} {
set _running 0
+ $_top configure -cursor {}
}
# ------------------------------------------------------------------
@@ -212,6 +213,7 @@ body Console::idle {event} {
# ------------------------------------------------------------------
body Console::busy {event} {
set _running 1
+ $_top configure -cursor watch
}
# ------------------------------------------------------------------
WARNING: multiple messages have this Message-ID
From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: feature suggestion
Date: Tue, 04 Dec 2001 11:36:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0112041135120.18-100000@makita.cygnus.com> (raw)
Message-ID: <20011204113600.YdhGcqdYnNsE5V3wK2bqGawulezdTn338nbRxG58G3A@z> (raw)
In-Reply-To: <87adwz367n.fsf@creche.redhat.com>
On 3 Dec 2001, Tom Tromey wrote:
> It would be helpful to me if the (mouse) cursor changed to a watch
> over the console window when the inferior is executing.
Try this patch. If it works, I'll check something in.
Keith
Index: library/console.itb
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/console.itb,v
retrieving revision 1.14
diff -u -p -r1.14 console.itb
--- library/console.itb 2001/10/17 20:30:29 1.14
+++ library/console.itb 2001/12/04 19:36:22
@@ -205,6 +205,7 @@ body Console::_build_win {} {
body Console::idle {event} {
set _running 0
+ $_top configure -cursor {}
}
# ------------------------------------------------------------------
@@ -212,6 +213,7 @@ body Console::idle {event} {
# ------------------------------------------------------------------
body Console::busy {event} {
set _running 1
+ $_top configure -cursor watch
}
# ------------------------------------------------------------------
next prev parent reply other threads:[~2001-12-04 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 13:22 Tom Tromey
2001-10-08 1:27 ` Keith Seitz [this message]
2001-10-08 14:34 ` Tom Tromey
2001-10-09 8:16 ` Keith Seitz
2001-12-05 9:08 ` Keith Seitz
2001-12-04 20:27 ` Tom Tromey
2001-12-04 11:36 ` Keith Seitz
2001-12-03 21:24 ` Tom Tromey
2001-10-16 10:16 Tom Tromey
2001-10-16 10:22 ` Keith Seitz
2001-10-16 10:30 ` Tom Tromey
2001-10-16 10:35 ` Keith Seitz
2001-12-21 13:37 ` Keith Seitz
2001-12-21 13:34 ` Tom Tromey
2001-12-20 22:19 ` Keith Seitz
2001-12-20 21:48 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.33.0112041135120.18-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).