Empathy List Archives

Q

QuackingPlums

Mon, Jan 26, 2015 9:08 AM

I've been using 01.05 until now but I noticed this morning that 01.23 is
being considered as an RC with only a week for review so I wanted to throw
this out there in case it's a bug whilst I investigate further.

I tend to work with multiple files open across multiple virtual desktops
(Spaces, or whatever it's called these days) and I open and close down
windows as I need them. I noticed recently that sometimes if I do Command-W
to close a window, then select the appropriate option (save or don't save)
on the "This document has been modified" dialog, OpenSCAD sometimes gets
stuck in one of the following scenarios:

Window is closed, but now OpenSCAD doesn't switch to one of my other open
windows (shows "OpenSCAD" in the menu but no other menu options)
Window doesn't close but now OpenSCAD blocks me from activating on of my
other open windows

It's not as simple as 'always when I click save' and I haven't done enough
testing yet to track down the exact sequence of events that causes it. Has
anybody else noticed anything similar? I'll upgrade to 01.23 now and see if
it still occurs.

--
View this message in context: http://forum.openscad.org/Weird-close-behaviour-on-OSX-tp11245.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

I've been using 01.05 until now but I noticed this morning that 01.23 is being considered as an RC with only a week for review so I wanted to throw this out there in case it's a bug whilst I investigate further. I tend to work with multiple files open across multiple virtual desktops (Spaces, or whatever it's called these days) and I open and close down windows as I need them. I noticed recently that sometimes if I do Command-W to close a window, then select the appropriate option (save or don't save) on the "This document has been modified" dialog, OpenSCAD *sometimes* gets stuck in one of the following scenarios: * Window is closed, but now OpenSCAD doesn't switch to one of my other open windows (shows "OpenSCAD" in the menu but no other menu options) * Window doesn't close but now OpenSCAD blocks me from activating on of my other open windows It's not as simple as 'always when I click save' and I haven't done enough testing yet to track down the exact sequence of events that causes it. Has anybody else noticed anything similar? I'll upgrade to 01.23 now and see if it still occurs. -- View this message in context: http://forum.openscad.org/Weird-close-behaviour-on-OSX-tp11245.html Sent from the OpenSCAD mailing list archive at Nabble.com.

MK

Marius Kintel

Tue, Jan 27, 2015 12:36 AM

On Jan 26, 2015, at 04:08 AM, QuackingPlums quackingplums@hotmail.com wrote:

Window is closed, but now OpenSCAD doesn't switch to one of my other open
windows (shows "OpenSCAD" in the menu but no other menu options)
Window doesn't close but now OpenSCAD blocks me from activating on of my
other open windows

I think these may be different issues.
I can sometimes reproduce the first, but not in debug mode - it feels like a Qt issue.

In terms of the second one; you say the window doesn’t close and also blocks other windows? If you manage to reproduce that, it would be very helpful!

-Marius

On Jan 26, 2015, at 04:08 AM, QuackingPlums <quackingplums@hotmail.com> wrote: > > * Window is closed, but now OpenSCAD doesn't switch to one of my other open > windows (shows "OpenSCAD" in the menu but no other menu options) > * Window doesn't close but now OpenSCAD blocks me from activating on of my > other open windows > I think these may be different issues. I can sometimes reproduce the first, but not in debug mode - it feels like a Qt issue. In terms of the second one; you say the window _doesn’t_ close and also blocks other windows? If you manage to reproduce that, it would be very helpful! -Marius

Q

QuackingPlums

Thu, Jan 29, 2015 9:26 AM

I have managed to get this to happen again in 01.23, but only after working
with multiple files open for a long time. I still can't lock it down to an
exact sequence of steps though. :(

Coincidentally, it feels a LOT like the situation described in the latest
XKCD cartoon: http://xkcd.com/1479/

I'm pretty sure there aren't any modal dialogs open anywhere though
(unless it just failed to close the one that is asking me if I want to save
before closing).

--
View this message in context: http://forum.openscad.org/Weird-close-behaviour-on-OSX-tp11245p11294.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

I have managed to get this to happen again in 01.23, but only after working with multiple files open for a long time. I still can't lock it down to an exact sequence of steps though. :( Coincidentally, it feels a LOT like the situation described in the latest XKCD cartoon: http://xkcd.com/1479/ - I'm pretty sure there aren't any modal dialogs open anywhere though (unless it just failed to close the one that is asking me if I want to save before closing). -- View this message in context: http://forum.openscad.org/Weird-close-behaviour-on-OSX-tp11245p11294.html Sent from the OpenSCAD mailing list archive at Nabble.com.

MK

Marius Kintel

Thu, Jan 29, 2015 5:00 PM

On Jan 29, 2015, at 04:26 AM, QuackingPlums quackingplums@hotmail.com wrote:

I have managed to get this to happen again in 01.23, but only after working
with multiple files open for a long time. I still can't lock it down to an
exact sequence of steps though. :(

I think I managed to run into the same issue. It don’t think it was related to closing windows though.
It also happened after working with multiple designs over some time.
It looks like we lose all input events, leaving the application unresponsive.
It suspiciously looks like a Qt bug. Qt-5.4.1 is just around the corner. Perhaps that would help.

Anyway, if you find more indicators what could be wrong, please post it.
..and when it happens, could you try to mess around a bit to see if you can get any output from the app, things like window resizing, opening files using the “open” command etc.?

-Marius

On Jan 29, 2015, at 04:26 AM, QuackingPlums <quackingplums@hotmail.com> wrote: > I have managed to get this to happen again in 01.23, but only after working > with multiple files open for a long time. I still can't lock it down to an > exact sequence of steps though. :( > I think I managed to run into the same issue. It don’t think it was related to closing windows though. It also happened after working with multiple designs over some time. It looks like we lose all input events, leaving the application unresponsive. It suspiciously looks like a Qt bug. Qt-5.4.1 is just around the corner. Perhaps that would help. Anyway, if you find more indicators what could be wrong, please post it. ..and _when_ it happens, could you try to mess around a bit to see if you can get _any_ output from the app, things like window resizing, opening files using the “open” command etc.? -Marius

discuss@lists.openscad.org

Weird 'close' behaviour on OSX