2.8: Python API: Application Timers do not work in registered scripts #62050

New Issue

Closed

opened 2019-02-28 15:45:14 +01:00 by Marc · 7 comments

Marc commented

2019-02-28 15:45:14 +01:00

System Information
Operating system: Windows 7, 64bit
Graphics card: N/A

Blender Version
Broken:
2.80, dd9cedddae, win64

Short description of error

Application Timers are not fired if they are registered in a registered script.

Exact steps for others to reproduce the error

Just use the following example in a registered script and check "Auto run scripts" in preferences.

import bpy

def every_2_seconds():
    print("Hello World")
    return 2.0

print('main')
bpy.app.timers.register(every_2_seconds)

Expected behavior

Hello World is printed every 2 seconds.

Actual behavior

Hello World is not printed (but the script run as I see main in the console).

Further information

Example works as expected if run with "Run Script" button.

**System Information** Operating system: Windows 7, 64bit Graphics card: N/A **Blender Version** Broken: 2.80, dd9cedddae69, win64 **Short description of error** Application Timers are not fired if they are registered in a registered script. **Exact steps for others to reproduce the error** Just use the following example in a registered script and check "Auto run scripts" in preferences. ``` import bpy def every_2_seconds(): print("Hello World") return 2.0 print('main') bpy.app.timers.register(every_2_seconds) ``` **Expected behavior** Hello World is printed every 2 seconds. **Actual behavior** Hello World is not printed (but the script run as I see `main` in the console). **Further information** Example works as expected if run with "Run Script" button.

Marc commented

2019-02-28 15:45:14 +01:00

Author

Added subscriber: @schlamar

Added subscriber: @schlamar

Jacques Lucke commented

2019-02-28 15:54:56 +01:00

Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke

Jacques Lucke self-assigned this 2019-02-28 15:54:56 +01:00

Jacques Lucke commented

2019-02-28 15:54:56 +01:00

Member

Does the problem still exist when you make the timer persistent?

Does the problem still exist when you make the timer persistent?

Marc commented

2019-02-28 16:01:25 +01:00

Author

The example works with persistent=True. Though, I still think this is unexpected behavior.

The example works with persistent=True. Though, I still think this is unexpected behavior.

Jacques Lucke commented

2019-02-28 16:02:40 +01:00

Member

I know, fixing it right now.

I know, fixing it right now.

blender-admin commented

2019-02-28 16:07:56 +01:00

This issue was referenced by 921c37bfa3

This issue was referenced by 921c37bfa3108708cb6c2a6cd7c1b1a588be2d74

Jacques Lucke commented

2019-02-28 16:09:56 +01:00

Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Jacques Lucke closed this issue

2019-02-28 16:09:56 +01:00

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

3 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#62050

No description provided.