Mac OSX notifications on multiple Blender instances #45076

Closed
opened 2015-06-14 14:32:18 +02:00 by Francesco Siddi · 12 comments

When opening 2 or more instances of Blender on OSX, at end of any operation connected to the Notification Center (render, comp, bake), a notification is displayed even if Blender is in the foreground.

When opening 2 or more instances of Blender on OSX, at end of any operation connected to the Notification Center (render, comp, bake), a notification is displayed even if Blender is in the foreground.
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @fsiddi

Added subscriber: @fsiddi

Added subscribers: @jensverwiebe, @Sergey

Added subscribers: @jensverwiebe, @Sergey
Martijn Berger was assigned by Sergey Sharybin 2015-06-15 11:58:14 +02:00

The thing is, we don't check for foreground/background processes in our side, seems it's all being decided by the notification center itself.

@jensverwiebe do you have any inputs here?

Assigning to Martijn since he's kinda maintaining OSX now. But i'm open for helping him with investigation.

The thing is, we don't check for foreground/background processes in our side, seems it's all being decided by the notification center itself. @jensverwiebe do you have any inputs here? Assigning to Martijn since he's kinda maintaining OSX now. But i'm open for helping him with investigation.
Member

All is like it should be !

If you have 2 instances of blender open and the rendering instance ! is in foreground, notification will
not show up. I will only occure if the rendering instance is in bg. So what ?

I propose to reject this issue.

Jens

All is like it should be ! If you have 2 instances of blender open and the rendering instance ! is in foreground, notification will not show up. I will only occure if the rendering instance is in bg. So what ? I propose to reject this issue. Jens
Author
Member

My problem is that the the notification shows up for the fg blender.

  • Open Blender
  • Open another Blender on top and press F12
  • Notification appears

On your setup this does not happen?

My problem is that the the notification shows up for the fg blender. - Open Blender - Open another Blender on top and press F12 - Notification appears On your setup this does not happen?
Member

Nope
This is how notifications work normally: they inform you about bg tasks.
I tried different instancing too: 2 times started blender from binary in dock - strted blender 2.74 and 2.75rc -> always correct behaviour
Perhaps check your notification center for settings, but 'am not aware you could affect this.

Or it is a bug in your OSX version ?

Jens

Nope This is how notifications work normally: they inform you about bg tasks. I tried different instancing too: 2 times started blender from binary in dock - strted blender 2.74 and 2.75rc -> always correct behaviour Perhaps check your notification center for settings, but 'am not aware you could affect this. Or it is a bug in your OSX version ? Jens
Member

Removed subscriber: @jensverwiebe

Removed subscriber: @jensverwiebe

Added subscriber: @brecht

Added subscriber: @brecht

I can't reproduce this bug either, Blender 2.76-rc2 on OS X 10.10.5.

So either it's fixed already, or we need details about the exact Blender / OS X version and how you open Blender. Is this using two different Blender applications or a single application, are they opened by from the dock, finder, terminal, .. ?

I can't reproduce this bug either, Blender 2.76-rc2 on OS X 10.10.5. So either it's fixed already, or we need details about the exact Blender / OS X version and how you open Blender. Is this using two different Blender applications or a single application, are they opened by from the dock, finder, terminal, .. ?
Author
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Author
Member

Hey there, thanks for looking into this.
I just checked again and it seems fixed!
For the record, I was launching Blender via the terminal. I'm closing the issue, unless there is a more formal procedure to follow.

Hey there, thanks for looking into this. I just checked again and it seems fixed! For the record, I was launching Blender via the terminal. I'm closing the issue, unless there is a more formal procedure to follow.
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
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
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
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
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
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 Info 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
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#45076
No description provided.