Allin Cottrell schrieb:
On Fri, 8 Jun 2007, Sven Schreiber wrote:
> I have noticed the following behavior for pre-selected values in
> the function package GUI and have some questions or maybe
I have to think about this some more. What happens now when we
come across a matrix or list argument in the function call GUI is
simply this: we see if we have any already-defined matrices/lists,
and if so we stick their names into a drop-down list.
I realize this will not necessarily produce sane, let along
optimal, defaults for the user. But getting that right is
potentially quite complicated and would have to be done on a
per-package basis. Nonetheless, there should be some improvements
possible that are not too expensive.
I completely understand, and I'm all for avoiding the risk of
introducing new bugs in that area. I'm also thinking about removing some
of the defaults in my packages, for example. Then a specification for a
list or matrix would be "remembered" at least if no other lists/matrices
exist in the session, which is maybe not so uncommon.
IMHO there is one exception though where a change of gretl's behavior is
needed: The returned object, because that overwrites things and could
lead to dataloss. As a short-term solution, couldn't it simply be left
As for the trouble Sven reported with "Save as" and "Delete" for
matrices in the GUI session window, I think these should be fixed
now in CVS and today's Windows snapshot.
Thanks, I'll try it out.