Received: by 10.52.18.203 with SMTP id y11mr533473vdd.6.1350000266057;
        Thu, 11 Oct 2012 17:04:26 -0700 (PDT)
X-BeenThere: pyglet-users@googlegroups.com
Received: by 10.52.89.80 with SMTP id bm16ls1848404vdb.9.gmail; Thu, 11 Oct
 2012 17:04:24 -0700 (PDT)
Received: by 10.59.6.72 with SMTP id cs8mr427213ved.27.1350000264904;
        Thu, 11 Oct 2012 17:04:24 -0700 (PDT)
Received: by 10.59.6.72 with SMTP id cs8mr427212ved.27.1350000264893;
        Thu, 11 Oct 2012 17:04:24 -0700 (PDT)
Return-Path: <r1chardj0...@gmail.com>
Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181])
        by gmr-mx.google.com with ESMTPS id s13si438039vde.2.2012.10.11.17.04.24
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 11 Oct 2012 17:04:24 -0700 (PDT)
Received-SPF: pass (google.com: domain of r1chardj0...@gmail.com designates 209.85.220.181 as permitted sender) client-ip=209.85.220.181;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of r1chardj0...@gmail.com designates 209.85.220.181 as permitted sender) smtp.mail=r1chardj0...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-vc0-f181.google.com with SMTP id n11so2922269vch.26
        for <pyglet-users@googlegroups.com>; Thu, 11 Oct 2012 17:04:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=vlqmIa4BjsFy97XjlnaYHKCyuclmDGbWF3n78jXM2Tw=;
        b=kukyPv5SlOER9B8QfoBT723DfVeO3OEH1a2PsxTE9p0ry/YomKivfbcpBDv4f5nELI
         Kx2QvPfmHH4UA0SVpAQsezoUtFg+SqJOuV2BF3aEZuNd/6GCR5tkyChYw9hrWINz930I
         ml/t9AHwLPYQSIB+mWI8KFblYSkQFHGQjLWJPcC8VgfU+r2UB70DVAy0gwd0pKEk/JKh
         n6LWU1GYaPoPZ50mNLcs3dyR0+veFPwV7VwAcOmLHe2hy0DjXQpIK4/9youHU1WsFwYd
         zqWA20TkbTRkNcOQMEfX8vcObOOo0Z/Q8mnYK2Qw1VhCaH/ObrhljgFkQffC1WaGMe5g
         pwbg==
MIME-Version: 1.0
Received: by 10.220.150.14 with SMTP id w14mr1521256vcv.13.1350000264594; Thu,
 11 Oct 2012 17:04:24 -0700 (PDT)
Received: by 10.58.147.104 with HTTP; Thu, 11 Oct 2012 17:04:24 -0700 (PDT)
In-Reply-To: <5077554F.9080...@gmail.com>
References: <9fc0f4b9-227e-4f04-a7ed-2816a0c9126b@googlegroups.com>
	<CALtqtKTb58qWXsE6+dpMBPGdzqFSyp5kftt2rZeig4tneu5...@mail.gmail.com>
	<CAGH5Vz-c98tOCYuihd9Tvrm6vh7F+s-FaXE-nSm-ufq1vFk...@mail.gmail.com>
	<5077554F.9080...@gmail.com>
Date: Fri, 12 Oct 2012 11:04:24 +1100
Message-ID: <CAHrZfZA=Pi7TPzCt5KFXEMa1BD1ewCUDkUfnP213sFjSWx-...@mail.gmail.com>
Subject: Re: Key checking in the update function and on_key_press
From: Richard Jones <r1chardj0...@gmail.com>
To: pyglet-users@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

On 12 October 2012 10:25, Adam Bark <adam.jt...@gmail.com> wrote:
> Personally, I set a flag in on_key_press and unset it in on_key_release.

That's all that KeyStateHandler does. It manages those flags for you :-)


     Richard