Contents

#Known issues & Bugs

  0000. A `every` event used in a controller's action will time correctly on the first action, but subsequent actions will be off by at most 3 ticks.
  This is because we do not have any way (currently) to reset the timing queue in the controller as it reisters for all timing events at init. See
  "Does not call intervals of other actions; and still works when switching back actions" in `spec/kern/controller_spec.rb` 
  0001. `Goto` macro does not recursively 'dealloc' everything.

Version data entries

31 entries across 31 versions & 1 rubygems

Version	Path
flok-0.0.74	docs/known_issues.md
flok-0.0.73	docs/known_issues.md
flok-0.0.72	docs/known_issues.md
flok-0.0.71	docs/known_issues.md
flok-0.0.70	docs/known_issues.md
flok-0.0.69	docs/known_issues.md
flok-0.0.68	docs/known_issues.md
flok-0.0.67	docs/known_issues.md
flok-0.0.66	docs/known_issues.md
flok-0.0.65	docs/known_issues.md
flok-0.0.64	docs/known_issues.md
flok-0.0.63	docs/known_issues.md
flok-0.0.62	docs/known_issues.md
flok-0.0.61	docs/known_issues.md
flok-0.0.60	docs/known_issues.md
flok-0.0.57	docs/known_issues.md
flok-0.0.56	docs/known_issues.md
flok-0.0.55	docs/known_issues.md
flok-0.0.54	docs/known_issues.md
flok-0.0.53	docs/known_issues.md