On May 21, 11:33 pm, pang wrote:
> I have uploaded an example of an interaction which could be used to
> present the problem of the eight queens:
>
> http://wiki.sagemath.org/interact/misc#Queensonboard
I also added an example: play nim against a perfect oponent. I created
a special page in th
> Does anyone
> have a non-trivial example they have already used which could
> be posted on the wiki?
I have uploaded an example of an interaction which could be used to
present the problem of the eight queens:
http://wiki.sagemath.org/interact/misc#Queensonboard
--~--~-~--~~--
On Thu, May 21, 2009 at 06:30:27AM -0700, pang wrote:
>
> On May 21, 2:48 pm, kcrisman wrote:
> > Something closely related was discussed but apparently never
> > implemented a while ago (a box to click for not updating immediately,
> > which would be unclicked when one wanted things to update a
>
> Actually, I did implement this
> athttp://trac.sagemath.org/sage_trac/ticket/5194, and it was merged in
> Sage 3.3.
Yes, this is documented - sorry for the mixup. It works as advertised
- including that for now, the image disappears as soon as one changes
a control.
A quick search using
On Thu, May 21, 2009 at 5:48 AM, kcrisman wrote:
>
> Something closely related was discussed but apparently never
> implemented a while ago (a box to click for not updating immediately,
> which would be unclicked when one wanted things to update again).
> Would this idea be relevant to your needs
On May 21, 2:48 pm, kcrisman wrote:
> Something closely related was discussed but apparently never
> implemented a while ago (a box to click for not updating immediately,
> which would be unclicked when one wanted things to update again).
> Would this idea be relevant to your needs?
Well, that w
Something closely related was discussed but apparently never
implemented a while ago (a box to click for not updating immediately,
which would be unclicked when one wanted things to update again).
Would this idea be relevant to your needs?
http://groups.google.com/group/sage-devel/browse_thread/t
> You are correct. Right now one can't do what you want with controls.
> It would
> be possible for us to implement it though. How would you like to
> specify that a control
> doesn't cause a change?
For example,
@interact
def _(var1=input_box(default_value=1, trigger_updates=False),
var2=inpu
On Thu, May 21, 2009 at 3:57 AM, Pablo Angulo wrote:
>
> Hello:
>
> Correct me if I'm wrong, but there's no way to avoid that an interaction
> is rebuilt after any change in the controls. While I've been able to
> live with that, I was now working in some examples using persistent data
> (code is
