> > The automatic evaluation of all @interact cells is a feature. > Do you wish that this did not occur, and that users had > to explicitly hit shift-enter (or click some button) to "fire up" > any interact? It would be easy to change the implementation > to have that behavior (in fact, that would be a lot easier to do > than the current implementation).
Like I said, I wasn't sure if that was a feature or not. One reason I feel it is a bug is because if the @interact cell depends on *non*- interact cells (e.g. if you defined some function earlier and then use it interactively) you just get error messages upon startup. But I wouldn't want to try to sway either way; it just makes loading things up long. If it was easy to have a "evaluate all interact" button like the pretty print one, that might help, but others may find the auto- evaluate useful, so I don't know what the 'right' answer is. > Why don't you post a link to your worksheet? http://www.math.uchicago.edu/~crisman/Weird_Interact_Behavior_Test.sws But even the following code does it. @interact def _(k=slider(0,5,1,1)): P1=plot(lambda x: x^k, 0,1) show(P1) Interestingly, with just one @interact cell, I get the graph but can't do slider; once there are two or more @interact cells, at least one gives these weird error messages involving NaN, etc, which Shift- Entering clears up (still without slider). So maybe there are two separate issues, I'm not sure. - kcrisman --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
