Python Operator.report does not show in status bar when overriding context #97284

New Issue

RedMser · 2022-04-12T18:20:35+02:00

RedMser commented

2022-04-12 18:20:35 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09

Blender Version
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-04-08 22:50, hash: 502d16e667
Also broken all the way back to 2.79.

Short description of error
An operator's report() call does not show a message in the status bar or info editor when the operator is not invoked by the user. This is expected.
However, overriding the execution context to 'INVOKE_DEFAULT' or even a specific area does not make it work either. This part seems like a bug.

Simple reproduction file
no_reports.blend

Run the script and notice Warning reports in the stdout but not in the status bar
Same when saving the .blend file
As expected, running the operator manually (F3 search) works as intended
- Alternatively, modify the invoke function to require user input (such as via context.window_manager.invoke_confirm), then the timer/save handler calls also work
The override_context makes no difference here

Reproducing from a blank startup file

Create an operator that calls self.report on execute
Call the operator from e.g. a timer or application handler
Even when overriding the context, the report only shows in stdout, but not in the user interface

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09 **Blender Version** Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-04-08 22:50, hash: `502d16e667` Also broken all the way back to 2.79. **Short description of error** An operator's `report()` call does not show a message in the status bar or info editor when the operator is not invoked by the user. This is expected. However, overriding the execution context to `'INVOKE_DEFAULT'` or even a specific area does not make it work either. This part seems like a bug. **Simple reproduction file** [no_reports.blend](https://archive.blender.org/developer/F12998423/no_reports.blend) - Run the script and notice Warning reports in the stdout but not in the status bar - Same when saving the .blend file - As expected, running the operator manually (F3 search) works as intended - Alternatively, modify the `invoke` function to require user input (such as via `context.window_manager.invoke_confirm`), then the timer/save handler calls also work - The override_context makes no difference here **Reproducing from a blank startup file** - Create an operator that calls `self.report` on execute - Call the operator from e.g. a timer or application handler - Even when overriding the context, the report only shows in stdout, but not in the user interface

RedMser commented

2022-04-12 18:20:35 +02:00

Added subscriber: @RedMser

Pratik Borhade commented

2022-04-13 06:09:09 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Pratik Borhade commented

2022-04-13 06:09:12 +02:00

Added subscriber: @PratikPB2123

RedMser commented

2022-04-13 20:14:44 +02:00

This was added in 2299d674f4 so quite a while ago.
Removing the flag if-check fixes the issue, but not sure how to detect if it's application timers/handlers doing the report (in comparison to operators calling other operators, which is what this fix seems to intend).

This was added in 2299d674f4 so quite a while ago. Removing the flag if-check fixes the issue, but not sure how to detect if it's application timers/handlers doing the report (in comparison to operators calling other operators, which is what this fix seems to intend).

Demeter Dzadik commented

2023-01-03 16:08:50 +01:00

Added subscriber: @Mets

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Python Operator.report does not show in status bar when overriding context #97284