--- Operating System, Graphics card ---
OS X 10.7.5, ATI Radeon HD 4850
--- Blender version with error, and version that worked ---
Latest revs fail, I don't know since when, sorry.
In 2.64.9 (r52350) the wheel mouse works fine, the f6 adjusting doesn't.
--- Short description of error ---
The Loop Cut and Slide command in Edit mode doesn't allow to choose the amount of cuts, nor to tweak the action after confirmation.
--- Steps for others to reproduce the error (preferably based on attached .blend file) ---
No need for attached file, it happens also in New scene (factory settings)
- open New scene
- enter Edit mode
- CTRL+R for Loop Cut and Slide over the cube
- spinning mouse wheel does nothing (you can't choose number of cuts)
- confirm
- f6 (and tool options panel) is grayed out, not editable.
thank you, paolo
Description
Event Timeline
Actually, they seems two distinct issues, the wheel mouse one maybe is related to others in Lion with Magic mouse wheel: http://projects.blender.org/tracker/index.php?func=detail&aid=28092&group_id=9&atid=498
Thanks, paolo
If mouse wheel does not work for you for operations like zoom in/out no doubt the root of the issue #28092 and would suggest you switching all the feedback to original report. If wheel works fine in other areas of blender -- then it'll be separated issue but not sure what causes it.
As for F6 -- not a bug, just it's not possible to redo this operation.
As workaround you could use numeric input instead of wheel to define number of cuts you need.
If you use magic mouse? Then I can check on this. The magic mouse now doesn't do wheel events anymore. So in some tools with hardcoded wheel input it's not working.
Blender has code to mimic wheel events for this (and trackpads) still, will check it.
@Sergey,
thank you for the hint, I wasn't aware that numeric inputs were working, that's a good workaround.
Currently the wheel fully works only in 3dview, in other 2d views only partially. I will follow issue #28092.
As for the f6, I understand.
@Ton,
yes I use Magic mouse.
Then this issue can be closed I think, it all comes down to the issue #28092.
Thank you
paolo