Am 28.05.2013 18:24, schrieb Allin Cottrell:
On Tue, 28 May 2013, Sven Schreiber wrote:
> for the first time ever I tried to attach a function package to the menus,
> but I couldn't get it to appear. I never got an error, just no effect.
Ah, I introduced a new bug that disabled that effect when I
was fixing the other problems you mentioned. But that in turn
was fixed in CVS and snapshots a few hours ago.
It's working now, very cool.
> I have noticed that in the dialog where the menu path is
> chosen, the "model -> limited dependent" submenu is
> expandable, whereas the "model -> time series" submenu
> isn't. (There is the 3rd-level submenu cointegration tests
> there.)
OK, I suppose in principle it ought to be possible to add an
item to the Cointegration test submenu; I'll look into that.
Yes that would be the most logical place.
On a related note: I've noticed by trial-and-error that for
"bundle-print" etc. the corresponding defined function must be declared
public instead of helper. (Otherwise the dialog items were greyed out.)
That logic wasn't obvious. And actually, the printing via that function
isn't working for me. Also the bundle that's returned never shows up
anyway -- at least since I have added the package to the menu it's also
not possible anymore to specify a return bundle name/container.
(In my case I'm grabbing a matrix from the result bundle and print the
elements in some way. Nothing happens.)
One further suggestion for the packages: It would be nice if the
bundle-print function (and friends) could get automatic access to the
arguments with which gui-main was called. I know I can stuff all the
arguments inside the bundle and read them out in bundle-print, but that
seems redundant and clunky.
thanks,
sven