Page MenuHome

Unable to UNDO, moving to layers require manual clicking on the OK button, which isn't what it used to be
Closed, InvalidPublic

Description

System Information
Windows 10
GTX 970

Blender Version
Blender 2.76 RC Hash:c586e30
Worked: 2.75a

Short description of error

  1. Blender does not UNDO in object mode
  1. When object is selected, pressing M and then a number key doesn't confirm the "move to layer #" operation, manual confirmation by clicking on the OK button or Press Enter key is required.
  1. This is already fixed, but when I was using 2.75a, when trying to move an object to another layer, the number key doesn't work at all. Though it used to work within same version.

Exact steps for others to reproduce the error
I imported my 2.75a user preference and key configuration to 2.76RC. (I did get rid of some key mapping that I don't use often to something I do use often)

Details

Type
Bug

Event Timeline

Brent Lio (remotecrab131) raised the priority of this task from to Needs Triage by Developer.
Brent Lio (remotecrab131) updated the task description. (Show Details)
Brent Lio (remotecrab131) set Type to Bug.

Bastien Montagne (mont29) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Sep 22 2015, 9:09 AM

Please avoid reporting several bugs at once.

  1. You most likely disabled 'Global Undo' in Userpreferences, Editing tab (or set its steps to 0).
  1. Please try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
  1. No need to report it if already fixed…

Please avoid reporting several bugs at once.

  1. You most likely disabled 'Global Undo' in Userpreferences, Editing tab (or set its steps to 0).
  2. Please try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
  3. No need to report it if already fixed…

you are correct, by turnning on Global undo, it fixed my issue #1 and #2 all at once. I have no idea why, but thank you for the help.

Though I apologize about reporting it as bugs, since all i could have done is just turn on Global control and restart the computer. :P

Will make sure it's not user error next time.

Bastien Montagne (mont29) claimed this task.

And we can close the report then. :)