The undo icon button will not function in Mcam X

[johnT]

Just below the create function in the menu bar, the Undo and Redo buttons will not highlight and therefor will not function. They are however highlighted when in the process of creating geometry but after the enter button is clicked the highlight goes away./ Any suggestions?

[88Matt]

you can only undo if there is a history to track. you cannot undo any solid manipulation right now which has been reported and addressed already.

[Ray H.]

ya, that button works totally fine.

possibly OE, what does your interactive prompt say?

[johnT]

Ok, it most likely is O/E, but you have to create the geometry and click or enter. When you do that the Undo icon is not highlighted, but when you click again as if to continue creating the same geometric feature the Undo will highlight. I don't remember it being like that in Version 9.

But thanks for the help.

[HEAVY METAL]

JOHN i have had same problem . Ill be working with a file and out of the blue the undo and redo will be greyed out and wont come back on. i just took it as another bug issue

[Jeremy Haage from MCAM NorthWest]

When an entity is live (light blue / cyan) undo/redo are not accessible. When you hit Enter to make it live you should then be able to access undo/redo at that point. If I understand you correctly though when you hit Enter and the entity becomes fixed (no longer cyan) you can't undo/redo?

[Thad]

quote:

---

When an entity is live (light blue / cyan) undo/redo are not accessible. When you hit Enter to make it live you should then be able to access undo/redo at that point.

---

OK, which is it? You're confusing me, Jeremy.

 

Thad

[HevyMetl]

Ok it just happened to me and I had to shut MC down and restart it to get it working again. I was trying to undo a line creation I just completed. I was totally out of the line create funtion. The undo/redo buttons were greyed out. The undo/redo selection under edit was likewise greyed out. I shut MC down and restarted the same file and all is working fine now.

 

Has this been logged as a bug?