Skip to content

Commit

Permalink
update comment about FPS in quicksilver frontend
Browse files Browse the repository at this point in the history
  • Loading branch information
jayrave committed Jun 28, 2020
1 parent 4fa174c commit b087ef5
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions quicksilver_frontend/src/main.rs
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,13 @@ async fn app(window: Window, mut graphics: Graphics, input: Input) -> Result<()>
let mut fps = Fps::new();

// Note: unlike other front-ends, we are not using any `FrameLimiter`s
// for quicksilver. Looks like awaiting on the event queue automatically
// sets the FPS to 60. This can be seen from the logs from our Fps struct
// for quicksilver. This is because, we are using quicksilver for targetting
// the web, where, when `await` on the event queue resolves is dependent on
// the rate of `requestAnimationFrame` which inturn is dependent on the
// screen's refresh rate. Therefore, the FPS won't be uncapped here & we can
// let this be decided by the screen's refresh rate
//
// Relevant issue: https://github.com/jayrave/runner/issues/1
'running: loop {
{
// Drain event pump to event queue. Separate scope as
Expand Down

0 comments on commit b087ef5

Please sign in to comment.