On Fri, Jul 26, 2024 at 10:15 AM Sven Schreiber
<sven.schreiber(a)fu-berlin.de> wrote:
Am 24.07.2024 um 23:03 schrieb Sven Schreiber:
Am 24.07.2024 um 22:45 schrieb Cottrell, Allin:
On Wed, Jul 24, 2024 at 4:22 PM Sven Schreiber
<sven.schreiber(a)fu-berlin.de> wrote:
I don't have time to give a minimal example right now, but I could do so
on Friday or so, if necessary.
Please do. This may be redundant, but of course the "no_const"
specification only applies to GUI usage.
Will do, and yes, GUI context.
OK, I'm attaching a stripped-down package version for testing. I'm observing
various problems:
- The package specifies "no-data-ok" and this also shows up in the info.
However, when executing the package GUI, a warning dialog with "this requires a
dataset" appears.
I think that's because your package depends on SVAR, which requires
time-series data.
- The GUI_SVAR_setID_uimaker function is declared as the ui-maker,
and requests no_const both for the lists X and Y, as well as no_singleton for Y. However,
in the GUI I can execute the package under all those cases that are supposed to be
prevented.
Your package doesn't seem to specify a menu attachment: that's
required for the ui-maker to kick in.
Allin