3:21 p.m.
Hi all,
referring to the function package guide section 4.3.2, "Run-time limits
and defaults". This should apply to int(egers) and scalar(s), and I
think for integers I have used that successfully at least for the upper
and lower limits (not sure about the defaults).
But for general scalars, I'm having problems cooking up a working
example - so is there a package out there that uses this feature?
Or going back to integers, a package that does run-time defaults, not
just limits?
thanks
sven
10:36 a.m.
Am 14.02.2026 um 16:21 schrieb Sven Schreiber:
referring to the function package guide section 4.3.2, "Run-time
limits and defaults". This should apply to int(egers) and scalar(s),
and I think for integers I have used that successfully at least for
the upper and lower limits (not sure about the defaults).
But for general scalars, I'm having problems cooking up a working
example - so is there a package out there that uses this feature?
Or going back to integers, a package that does run-time defaults, not
just limits?
Any ideas about which packages do this? Jack, some of your recent
updates perhaps?
thanks
sven
1 p.m.
Am 17.02.2026 um 11:36 schrieb Sven Schreiber:
Am 14.02.2026 um 16:21 schrieb Sven Schreiber:
> referring to the function package guide section 4.3.2, "Run-time
> limits and defaults". This should apply to int(egers) and scalar(s),
> and I think for integers I have used that successfully at least for
> the upper and lower limits (not sure about the defaults).
>
> But for general scalars, I'm having problems cooking up a working
> example - so is there a package out there that uses this feature?
>
> Or going back to integers, a package that does run-time defaults, not
> just limits?
>
Any ideas about which packages do this? Jack, some of your recent
updates perhaps?
OK, off-list, Jack indeed pointed me to his ZivotAndrews package which
does this default thing with integers. Thanks!
For general scalars, I'm having no luck, though. I'm attaching a
barebones example which doesn't work for me - meaning that its default
is defined as 2, but that's not shown. (The corresponding variant with
an int argument works OK.)
(Disregard the included private function initial_defaults, it's not used
there.)
An unrelated extra GUI problem: When executing this package, there is a
"+" button at the right, to create a new scalar variable. When I click
it, I get a formula entry window. Then I just enter (wrongly) a new name
(say "hu") but no formula. I get an empty error window with no message
and a close button. (Apparently in the background "hu" is created and
initialized as usual with NA, that's not the issue.)
thanks
sven
10:10 p.m.
Am 17.02.2026 um 14:00 schrieb Sven Schreiber:
...
For general scalars, I'm having no luck, though. I'm attaching a
barebones example which doesn't work for me - meaning that its default
is defined as 2, but that's not shown. (The corresponding variant with
an int argument works OK.)
Well, looking at gui/fncall.c (following Allin's off-list directions) I
found at least I typo, I guess. Here are lines 1799-1803 inside the
function *double_arg_selector:
err=min_max_def_from_ui(ui,dvals,0);
if(!err){
minv=dvals[0];
minv=dvals[1];
dflt=dvals[2];
}
As you can see, "minv" is assigned twice, and I guess the second one
should be "maxv" instead (which exists at the top of the function).
Not sure whether that solves all the problems.
An unrelated extra GUI problem: When executing this package, there is
a "+" button at the right, to create a new scalar variable. When I
click it, I get a formula entry window. Then I just enter (wrongly) a
new name (say "hu") but no formula. I get an empty error window with
no message and a close button. (Apparently in the background "hu" is
created and initialized as usual with NA, that's not the issue.)
Again, this is unrelated. The thing is that the creation of a scalar in
the GUI is done differently when going through the session icon view.
(There you get a window with all defined scalars in the form of a
listing, and you can add new rows to that listing.) So perhaps only in
this package execution context does this "create new scalar" window
appear, and thus won't get much use I guess.
thanks
sven
19
days inactive
30
days old
3 comments
1 participants
participants (1)
-
Sven Schreiber