Move to layer doesn't accept number key input #45055

New Issue

JA 12 · 2015-06-13T01:38:16+02:00

JA 12 commented

2015-06-13 01:38:16 +02:00

Ubuntu 14.04, Gnome 3 Classic, Nvidia graphics

Broken: 2.75 087c82e
Worked: 2.74 000dfc0

Scene layer selection is not accessible with number or numpad keys anymore when moving an object to another scene layer.

Exact steps for others to reproduce the error

Open a recent build of 2.75, default settings
Select object, M to move and number key to select the corresponding scene layer
Nothing happens. Scene layer selection was expected

Ubuntu 14.04, Gnome 3 Classic, Nvidia graphics Broken: 2.75 087c82e Worked: 2.74 000dfc0 Scene layer selection is not accessible with number or numpad keys anymore when moving an object to another scene layer. **Exact steps for others to reproduce the error** 1. Open a recent build of 2.75, default settings 2. Select object, M to move and number key to select the corresponding scene layer 3. Nothing happens. Scene layer selection was expected

JA 12 commented

2015-06-13 01:38:16 +02:00

Changed status to: 'Open'

JA 12 commented

2015-06-13 01:38:16 +02:00

Added subscriber: @ja12

JA 12 commented

2015-06-13 01:43:02 +02:00

Also a question about reporting: should we select most suitable/multiple projects in the project field when reporting? Like for instance, BF Blender, BF Blender: regressions, User interface might be suitable options for this.

Julian Eisel commented

2015-06-13 01:46:16 +02:00

Added subscriber: @JulianEisel

Julian Eisel commented

2015-06-13 01:46:16 +02:00

AFAIK this was fixed with a9d3f663d3 so should work fine again. You can test tomorrow using the buildbot builds .

Re projects - you don't need to bother with this, we'll handle that if needed.

AFAIK this was fixed with a9d3f663d3 so should work fine again. You can test tomorrow using the [buildbot builds ](https://builder.blender.org/). Re projects - you don't need to bother with this, we'll handle that if needed.

Julian Eisel commented

2015-06-13 01:47:24 +02:00

Changing to Incomplete since it would be good to get confirmed if it's working again.

JA 12 commented

2015-06-13 01:57:13 +02:00

That was fast. Thank you.

I'll test with the new build as it becomes available but I'm sure it will work alright. I probably reported this too early this time but others were getting same behaviour and I wasn't sure how long it had been like that.

That was fast. Thank you. I'll test with the new build as it becomes available but I'm sure it will work alright. I probably reported this too early this time but others were getting same behaviour and I wasn't sure how long it had been like that.

David Radford commented

2015-06-13 22:44:36 +02:00

Added subscriber: @DavidRadford