|
@@ -52,7 +52,7 @@ This first beta does NOT have the following features, but they are planned in th
|
|
|
|
|
|
|
|
## Feedback wanted
|
|
## Feedback wanted
|
|
|
Here are some things I want to get feedback on during this first beta:
|
|
Here are some things I want to get feedback on during this first beta:
|
|
|
-- Is the `k2.new_frame()` concept OK? I was thinking of merging `new_frame()` and `process_events()`,
|
|
|
|
|
|
|
+- Is the `k2.new_frame()` concept OK? It sets the "frame time" and clears some frame-specific state. I was thinking of merging `new_frame()` and `process_events()`,
|
|
|
but something tells me that some people may want to move their event processing around. Initially
|
|
but something tells me that some people may want to move their event processing around. Initially
|
|
|
I was toying with the idea to have the user use `core:time` and figure out `dt` etc themselves,
|
|
I was toying with the idea to have the user use `core:time` and figure out `dt` etc themselves,
|
|
|
but that was not good for first-user experience.
|
|
but that was not good for first-user experience.
|
Karl Zylinski