Closing Preferences Window Closes Application! #42464

Closed
opened 8 years ago by chapp-ai · 23 comments

System Information
Operating system and graphics card
Mac OS X 10.9.5, NVIDIA GeForce GT 750M

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)
2.72b

Short description of error
Clicking the Preferences window banner red circle on a Mac closes the entire application instead of closing just the Preferences window. The only way to hide (but not close) the window is click anywhere outside the window, but then it automatically redisplays each time Blender is restarted.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
Choose "User Preferences" from the File menu, then click that window's red Close button on the window banner. Instead of closing the preferences window, the entire damned application shuts down.

**System Information** Operating system and graphics card Mac OS X 10.9.5, NVIDIA GeForce GT 750M **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Worked: (optional) 2.72b **Short description of error** Clicking the Preferences window banner red circle on a Mac closes the entire application instead of closing just the Preferences window. The only way to hide (but not close) the window is click anywhere outside the window, but then it automatically redisplays each time Blender is restarted. **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps Choose "User Preferences" from the File menu, then click that window's red Close button on the window banner. Instead of closing the preferences window, the entire damned application shuts down.
Poster

Changed status to: 'Open'

Changed status to: 'Open'
Poster

Added subscriber: @chapp-ai

Added subscriber: @chapp-ai
Poster

Now also when restarting Blender (frequent when trying to close the preferences window and forgetting that it closes the application) the preferences window is always open by default and is titled "Blender" instead of "User Preferences". My first day using this application and already thinking of dubbing it "Blunder" based on its user-interface and poor (low-contrast) default color theme.

Now also when restarting Blender (frequent when trying to close the preferences window and forgetting that it closes the application) the preferences window is always open by default and is titled "Blender" instead of "User Preferences". My first day using this application and already thinking of dubbing it "Blunder" based on its user-interface and poor (low-contrast) default color theme.
jensverwiebe was assigned by mont29 8 years ago
Owner

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges
Owner

I cannot reproduce this on my Macbook Pro Retina (Late 2013). ;)

I cannot reproduce this on my Macbook Pro Retina (Late 2013). ;)
Poster

Let's see if a screen capture will work...

Screen_Shot_2014-11-01_at_12.33.53_PM.jpg

Okay, can't tell from the submission form, but presuming the submitted comment will show the screenshot, you will notice that both the User Preferences window and the Application window are both titled "Blender". Clicking the red close circle on the preferences window closes Blender (all windows). Command-w with the preferences window active closes the application. Selecting "Close" from the Windows menu closes the application. I cannot get the preferences window to close without closing Blender.

Let's see if a screen capture will work... ![Screen_Shot_2014-11-01_at_12.33.53_PM.jpg](https://archive.blender.org/developer/F121104/Screen_Shot_2014-11-01_at_12.33.53_PM.jpg) Okay, can't tell from the submission form, but presuming the submitted comment will show the screenshot, you will notice that both the User Preferences window and the Application window are both titled "Blender". Clicking the red close circle on the preferences window closes Blender (all windows). Command-w with the preferences window active closes the application. Selecting "Close" from the Windows menu closes the application. I cannot get the preferences window to close without closing Blender.
Poster

Btw, this is on a MacBook Pro Retina Late 2014, the newest model released.

Btw, this is on a MacBook Pro Retina Late 2014, the newest model released.
Collaborator

My only guess is you once saved your startup file with the preferences open in background what mudlles the window order, should not happen though.
Try delete your startup.blend and create a new one.
Should not have any sideefect as you described though, must lookat ....

Jens

My only guess is you once saved your startup file with the preferences open in background what mudlles the window order, should not happen though. Try delete your startup.blend and create a new one. Should not have any sideefect as you described though, must lookat .... Jens
Poster

Agreed, should not happen. Where would that startup.blend file be located at?

Agreed, should not happen. Where would that startup.blend file be located at?
Poster

I found the startup.blend file down in Application Support and deleted it, as well as userpref.blend but there is still a bug in the application. Upon launching Blender the preferences no longer auto-displays but then opening User Preferences, making changes, saving the settings, then closing the preferences still quits the application instead of just closing the preferences window. (Were preferences tested before releasing the program?)

I found the startup.blend file down in Application Support and deleted it, as well as userpref.blend but there is still a bug in the application. Upon launching Blender the preferences no longer auto-displays but then opening User Preferences, making changes, saving the settings, then closing the preferences still quits the application instead of just closing the preferences window. (Were preferences tested before releasing the program?)
Owner

So far you are the only one with this problem. We are very supportive and try to help you out, but your "Blender is bad" attitude is not helpful.

So far you are the only one with this problem. We are very supportive and try to help you out, but your "Blender is bad" attitude is not helpful.
Collaborator

