Page MenuHome
Create Task
Maniphest T78913

Regular error in <string> and invalid token
Closed, ResolvedPublic
Actions

Description

System Information
Operating system: W10 Profesional V10.0.18363
Graphics card: NVIDIA GeForce GTX 1080 Ti Pilot : 26.21.14.3200

Blender Version
Broken: version: 2.83.2, branch: master, commit date: 2020-07-09 05:50, hash: 239fbf7d936f, type: Release

system-info.txt22 KBDownload

Short description of error
Regular error in <string> and invalid token

Exact steps for others to reproduce the error
Modeling in edit mode.
Add bevel modify.
Change Segments 1 to 2.
Change Outer : Sharp to Path.
Select edges (poly edge) and in N Pannel, modify 0.00 from man bevel weight to 0.10.
Pop error <string>
Look images from console.


Blend file
Decors-science.blend993 KBDownload

Related Objects

Event Timeline

Alexandre LAB (geeks) created this task.Jul 14 2020, 11:45 AM
Jacques Lucke (JacquesLucke) changed the task status from Needs Triage to Needs Information from User.Jul 14 2020, 5:24 PM
Jacques Lucke (JacquesLucke) added a subscriber: Jacques Lucke (JacquesLucke).

This does not look like a bug to me. Looks like you typed invalid numbers into the input field.

If that is not the bug you mean, please attach a short screen recording that shows what you do exactly.

Alexandre LAB (geeks) added a comment.Jul 14 2020, 5:30 PM

A bad game leads to this result.

At first glance, it does when I type "0 ..". If the entry stops at "0 .." when I press enter the arrows appear.

Perhaps then, it is necessary to protect the field with a clearer message (genre: you have not entered the correct number). "<string>", for me I don't mean anything!

Campbell Barton (campbellbarton) mentioned this in rB565d7f75ccfe: UI: improve errors when evaluating a number button fails.Jul 27 2020, 1:02 PM
Campbell Barton (campbellbarton) closed this task as Resolved.Jul 27 2020, 1:04 PM
Campbell Barton (campbellbarton) claimed this task.
Campbell Barton (campbellbarton) added a subscriber: Campbell Barton (campbellbarton).

While I don't think this is a bug, the errors weren't very good, committed improvements to them rB565d7f75ccfe: UI: improve errors when evaluating a number button fails.