Sven Schreiber schrieb:
I think that's a good choice -- I will do some more testing
the old bugs are gone AFAICT, great work!
Then however I did something mean:
After saving the package (and having run it successfully) I created
another function with the same name as the public interface of the
package. Ran the new function (it doesn't do anything, basically just a
dummy). Then ran the previously saved function again: The result is not
the one specified by the function within the package, but by the new
version. So the result is rubbish.
As I said, this is mean-spirited and I guess it's not new behavior.
Ideally, the package should be encapsulated from other scripts that an
unsuspecting user creates, but I don't think this is a blocker for a new
another minor and unrelated issue:
An integer argument with a range such as "int freqpoints[0:500:100]"
gives in the GUI an entry field with clickable up-down arrows, which is
But an argument w/o range such as "int lagorder" gives no clickable
arrows (a drop-down-list-style arrow is there but greyed out), though I
cannot see why they couldn't be there as well.
(For non-integer arguments it's only a bit strange that there's also a
greyed-out arrow, but that's only cosmetic.)