Hi, I have noticed the following behavior for pre-selected values in the function package GUI and have some questions or maybe suggestions: * If a list argument doesn't have a defined default, gretl seems to remember the last choice, which is very nice! Or is it merely the list that was defined first? In any case I'm wondering whether it would be possible to apply also this "memory" to list arguments _with_ defaults. The default is IMHO intended to save typing in scripts, not to reset your specification in the GUI every time. Something like the rule: If there is a last saved spec. for the datafile, use it. If not, use the default, if there is one. (But of course I understand if it's too problematic to separate the GUI logic from the console use.) * Same thing for other parameters; would it be possible to remember them? I'm not sure what the logic is that gretl currently uses for the preset values for example of matrix arguments that don't have a defined default. The "oldest" in the session? * What I find potentially dangerous is that gretl fills in some existing object for example for a _return_ matrix. (Again, the oldest existing return matrix in the session?) The default here should be empty IMHO. * And something a little different: For matrix parameters, there is a "new" button, while for list parameters, there is a "more" button. (I know I'm partly responsible for that myself.) I would suggest some unification: Either enable matrix editing from within the package GUI like with lists, replacing "new" by "more" for matrices. Or _disable_ list editing from within the package GUI and implement that in gretl in general. (Of course I would favor the last option, but since I am not the one doing the work...) Thanks for reading until the end ;-) -sven