9:58 p.m.
Dear Gretl Team,
Today a colleague asked me where she could find the buttons "cut" and
"redo"
in the script editor window.
I think it would be nice to have these buttons. What do you think?
Um abraço,
*Henrique C. de Andrade*
Doutorando em Economia Aplicada
Universidade Federal do Rio Grande do Sul
www.ufrgs.br/ppge
10:25 p.m.
Henrique,
Today a colleague asked me where she could find the buttons
"cut" and "redo" in the script editor window.
I think it would be nice to have these buttons. What do you think?
You can do ctrl-x (cut), ctrl-v (paste) and ctrl-z (undo), at least on windows. I
personally prefer doing keyboard commands to mouse-clicks, so these work fine for me in
the majority of cases. That said, I for one don't have much of an opinion on the extra
buttons.
PS
10:52 p.m.
Em 30 de julho de 2011 Peter <psummers(a)highpoint.edu> escreveu
Henrique,
>Today a colleague asked me where she could find the buttons "cut" and
"redo" in the script editor window.
>I think it would be nice to have these buttons. What do you think?
You can do ctrl-x (cut), ctrl-v (paste) and ctrl-z (undo), at least on
windows. I personally prefer doing keyboard commands to mouse-clicks, so
these work fine for me in the majority of cases. That said, I for one don't
have much of an opinion on the extra buttons.
Dear Peter, thanks for your answer!
I know about the keyboard shortcuts, but there are some occasions that the
buttons could help a lot.
The first one is related to Gretl for Mac. The keyboard shortcuts for native
applications are command+x, command+v, etc. while X11 applications (like
Gretl) use control instead of command. This is a little bit annoying. With
the buttons we don't have this problem.
The second argument is one of the most important feature of Gretl: "Ease of
use". As incredible as it may seem, there are people that doesn't know
keyboard shortcuts.
Best regards and thanks again,
*Henrique C. de Andrade*
Doutorando em Economia Aplicada
Universidade Federal do Rio Grande do Sul
www.ufrgs.br/ppge
2:50 p.m.
On Sat, Jul 30, 2011 at 5:58 PM, Henrique Andrade
<henrique.coelho(a)gmail.com> wrote:
Dear Gretl Team,
Today a colleague asked me where she could find the buttons "cut" and
"redo"
in the script editor window.
I think it would be nice to have these buttons. What do you think?
They're now added in CVS.
Allin
6:23 a.m.
Sorry for hijacking an existing thread, but I thought it's not worth
starting a new one.
Sometimes a tool to forcibly terminate a running script would come very
handy, too. Maybe a combined "Start/Stop" button or something alike.
Regards,
Vitalie Ciubotaru
On 08/01/2011 11:50 PM, Cottrell, Allin wrote:
On Sat, Jul 30, 2011 at 5:58 PM, Henrique Andrade
<henrique.coelho(a)gmail.com> wrote:
> Dear Gretl Team,
>
> Today a colleague asked me where she could find the buttons "cut" and
"redo"
> in the script editor window.
>
> I think it would be nice to have these buttons. What do you think?
They're now added in CVS.
Allin
12:28 p.m.
<snip>
Sometimes a tool to forcibly terminate a running script would come
very
handy, too. Maybe a combined "Start/Stop" button or something alike.
I found myself looking for the "stop" button just yesterday ;-).
As long as we're on the subject, would it be possible to add a facility to
increase/decrease the indenting on a block of code? I like gretl's semi-automatic
"smart indenting", but there are times (eg, creating an outer loop around an
existing block of code) that it doesn't work.
FWIW,
PS
On 08/01/2011 11:50 PM, Cottrell, Allin wrote:
On Sat, Jul 30, 2011 at 5:58 PM, Henrique Andrade
<henrique.coelho(a)gmail.com> wrote:
> Dear Gretl Team,
>
> Today a colleague asked me where she could find the buttons "cut" and
"redo"
> in the script editor window.
>
> I think it would be nice to have these buttons. What do you think?
They're now added in CVS.
Allin
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users
2:04 a.m.
On Tue, 2 Aug 2011, Summers, Peter wrote:
> Sometimes a tool to forcibly terminate a running script would
come very
handy, too. Maybe a combined "Start/Stop" button or something alike.
I found myself looking for the "stop" button just yesterday ;-).
From a programmer's point of view, the question is: where should
we
stick the handlers for aborting a script? Is everyone who's putting
forward this idea thinking in terms of breaking out of a gretl loop?
Notice that you have a "break" command for loops, so with some
foresight you can arrange a conditional breakout if things are not
going well.
Allin Cottrell
7:53 a.m.
On Mon, 2011-08-08 at 22:04 -0400, Allin Cottrell wrote:
On Tue, 2 Aug 2011, Summers, Peter wrote:
>> Sometimes a tool to forcibly terminate a running script would come very
> handy, too. Maybe a combined "Start/Stop" button or something alike.
>
> I found myself looking for the "stop" button just yesterday ;-).
>From a programmer's point of view, the question is: where should we
stick the handlers for aborting a script? Is everyone who's putting
forward this idea thinking in terms of breaking out of a gretl loop?
Notice that you have a "break" command for loops, so with some
foresight you can arrange a conditional breakout if things are not
going well.
Personally, I am not thinking of breaking out of faulty loops.
In one of my scripts I had a lot of time-consuming loops. When I wanted
to check changes in my script not directly related to the loops, I
usually commented them out, but occasionally I forgot. A stop-button
would have been useful. "break" obviously doesn't help me in that case.
In general, I think a stop-button is useful in cases where you notice
that you have lacked foresight ;-)
Britta
1:50 p.m.
On Tue, 9 Aug 2011, amaryl wrote:
On Mon, 2011-08-08 at 22:04 -0400, Allin Cottrell wrote:
> On Tue, 2 Aug 2011, Summers, Peter wrote:
>
>>> Sometimes a tool to forcibly terminate a running script would come very
>> handy, too. Maybe a combined "Start/Stop" button or something alike.
>>
>> I found myself looking for the "stop" button just yesterday ;-).
>
>> From a programmer's point of view, the question is: where should we
> stick the handlers for aborting a script? Is everyone who's putting
> forward this idea thinking in terms of breaking out of a gretl loop?
>
> Notice that you have a "break" command for loops, so with some
> foresight you can arrange a conditional breakout if things are not
> going well.
Personally, I am not thinking of breaking out of faulty loops.
In one of my scripts I had a lot of time-consuming loops. When I wanted
to check changes in my script not directly related to the loops, I
usually commented them out, but occasionally I forgot. A stop-button
would have been useful. "break" obviously doesn't help me in that case.
In general, I think a stop-button is useful in cases where you notice
that you have lacked foresight ;-)
The problem with a "break" button is that the program has to constantly
check if the button has been pressed and, if so, take the appropriate
action. This slows down execution and I personally don't like it very
much. This said, it has happened to me to long for a break button, like
for example when you run some estimation command that is known to take
minutes and you realise just after having pressed "OK" that you forgot to
add a variable or so.
What we may want to do is think about some mechanism for interrupting the
current command in the GUI client, and advise users to use the unstoppable
might of the CLI client if performance is of paramount importance.
Thoughts?
Riccardo (Jack) Lucchetti
Dipartimento di Economia
Università Politecnica delle Marche
r.lucchetti(a)univpm.it
http://www.econ.univpm.it/lucchetti
2:08 a.m.
On Wed, 17 Aug 2011, Riccardo (Jack) Lucchetti wrote:
On Tue, 9 Aug 2011, amaryl wrote:
> On Mon, 2011-08-08 at 22:04 -0400, Allin Cottrell wrote:
>> On Tue, 2 Aug 2011, Summers, Peter wrote:
>>
>>>> Sometimes a tool to forcibly terminate a running script would come very
>>> handy, too. Maybe a combined "Start/Stop" button or something
alike.
>>>
>>> I found myself looking for the "stop" button just yesterday ;-).
>>
>>> From a programmer's point of view, the question is: where should we
>> stick the handlers for aborting a script? Is everyone who's putting
>> forward this idea thinking in terms of breaking out of a gretl loop?
>>
>> Notice that you have a "break" command for loops, so with some
>> foresight you can arrange a conditional breakout if things are not
>> going well.
>
> Personally, I am not thinking of breaking out of faulty loops.
> In one of my scripts I had a lot of time-consuming loops. When I wanted
> to check changes in my script not directly related to the loops, I
> usually commented them out, but occasionally I forgot. A stop-button
> would have been useful. "break" obviously doesn't help me in that
case.
>
> In general, I think a stop-button is useful in cases where you notice
> that you have lacked foresight ;-)
The problem with a "break" button is that the program has to constantly check
if the button has been pressed and, if so, take the appropriate action. This
slows down execution and I personally don't like it very much. This said, it
has happened to me to long for a break button, like for example when you run
some estimation command that is known to take minutes and you realise just
after having pressed "OK" that you forgot to add a variable or so.
What we may want to do is think about some mechanism for interrupting the
current command in the GUI client, and advise users to use the unstoppable
might of the CLI client if performance is of paramount importance. Thoughts?
Stopping gretlcli is no problem: good old Ctrl-C. I agree that one
might sometimes want a way of stopping execution in the GUI (though
there's xkill and equivalents).
In CVS I've added a Stop button to the toolbar in the script editor
window. This is checked by a callback at the top of the main
command-line execution function in libgretl. So script execution
should halt, if this button is clicked, as soon as the next line
comes up for execution.
It's not so easy to stop execution of a time-consuming built-in
command. That would require peppering the functions within libgretl
with calls to check the stop button status. However, we could also
add a stop button to the dialog boxes used to fire up "addons" and
other function packages, since these are script-based and would be
caught by the command-line blocker.
Allin Cottrell
12:52 p.m.
On Wed, 17 Aug 2011, Allin Cottrell wrote:
In CVS I've added a Stop button to the toolbar in the script
editor window.
This is checked by a callback at the top of the main command-line execution
function in libgretl. So script execution should halt, if this button is
clicked, as soon as the next line comes up for execution.
Oof, this was buggy (guaranteed crash whenever you invoke a
user-defined function in the gretl GUI) so it's reverted for
now. But I think I see how to do it right so I'll commit an
updated version later today.
Allin
4635
days inactive
4654
days old
10 comments
7 participants
participants (7)
-
Allin Cottrell -
amaryl -
Cottrell, Allin
-
Henrique Andrade -
Riccardo (Jack) Lucchetti -
Summers, Peter -
Vitalie Ciubotaru