This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-17
Channels
- # aws (2)
- # beginners (34)
- # boot (39)
- # cider (28)
- # cljs-dev (2)
- # cljsrn (30)
- # clojure (195)
- # clojure-austin (6)
- # clojure-dev (6)
- # clojure-dusseldorf (1)
- # clojure-france (1)
- # clojure-russia (139)
- # clojure-spec (25)
- # clojure-uk (66)
- # clojurescript (125)
- # community-development (1)
- # core-async (42)
- # cryogen (1)
- # cursive (22)
- # datascript (6)
- # datomic (67)
- # docker (1)
- # emacs (7)
- # events (1)
- # garden (3)
- # hoplon (15)
- # jobs (3)
- # lein-figwheel (10)
- # leiningen (3)
- # luminus (4)
- # mount (2)
- # nginx (1)
- # off-topic (101)
- # om (42)
- # om-next (6)
- # onyx (7)
- # proton (1)
- # protorepl (4)
- # re-frame (15)
- # reagent (30)
- # remote-jobs (1)
- # ring (8)
- # ring-swagger (17)
- # rum (1)
- # spacemacs (2)
- # sql (1)
- # yada (50)
How should I delete the window if set :trigger/period
to [1000 :millisecond]
?
I also trying to remove the trigger by return nil in refinement. But it begins to bump nil
in trigger.
@richardwong Windows can’t be deleted. If they are used in combination with a discarding trigger refinement, their content is set to nil, and internally the record of the window contents is removed.
I don’t understand what you mean by “remove the trigger”. Triggers, also, cannot be removed.
How to clean the window state of extents, I found the window will hold all extents that window aggregated?
Remove the trigger means stop :trigger/period
bump process. after set window state
to nil
I still can get the sync method being called..
@isaac A window contents aren’t subject to “set the whole thing to nil”, or something like that. If you want a clean state, kill off the job and start a new one.
@richardwong Triggers will continue to fire on their period interval regardless of their contents.