Shashi, In case you're still there: How do I access results from calculation done inside one consume in another consume? I think I'm doing this wrong. I basically have some inputs that when they change (via one of your widgets), I run some functions on the values of the inputs. These functions have some results, and then I want to access those results in another tab in combination with other inputs and widgets etc... Sorry for all the questions..
Yakir Gagnon The Queensland Brain Institute (Building #79) The University of Queensland Brisbane QLD 4072 Australia cell +61 (0)424 393 332 work +61 (0)733 654 089 On Thu, Oct 15, 2015 at 2:29 PM, Yakir Gagnon <[email protected]> wrote: > *amazing... > > > Yakir Gagnon > The Queensland Brain Institute (Building #79) > The University of Queensland > Brisbane QLD 4072 > Australia > > cell +61 (0)424 393 332 > work +61 (0)733 654 089 > > On Thu, Oct 15, 2015 at 2:29 PM, Yakir Gagnon <[email protected]> wrote: > >> OMG amaing. Thanks again ...!!! >> >> >> Yakir Gagnon >> The Queensland Brain Institute (Building #79) >> The University of Queensland >> Brisbane QLD 4072 >> Australia >> >> cell +61 (0)424 393 332 >> work +61 (0)733 654 089 >> >> On Thu, Oct 15, 2015 at 2:17 PM, Shashi Gowda <[email protected]> >> wrote: >> >>> Memoization means storing the result of a function and then using the >>> stored value when the function is called with the same arguments. >>> >>> See https://github.com/simonster/Memoize.jl >>> >>> On Thu, Oct 15, 2015 at 9:16 AM, Yakir Gagnon <[email protected]> >>> wrote: >>> >>>> Thanks Shashi, >>>> But while that prevents stuff in another tab from running before that >>>> other tab is in focus, stuff runs twice when that tab gets focused...!? >>>> Maybe that's what you meant with "you will need to memorize the >>>> function you pass to lift..." but in that case I don't understand what you >>>> mean. >>>> >>>> Thanks again for the awesome work! >>>> >>>> >>>> Yakir Gagnon >>>> The Queensland Brain Institute (Building #79) >>>> The University of Queensland >>>> Brisbane QLD 4072 >>>> Australia >>>> >>>> cell +61 (0)424 393 332 >>>> work +61 (0)733 654 089 >>>> >>>> On Thu, Oct 15, 2015 at 2:46 AM, Shashi Gowda <[email protected]> >>>> wrote: >>>> >>>>> You can pass in an init=empty keyword argument to lift / consume, and >>>>> the initial value of the signal will be an empty UI. The actual value will >>>>> be computed next time the input signal udpates. You should also provide a >>>>> typ=Any kwarg to lift / consume so that if you replace empty with >>>>> something >>>>> that is not Empty, you do not get a type conversion error. something like: >>>>> >>>>> selected_tab = Input(1) >>>>> vbox( >>>>> tabs(["a", "b"]) >>> selected_tab, >>>>> lift(selected_tab, typ=Any, init=empty) do page_no >>>>> // compute page at page_no >>>>> end >>>>> ) >>>>> >>>>> may be what you need. To avoid recomputing when you switch to tab 1 >>>>> and then to tab 2 and then back to tab 1, you will need to memoize the >>>>> function you pass to lift... >>>>> >>>>> >>>>> On Wed, Oct 14, 2015 at 6:06 PM, Yakir Gagnon <[email protected]> >>>>> wrote: >>>>> >>>>>> Title... >>>>>> I have a bunch of tabs and it all takes time to load. I don't need >>>>>> the functions to evaluate before the user presses on something. Any easy >>>>>> way i can prevent all the signals from running their functions when the >>>>>> pages load up? >>>>> >>>>> >>>>> >>>> >>> >> >
