Am 01.05.2019 um 04:53 schrieb Fred Engst:
Here are the details:
1. After a script is opened, or a new one is
created, if I save it with a new name, the list of windows that are
open when I click on the top right corner of gretl still shows the
old name, which can cause confusion.
Hm, I only see "script editor" there anyway, but perhaps that has to do
with tabs activated for me. Are you using the script editor in a tabbed way?
———————————————————————————————————
2. With time series data, if the names of two variables that are very
long, close to the 31 character limit, and they differ only at the
last one or two characters, then a regression of the two with lagged
variables will clash with gretl auto created shortened
abbreviations.
Certainly a limitation, not sure if it counts as a bug. As the person
who called for the extension of variable names years ago (from a much
shorter limit) I see what you mean, but I guess it's OK to ask the user
to stay below 28 or 25 characters or so.
OTOH when series are auto-imported (dbnomics!) and the long names come
from somewhere else, the issue may be more problematic.
I then renamed it down to a shorter names rename 2
o12345678901234567890123456 rename 1 o1234567890123456789012345678
Listing 3 variables: 0) const 1) o1234567890123456789012345678 2)
o12345678901234567890123456
? ols 1 0 o1234567890123456789012345678(-1 to -4) \
o12345678901234567890123456(-1 to -4) variable 3 duplicated in the
command list.
Error executing script: halting
Those names are still very long, not sure what your point is here, given
the limitation above.
———————————————————————————————————
3. Sometimes the lagged variable don’t show up in the main window, so
that I can’t delete those lagged ones, other then using the list
command and then invoke the delete varlist command.
My guess is that they're "hidden" below their parent variable, watch out
for a little arrow or triangle symbol in the variable list. When you
click on it the lags are shown.
———————————————————————————————————
4. When I’m working on a .gretl file, if I choose to see the command
log, an error would show up.
Confirmed (I think). My guess is that it has to do with gretl's
"philosophy": Either use the command log to record your actions, or use
a session-file based approach (.gretl), but not both. But first this is
a bit of speculation, and secondly even then it should be caught (or
disabled).
———————————————————————————————————
5. Once I open the icon view, if I double click on the summary icon,
often I see nothing is happening. Once I move the icon view to
somewhere else, there is the dialog box asking for options to
summarize. It was hidden behind the icon view window the whole time.
Cannot confirm, but I believe you ;-)
Here we need more info about your setup, OS, version etc.
Thanks for the reports
sven