it might sound weird but i need a trick when some operation should be undoadle but not redoable. something like after undo immediately goes another “empty” operation that wipes redo history…
any ideas?
i feel like i’m missing an easy way to achieve this behavior
This is probably too heavyweight of a solution…
max undo
gc light:false
gc light:false is the same as gc()
it flushes all undo stack. i need to flush only redo history
Over-write the redo buffer by doing a new action?
max undo
undo (
b = box()
delete b
)
this is the right direction… but i don’t want to see this “dummy” undo action in undo/redo stack
max undo
clearUndoBuffer()
?
no… my goal is to clear only REDO history. like when you do any max operation after UNDO. but i want this operation be not going in both undo and redo stacks.
in short – if used is udoing my operation it clears redo stack
I’m way out of my league here…but I’ll try…what about this:
x = currently selected object
do something
undo
clearSelection()
reselect x – this pair clears out the redo stack but clears out only ONE entry out of the undo stack
Bob’s your uncle ?
sorry no codes…you know me…
it’s completely incomprehensible to me how you do such masterly MCG, and at the same time claim that you don’t do the coding?
there is must be something to change – either start coding, or break with MCG ;)… so as not to mislead the people
ok ok…been VEXing it in Houdini…and even tidbits of Python…
thing is…now that i’m into Houdini, i have 2 options at my disposal…VOPs…which is ‘visual programming’ like MCG…and VEX which is scripting like mxs
and guess what…99.99% of the time…i choose VEX…
I’m glad it’s not only me that find this as well! Trying to digest an MCG made by Vu is much harder than even reading DenisT code!
if it helps anyone in your class to understand…yes it’s true i know very very little mxs, matrices, mathematical wizardy…tho i have to confess i was
always top of the class in maths when i was a little grasshopper (by top, i mean my average for all tests year after year was…100%).
Now, when i set off to build an MCG, doesnt matter if the long term goal was to build the Taj Mahal or an outhouse (Aussie shithouse)…the IMMEDIATE
goal is always…can i put down a simple line, a box, a sphere whatever, just get something visible to look at onto the screen…then next immediate goal, can i
clone what i just did to be say a line of those boxes…then next…can i clone them up to form a wall…and so on. It might sound heretic to some…but i actually
don’t have a well defined plan, i make things up as i go, It’s always done in small baby steps’, the tortoise always wins…
And i use ’ constants’ all the time…because they eliminate noobism…ie if you plug in variable after variable , you’re gonna trip up sooner or later…while
if you test with constants like 0, 1, 5, 10 (or floats)…etc…you can’t go wrong…only when you’ve got it all working then substitute the vars in.
anyway, don’t know how you mxs guys/gals do it but…just get ‘something’ onto the screen ASAP to look at…once you can see it it’s easier to work with
rather than some abstract thing in the head that you can’t interact with…a lot of times i don’t understand things i simply do ‘something’ ridiculous and observe
the results…THEN draw conclusion from the observed evidence…while if i try to be ‘smart’ and ‘postulate’ and conclude…well that won’t work…who’s to say my
theory is 100% correct ? That’s enough from me…gotta go take a dump in the old ricketty outhouse…
can you believe that just two hours ago I told people in the class about the ways to develop the 3DS MAX tools and brought you as an example of just highly skilled using of MCG without any using of mxs or sdk? there are coincidences!
I’m trying to think of any max action which doesn’t create an Undo record… I know there are some…
MassFX bake all ? it even warns you are you sure…really really sure ? coz you can’t undo (hence the Unbake button)