Page MenuHome

Operator Slider in 3D View Gets Interpreted as Backspace in Text Editor
Closed, DuplicatePublic

Description

System Information
Operating system: Microsoft Windows 10 Pro
Graphics card: NVidia GeForce GTX 970

Blender Version
Broken: 2.80 beta, 2018-12-28, a7c5f4f20657
Worked: I didn't have this problem with the latest stable release, 2.79b

Short description of error
While creating a simple add-on I came across this bug. 10-20% of the time when I run my script and try to use it, I get the issue. When changing the value of a slider in the window created in the bottom left of the 3D view by dragging with the cursor, the text editor cursor is moved back to the last position it made an edit, and backspaces are rapidly inserted at the end of the line that the cursor just moved to. Undo isn't aware of these changes, so you'd better remember what was just deleted or make frequent backups. Also, when it happens, the object added by the add-on gets added many times, instead of the slider just adjusting a value of the original object. Simply running the script again (after restoring anything that was deleted by the bug) will usually fix it.

Exact steps for others to reproduce the error
Based on the default startup. Try to make an add-on based on the "Addon Add Object" template, run the script either with the button or with Alt+P quite often, every time using your new addon to add your new object, and messing with the sliders. Within a few attempts you should have come across the bug.

Details

Type
Bug

Event Timeline

I don't know why the hash links to something, it's just the one from the blender splash screen.

I noticed the too. You don’t even have to use a operator. Sometimes just using the undo in 3D View makes it add, delete, or delete the entire text. It’s nearly impossible to use the text editor currently. My guess is it’s the undo/redo system, which seems to be causing a lot of issues.

Here’s a issue I reported.

https://developer.blender.org/T58217

I'll close this as duplicate of T58217 . However, if the issue still remains after that one has been solved, please let us know.