Re: RFC: bind of Enter keys to all buttons

Re: RFC: bind of Enter keys to all buttons

[Syd Polk]

Fernando Nasser wrote:
> 
> Jim Ingham wrote:
> >
> > Also sprach Fernando Nasser:
> >
> > > Is there any thing that prevents us to do this?  Is someone aware of a button
> > > anywhere that shoud not execute its command when it is selected and we press
> > > one of the Enter keys?
> > >
> >
> > You really shouldn't do it this way, since this does not ensure that there
> > is UI indicating that the button in question IS the default button (usually
> > there is a little focus ring around the "default" button).  If you just make
> > it so that any button that has the focus will activate on return,
> 
> Yes, that is what someone asked for: return would activate the button with the
> foucus.  Presently a "sapace" does it.
> 

Return should activate the default button (normally the OK button).

The space bar invoking the button is stolen from Windows, but I see no
reason to change it. There is no point in having a default button if you
have to tab to it to invoke it.

> > then it is
> > too easy not to link the activation of the button to its correct appearance.
> 
> I am not sure if I understood that part...
> 
> > This should really be handled in a dialog class - which is where the default
> > buttons almost invariably show up.  Then you can set the default button OF
> > THE DIALOG, and ensure that you a) focus on it, b) give it the highlight
> > ring and c) activate it as you do above.
> >
> 
> I see, we are talking about two different things.  I am not meddling with the
> default button, it is done like you said and I would never change that.
> 
> I am just proposing to add a default handler for button events so that hitting
> Return or KP-Enter executes the -command
> Currently "space" does that and it is very strange.
> 
> What I was trying to do is a Class Binding (instead of a bind for every single
> button that we add around)...
> 
> But this does not seem to be very reliable.  It sometimes work, sometimes not, works
> for some windows and not others.  Looks like a bug to me.
> 
> --
> Fernando Nasser
> Red Hat - Toronto                       E-Mail:  fnasser@cygnus.com
> 2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
> Toronto, Ontario   M4P 2C9              Fax:  416-482-6299

Re: RFC: bind of Enter keys to all buttons

[Tom Tromey]

Fernando> P.S.: Is having the default button a "good thing"?

Yes.  Some dialogs are most easily filled out using keyboard
navigation.  It is annoying when enter doesn't accept the whole dialog
and move on.

For instance in gdbtk I find it annoying that hitting Enter when the
focus is in the Arguments entry field doesn't cause the dialog to go
away.

Tom

Create binary distribution.

[Leslie Newell]

Hi,
Downloading Cygwin and compiling Insight tends to be quite daunting to Gnu/Cygwin newbies (it was for me anyway!). I would like to
create a simple setup program with the binaries and support files to hopefully make life easier for others. What files do I need to
include to get Insight to run and how do I set up the paths?

My current setup is: host Cygwin(not sure about version), target h8300hms, latest snapshot of Insight(downloaded Friday).

Also is there any way of setting remote timeout to less than one second or the number of retries to less than 10? If a download
fails Insight can sit there for ages continually retrying each packet - I have had to resort to the three finger salute (Ctrl Alt
Del) a couple of times.


Thanks,
Les

Re: Create binary distribution.

[Keith Seitz]

Leslie Newell wrote:
> 
> Also is there any way of setting remote timeout to less than one second or
> the number of retries to less than 10? If a download fails Insight can sit
> there for ages continually retrying each packet - I have had to resort to
> the three finger salute (Ctrl Alt Del) a couple of times.

You can use the "remotetimeout" variable to change the delay time. When
I work on Cygwin, I always set it to 1: "set remotetimeout 1". There is
no interface for this, so you'll need to type this into the console
window (or put it in the init file: gdb.ini on windows, I think).

Keith

Re: Create binary distribution.

[Leslie Newell]

I have already set the timeout to 1. The problem is that if the target is not responding and I try to download a file, Insight will
keep retrying 10 times for each packet. Even with a 6K file this is a lot of retries.... I wonder if this could be considered a bug
because if a packet fails there is no point sending the rest of the file.

Les


> Leslie Newell wrote:
> >
> > Also is there any way of setting remote timeout to less than one second or
> > the number of retries to less than 10? If a download fails Insight can sit
> > there for ages continually retrying each packet - I have had to resort to
> > the three finger salute (Ctrl Alt Del) a couple of times.
>
> You can use the "remotetimeout" variable to change the delay time. When
> I work on Cygwin, I always set it to 1: "set remotetimeout 1". There is
> no interface for this, so you'll need to type this into the console
> window (or put it in the init file: gdb.ini on windows, I think).
>
> Keith
>

Re: Create binary distribution.

[Keith Seitz]

Leslie Newell wrote:
> 
> I have already set the timeout to 1. The problem is that if the target is not responding and I try to download a file, Insight will
> keep retrying 10 times for each packet. Even with a 6K file this is a lot of retries.... I wonder if this could be considered a bug
> because if a packet fails there is no point sending the rest of the file.

Ugh. That problem again. The whole download thing runs independently of
the GUI. You'll need to ping the gdb mailing list for resolution. :-(

Keith