-
-
Notifications
You must be signed in to change notification settings - Fork 0
PLUGIN: Global - Mode switching can accidentally make OP fail #25
Copy link
Copy link
Open
Labels
C issueC-class issues don't explicitly prevent actions from being performed.C-class issues don't explicitly prevent actions from being performed.MildLow Severity issues that only causes light visible issues or inconvenience within its class.Low Severity issues that only causes light visible issues or inconvenience within its class.more testing neededThis issue needs more people to test its parameters, scope or repeatability.This issue needs more people to test its parameters, scope or repeatability.
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
C issueC-class issues don't explicitly prevent actions from being performed.C-class issues don't explicitly prevent actions from being performed.MildLow Severity issues that only causes light visible issues or inconvenience within its class.Low Severity issues that only causes light visible issues or inconvenience within its class.more testing neededThis issue needs more people to test its parameters, scope or repeatability.This issue needs more people to test its parameters, scope or repeatability.
=needs more testing=
highlights3, frames1, frames2, op14, op8, op12:
has:
In THEORY, if you accidentally leave the object in the wrong mode, the next operator might fail. We'll want to test this and see, but in terms of best practices something safer would be to define
Something like that =TEST THIS=