Modal input feature appears to be missing from 2.70 test builds #38743

New Issue

Sam Brubaker · 2014-02-21T17:17:54+01:00

Sam Brubaker commented

2014-02-21 17:17:54 +01:00

Version: 2.70 test release (win 64)

I apologize if this is already known, but it appears that this feature is not implemented in the 2.70 test builds that were released yesterday. When transforming an object by entering a value, the header display does look different, but does not accept any math operators or letters. To reproduce, try transforming an object in the 3d view by entering a simple math expression (2*6, 100+73, etc.).

Did this feature simply not make it into this particular build, or am I using it incorrectly? Again, I apologize if this is the case.

Version: 2.70 test release (win 64) I apologize if this is already known, but it appears that [this feature ](http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.70/UI#Modal_Numinput) is not implemented in the 2.70 test builds that were released yesterday. When transforming an object by entering a value, the header display does look different, but does not accept any math operators or letters. To reproduce, try transforming an object in the 3d view by entering a simple math expression (2*6, 100+73, etc.). Did this feature simply not make it into this particular build, or am I using it incorrectly? Again, I apologize if this is the case.

Sam Brubaker commented

2014-02-21 17:17:54 +01:00

Changed status to: 'Open'

Sam Brubaker commented

2014-02-21 17:17:54 +01:00

Added subscriber: @rocketman

Sam Brubaker commented

2014-02-21 17:22:44 +01:00

There is a note on the wiki:

Did not touch to how values are shown in header when modal numinput is not enabled (would do that in another commit), so this is still quite inconsistent.

This might explain the results I'm getting. But if Modal numinput is not enabled, where exactly does one enable/disable it?

There is a note on the wiki: *Did not touch to how values are shown in header when modal numinput is not enabled (would do that in another commit), so this is still quite inconsistent.* This might explain the results I'm getting. But if Modal numinput is not enabled, where exactly does one enable/disable it?

Thomas Dinges commented

2014-02-21 18:08:10 +01:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2014-02-21 18:08:10 +01:00

Try the "=" key, there were recent changes here.

Thomas Dinges commented

2014-02-21 18:08:42 +01:00

Added subscriber: @mont29

Thomas Dinges commented

2014-02-21 18:08:42 +01:00

@mont29: Time to update the wiki /release logs I guess. :)

Bastien Montagne was assigned by Thomas Dinges

2014-02-21 18:09:43 +01:00

Sam Brubaker commented

2014-02-21 19:06:11 +01:00

Thank you, @dingto. I tried the "=" key but it has no effect.

Thomas Dinges commented

2014-02-21 19:14:58 +01:00

See here for recent changes. https://developer.blender.org/rB32d6f853f33c107fd3afbff7845269c41c2686d4

Henrik Aarnio commented

2014-02-22 02:39:08 +01:00

Added subscriber: @hjaarnio

Henrik Aarnio commented

2014-02-22 02:39:08 +01:00

Does not seem to work on layout that doesn't have a dedicated = key, but = is produced with eg shift-0.

Bastien Montagne commented

2014-02-22 11:47:23 +01:00

Yeah, known issue with non-EN keyboards, we do have many shortcuts that do not work... :/

Will add '*' in addition to '=', should do the trick for now (and update release notes of course, too).

Yeah, known issue with non-EN keyboards, we do have many shortcuts that do not work... :/ Will add '*' in addition to '=', should do the trick for now (and update release notes of course, too).

blender-admin commented

2014-02-22 12:08:39 +01:00

This issue was referenced by blender/blender-addons-contrib@c1cdce364b

This issue was referenced by blender/blender-addons-contrib@c1cdce364bc1f122db2ce72a15fc969a375d0f4e

blender-admin commented

2014-02-22 12:08:39 +01:00

This issue was referenced by c1cdce364b

This issue was referenced by c1cdce364bc1f122db2ce72a15fc969a375d0f4e

Bastien Montagne commented

2014-02-22 12:09:43 +01:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue