Re: [Gretl-devel] bundle-print function in a GUI package
On Wed, 12 Jul 2017, Sven Schreiber wrote:
Am 12.07.2017 um 18:47 schrieb Allin Cottrell:
> On Wed, 12 Jul 2017, Sven Schreiber wrote:
>> Should or could these differences play a role? Because otherwise so far I
>> didn't see where my mistake would be.
>
> The gui-main function must be marked as "no-print" in order for the
> bundle-print function to be invoked (otherwise we assume it takes care of
> printing without any auto-assist).
Aha! That must be it, I thought the bundle-print function would automatically
be run. From the pkg guide the no-print option seemed to be there just to
suppress opening an unnecessary window.
"no-print" as an attribute of gui-main can mean that truly nothing
should be printed, but if gui-main returns a bundle and there's a
bundle-print function in the package, its meaning becomes, "I'm not
going to print anything myself, but go ahead and invoke
bundle-print".
If bundle-print were invoked regardless of the no-print attribute on
gui-main, the relationship between bundle-print and whatever
gui-main wants to print itself would be unclear. Which should come
first, for instance? And if gui-main wants to invoke the bundle
printer as part of its output, it can do so: there are examples of
this among the current gfns.
But maybe this point should be made clearer in the Guide.
Actually, why would an author add a bundle-print function if it
shouldn't be run?
There's clearly no point if it should _never_ be run, but remember
it will be run whenever the user activates the icon for a bundle
produced by the package in question.
Allin