A serious computing device never gives such issues.

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On 20 November 2017 at 02:26, bw <stabbingfin...@gmail.com> wrote:

> Interesting notion, event.clear(). Or perhaps try an event.pump() in the
> game loop.
>
> On 11/18/2017 11:28 PM, Ian Mallett wrote:
>
> ​Hi,
>
> FWIW I am unable to reproduce on Win 7 Pro, Py 3.5.1, PyGame 1.9.2a0 (to
> print the latter, `print(pygame.ver)`).
>
> The event system, like everything else, is really just a thin layer over
> SDL's—so for platform-specific issues in PyGame it's commonly the
> underlying SDL that's at fault. Notwithstanding that SDL is fairly
> well-tested, but Mac tends to be a lower priority for testing, on account
> of Apple making game development on OS X difficult in a variety of ways. My
> *guess* is that it's a minor hiccup in older SDL on MacOS that no one
> ever noticed before, additionally because MOUSEBUTTONUP is often ignored—in
> which case you're most likely to get closure from the SDL community, unless
> someone here feels like C spelunking.
>
> Maybe `pygame.event.clear()` would trick the event system into behaving
> better on startup?
>
> Ian
>
>
>


-- 
Kalasuri Diliup Gabadamudalige

https://dahamgatalu.wordpress.com/
http://soft.diliupg.com/
http://www.diliupg.com

**********************************************************************************************
This e-mail is confidential. It may also be legally privileged. If you are
not the intended recipient or have received it in error, please delete it
and all copies from your system and notify the sender immediately by return
e-mail. Any unauthorized reading, reproducing, printing or further
dissemination of this e-mail or its contents is strictly prohibited and may
be unlawful. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.
**********************************************************************************************

Reply via email to