Philipp Niedermayer
Philipp Niedermayer
Loosely related issue: #315
> Maybe the line could keep the indices as a list after optimising? So that after elements are removed all remaining elements still have their original id Currently element ids...
I see, then it's clearly not a bug. I have a use case where it is convenient to allow zero size arrays. Please don't prevent it with an explicit check,...
Some further ideas to mitigate memory limitations: - Have a particles monitor that writes data to a file after a given memory size is reached (e.g. 100 MB) and then...
I'm aware of the security implications of `eval`, that's why there is a security check before evaluation. It only allows numbers (including the letter e for exponentials), brackets and the...
> Other places in GRC that do eval() pass in a local namespace. As mentioned before, **QT GUI Entry** is a counterexample: when type is set to raw, it calls...
> The eval should at least use a local namespace. I don't know to what degree that helps, but let's not be less "secure" than the rest of the system....
> So, would it be possible to integrate the advantages of this block into the existing range or entry block, so we don't have multiple blocks that do almost the...
> Both blocks are missing a msg input port, that one could set the value be clicking on the spectrum display. @dl1ksv at least for my block you can simply...
> A msg port would be cleaner, though. @willcode Can you provide a hint for msg ports on variable-defining blocks? Since the block id and variable name are identical by...