On Sun, 2 Jul 2017, Sven Schreiber wrote:
I had a teaching session for forecasting with gretl in GUI style,
and I found the forecast result window a little un-intuitive. So I
think that window could use a menu bar, even though it might be a
very short bar.
First, it was unclear to me how I could save the forecast to a
series. A student pointed out (fortunately) that there's the "+"
button in the window which does just that. But I think if someone
like me who has been using Gretl for years doesn't get it, it's a
problem. (Please no jokes about my limited cleverness.) If there
had been a menu item "Save", it would have been obvious I think.
Well, I see what you mean, but I think it would too ugly to
supplement the existing toolbar with a (one-item) menu bar. Note
that all buttons on gretl toolbars have a tooltip, and this one
("+") reads "Add to dataset...". This button appears in several
windows: if anyone can suggest a more intuitive icon for it, I'm
listening. In general, one should mouse-over buttons whose purpose
is not immediately clear (though it's obviously better if the
purpose is immediately clear).
Secondly, how can I save the forecast standard errors from the
GUI? It seems it's impossible, although I know how to do it in a
script with $fcerr [...]
That's now enabled in git. If the forecast window shows standard
errors then the "+" button pops up a menu offering to save either
the forecast itself or the standard errors.
(BTW, it now occurs to me that "fcerr" sounds more like fc
errors,
i.e. y-\hat{y}, but it's probably too late to change that).
Not really too late: taking your point, I've now renamed that
accessor as $fcse. But the old $fcerr is still present as an alias.
Allin