【转】How do I use MDGModifier so I can get reliable Undo/Redo?

 

I've had several logistical problems with MDGModifiers, exclusively with its ::undo() and ::redo() mechanism. After much trial and error on the topic I've come to the following conclusions:

There are times when you may have to perform a ::doIt() in the middle of your MDGModifier modification so the scene state is valid for further operations. For example, if you use MDGModifier::create(), you will need to ::doIt() so this node exists if you wish to perform any edits using a class other than MDGModifier (finding an MPlug on your new node, for instance).

Do not continue to use a MDGModifier object after you have called its ::doIt() method!

My "Golden Rule" for MDGModifier is now the following:

"Execute ::doIt() as soon as I need to update the state of the scene, then immediately allocate another MDGModifier for further edits. Continue, rinse, repeat."

All allocated MDGModifier nodes go onto a stack. The stack in undone in FILO order, and redone in FIFO order.

 

 

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值