Very odd, cannot still nort reproduce.
Do you perhaps use the "seperate spaces" option ?

Very odd, cannot still nort reproduce. Do you perhaps use the "seperate spaces" option ?
Poster

I have no idea what "separate spaces" is. Simply downloaded the latest release of Blender (first-time download), moved the folder to Applications, launched the program, opened User Preferences, changed Input Select from "Right" to "Left", clicked "Save User Settings", then closed (or rather tried to close) the preferences window (doesn't matter how - all have the same effect: red close button, command-w, Windows->Close) and the application quits. If I thought Blender was bad then I wouldn't have downloaded it to try it out after hearing so many good things about it, but the user-interface is overwhelming compared to similar applications and having the application quit when closing preferences is pretty much a blocking issue.

I have no idea what "separate spaces" is. Simply downloaded the latest release of Blender (first-time download), moved the folder to Applications, launched the program, opened User Preferences, changed Input Select from "Right" to "Left", clicked "Save User Settings", then closed (or rather tried to close) the preferences window (doesn't matter how - all have the same effect: red close button, command-w, Windows->Close) and the application quits. If I thought Blender was bad then I wouldn't have downloaded it to try it out after hearing so many good things about it, but the user-interface is overwhelming compared to similar applications and having the application quit when closing preferences is pretty much a blocking issue.
Owner

That is odd, and probably would have been noticed by others already ( we have many users on Mac OS). You can try to re-download it, and start it from the download folder or so, although I don't think that this should cause any problem.

(Btw was just referring to your "Blunder" comment. :D )

That is odd, and probably would have been noticed by others already ( we have many users on Mac OS). You can try to re-download it, and start it from the download folder or so, although I don't think that this should cause any problem. (Btw was just referring to your "Blunder" comment. :D )
Collaborator

Technically it looks like something is odd with window id's. I made Blender only allow immediate close if
a: nothing was changed and b: the window to be closed is the last mainwindow open.
Although prefs is a special case it seems.
Else you would get a quit dialog. Have no clue why this should be different in your environment atm.

Very odd noone can reproduce this.

Technically it looks like something is odd with window id's. I made Blender only allow immediate close if a: nothing was changed and b: the window to be closed is the last mainwindow open. Although prefs is a special case it seems. Else you would get a quit dialog. Have no clue why this should be different in your environment atm. Very odd noone can reproduce this.
Collaborator

Can you test following: open your blender and do move the default cube and then try close either prfs or mainwindow again.
Does it give a dialog ?

Can you test following: open your blender and do move the default cube and then try close either prfs or mainwindow again. Does it give a dialog ?
Poster

Guess I'm just special? :)

Launched Blender and moved the default cube then closed the application, got prompted that some changes are not saved. Quit anyway.

Launched Blender and moved the default cube, then opened User Preferences, made no changes and immediately clicked the red close circle to close the preferences window, got prompted that some changes are not saved and whether I want to quit anyway.

Don't know why, but it's as though Blender (or OS X) is believing the parent application window to be closing rather than the child preferences window.

Guess I'm just special? :) Launched Blender and moved the default cube then closed the application, got prompted that some changes are not saved. Quit anyway. Launched Blender and moved the default cube, then opened User Preferences, made no changes and immediately clicked the red close circle to close the preferences window, got prompted that some changes are not saved and whether I want to quit anyway. Don't know why, but it's as though Blender (or OS X) is believing the parent application window to be closing rather than the child preferences window.
Collaborator

Yes, thats indeed a fact, but why the heck ?

It looks as just klicking the close button does not make the window keywindow, checking.
Also i'am sure on 10.8 where it was developed the behavoiur was different.

hmmm

Yes, thats indeed a fact, but why the heck ? It looks as just klicking the close button does not make the window keywindow, checking. Also i'am sure on 10.8 where it was developed the behavoiur was different. hmmm
Collaborator

Okay looked through all code now and tested circumstances.
Still cannot reproduce. I know we have cornercases when closing
an non-keywindow, for i had to use a trick to not close without dialog
when the main application window will be closed.
To plain closing a window there must be > 1 window and it is not
objectAtIndex:[windowsList count] - 1, this trick avoids mainwin closing
due it was moved to index 1 when another win gets frontmost.

I cannot see atm. why this should behave any different for you.
Very odd.

Also cannot use NSWindow isMainWindow anymore it seems, its now deprecated
but this would not help too much as i checked mainwin does not explicitely mean its
the app mainwin ( in nib, which we don't use in Blender ) Sigh ...

Okay looked through all code now and tested circumstances. Still cannot reproduce. I know we have cornercases when closing an non-keywindow, for i had to use a trick to not close without dialog when the main application window will be closed. To plain closing a window there must be > 1 window and it is not objectAtIndex:[windowsList count] - 1, this trick avoids mainwin closing due it was moved to index 1 when another win gets frontmost. I cannot see atm. why this should behave any different for you. Very odd. Also cannot use NSWindow isMainWindow anymore it seems, its now deprecated but this would not help too much as i checked mainwin does not explicitely mean its the app mainwin ( in nib, which we don't use in Blender ) Sigh ...
Collaborator

Forgot explanation of your situation:

			case GHOST_kEventWindowClose:
				// check for index of mainwindow as it would quit blender without dialog and discard
				if ([windowsList count] > 1  && window->getCocoaWindow() != [windowsList objectAtIndex:[windowsList count] - 1]) {
					pushEvent( new GHOST_Event(getMilliSeconds(), GHOST_kEventWindowClose, window) );
				}
				else {
					handleQuitRequest(); // -> quit dialog
				}
				break;

windowcount is > 1 ( mainwin + prefs = 2 )
&& prefs is active thus at index0 ergo allowd to push close event.
The else clause calling handleQuitRequest() should nevver happer here.

Forgot explanation of your situation: ``` case GHOST_kEventWindowClose: // check for index of mainwindow as it would quit blender without dialog and discard if ([windowsList count] > 1 && window->getCocoaWindow() != [windowsList objectAtIndex:[windowsList count] - 1]) { pushEvent( new GHOST_Event(getMilliSeconds(), GHOST_kEventWindowClose, window) ); } else { handleQuitRequest(); // -> quit dialog } break; ``` windowcount is > 1 ( mainwin + prefs = 2 ) && prefs is active thus at index0 ergo allowd to push close event. The else clause calling handleQuitRequest() should nevver happer here.
Poster

Here's where it gets a little more odd. I rebooted my Mac and the problem is gone. It's now working the way I would expect it to. Weird that if something was quirked in the OS only Blender was affected by it rather than other apps as well. Sorry for taking up so much of your time. Now I get to watch some tutorials and try figuring out this beast.

Here's where it gets a little more odd. I rebooted my Mac and the problem is gone. It's now working the way I would expect it to. Weird that if something was quirked in the OS only Blender was affected by it rather than other apps as well. Sorry for taking up so much of your time. Now I get to watch some tutorials and try figuring out this beast.
Collaborator

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
jensverwiebe closed this issue 8 years ago
Collaborator

I could think of something muddled in the GL system.
Anyway, the issue was not plausible right hand.
Closing this as "unique issue caused by uncommon system state".

Jens

I could think of something muddled in the GL system. Anyway, the issue was not plausible right hand. Closing this as "unique issue caused by uncommon system state". Jens
Sign in to join this conversation.
No Label
Interest/Alembic
Interest/Animation & Rigging
Interest/Asset Browser
Interest/Asset Browser Project Overview
Interest/Audio
Interest/Automated Testing
Interest/Blender Asset Bundle
Interest/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
Interest/Eevee & Viewport
Interest/Freestyle
Interest/Geometry Nodes
Interest/Grease Pencil
Interest/ID Management
Interest/Images & Movies
Interest/Import/Export
Interest/Line Art
Interest/Masking
Interest/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
Interest/Python API
Interest/Render & Cycles
Interest/Render Pipeline
Interest/Sculpt, Paint & Texture
Interest/Text Editor
Interest/Translations
Interest/Triaging
Interest/Undo
Interest/USD
Interest/User Interface
Interest/UV Editing
Interest/VFX & Video
Interest/Video Sequencer
Interest/Virtual Reality
legacy module/Animation & Rigging
legacy module/Core
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Sculpt, Paint & Texture
legacy module/User Interface
legacy module/VFX & Video
legacy project/BF Blender: 2.8
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/OpenGL Error
legacy project/Retrospective
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
Module › Animation & Rigging
Module › Core
Module › Development Management
Module › Eevee & Viewport
Module › Grease Pencil
Module › Modeling
Module › Nodes & Physics
Module › Pipeline, Assets & IO
Module › Platforms, Builds, Tests & Devices
Module › Python API
Module › Render & Cycles
Module › Sculpt, Paint & Texture
Module › Triaging
Module › User Interface
Module › VFX & Video
Platform/FreeBSD
Platform/Linux
Platform/macOS
Platform/Windows
Priority › High
Priority › Low
Priority › Normal
Priority › Unbreak Now!
Status › Archived
Status › Confirmed
Status › Duplicate
Status › Needs Information from Developers
Status › Needs Information from User
Status › Needs Triage
Status › Resolved
Type › Bug
Type › Design
Type › Known Issue
Type › Patch
Type › Report
Type › To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#42464
Loading…
There is no content yet.