glazier-pipes 0.1.5.0 → 0.1.5.1

raw patch · 3 files changed

+7/−4 lines, 3 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• LICENSE +2/−2
• glazier-pipes.cabal +1/−1
• src/Glazier/Pipes/Ui.hs +4/−1

@@ -1,4 +1,4 @@-Copyright Author name here (c) 2017+Copyright Louis Pan (c) 2017  All rights reserved. @@ -13,7 +13,7 @@       disclaimer in the documentation and/or other materials provided       with the distribution. -    * Neither the name of Author name here nor the names of other+    * Neither the name of Louis Pan nor the names of other       contributors may be used to endorse or promote products derived       from this software without specific prior written permission. 

@@ -1,5 +1,5 @@ name:                glazier-pipes-version:             0.1.5.0+version:             0.1.5.1 synopsis:            A threaded rendering framework using glaizer and pipes description:         Please see README.md homepage:            https://github.com/louispan/glazier-pipes#readme

@@ -15,6 +15,8 @@ -- | This is similar to part of the Elm startApp. -- This is responsible for running the Glazier Gadget update tick until it quits. -- This is also responsible for rendering the frame.+-- This function is only required if you are not using another application framework which+-- already takes care of rendering and processing user input. runUi :: (MonadIO io) =>      Int   -> (s -> IO ()) -- render@@ -57,10 +59,11 @@                  lift $ render s)             (const . atomically $ putTMVar finishedRenderThread ()) -    -- This is different between the Strict and Lazy version+    -- application run     s' <- P.runEffect $         appSignal P.>-> PP.mapM             (liftIO . atomically . void . STE.forceSwapTMVar latestState) P.>-> PP.drain+     -- cleanup     -- allow rendering of the frame one last time     liftIO . atomically $ takeTMVar enableRenderThread