Sent: Friday, October 21, 2016 2:47 AM
To: Jonathan Wilkes via Pd-list
Subject: Re: [PD] window close bug
Just restarting PD.
Sent: 21 October 2016 03:13
To: Liam Goodacre; Jonathan Wilkes via Pd-list
Subject: Re: window close bug
> I would expect the whole OS to be running erratically if I had a problem with...
> A quick restart also solves the issue
> Am I the only one who experiences this?
Sent: Friday, October 21, 2016 2:01 AM
To: Jonathan Wilkes via Pd-list
Subject: Re: [PD] window close bug
Thanks Lucas. I would expect the whole OS to be running erratically if I had a problem with the keyboard, but as it is I only experience this behaviour in PD. A quick restart also solves the issue.
Any other ideas? Am I the only one who experiences this?
From: Lucas Cordiviola
Sent: 18 October 2016 00:15
To: Liam Goodacre;Jonathan Wilkes via Pd-list
Subject: Re: window close bug
Are you sure your keyboard is ok?
Try another keyboard, if you are on a notebook try disabling the one that's built-in and connect an usb one.
It could be a faulty key (probably ALT?).
I occasionally use win10 and never experienced this behavior you report, normally I'm on win8.1 and also didn`t.
Mensaje telepatico asistido por maquinas.
From: Pd-list <pd-list-bounces@lists.iem.at> on behalf of Liam Goodacre <liamg_uw@hotmail.com>
Sent: Monday, October 17, 2016 11:55 AM
To: Jonathan Wilkes via Pd-list
Subject: [PD] window close bug
Here’s another curious bug that I’ve just started experiencing (seems like I’m having one of those weeks!) Occasionally, the window cross icon on the top right seems to go rogue and start acting out another menu command. So every time I press it, it will zoom in on the canvas instead of closing the window, or create a comment, or (distressingly) save the file. These are the three that I’ve experienced so far. When it happens, it’s consistent, so that every open window has the same problem, and I have to force-quit PD (probably I have to force quit because the console cross icon has also been affected). I haven’t spotted a trigger for this behaviour yet, it seems to be random. Has anyone ever experienced this? I’m on 0.47.1, Windows 10.