[Closed] Wishlist for callbacks: Please list yours
Hi everybody
I want to assemble a wishlist of callbacks everyone would like implemented in maxscript. I’m curious to know what your needs are, and what is or isn’t being addressed. I figure by focusing on a narrow topic, it will be easier to document and discuss.
Just note, I am not doing this in any official capacity, since I’m at home typing this up. But I think if the topic is concise enough, and thoroughly discussed that it can do nothing but aid in the future development of Max.
My two
when a selectionset is created
when a selectionset is deleted
The notifications would return the names that were created or deleted.
Chris J.
Hey Chris (what’s up?),
Can I ask for a callback which returns true when say the user is double clicked in the viewport? If so, I will have to make a small list of callbacks which would be really useful.
Thanks man,
Light
I think that callbacks for subobject operations would be nice, like:
when a sub object is selected (return bitarray of selection)
when a sub object is moved (no return)
and things along a similar vein.
Much more events about ANIMATIONS.
When a key has been
- moved
- deleted
- added.
MOUSE
- right click from mouse
- middle click from mouse
- mouse scroll
- button4 and button5 clicked
- mouse moved (it would be nice if it could also return the direction the mouse has been moved in).
As many events as possible about things happening on EDITABLE_POLY Object.
- extrude started/stopped
- bridge started/stopped
- chamfer started/stopped
- more like the above
- subobject level changed
/Andreas
Are you aware that a change handler will recognize sub-object selection changes, and transforms? For instance:
function OnSelectionChanged =
(
print "in OnSelectionChanged"
format " Sub-Object-Level: %
" subobjectLevel
)
function OnGeometryAltered =
(
print "in OnGeometryAltered"
)
when select objects changes obj do
(
print obj
OnSelectionChanged()
)
when geometry objects changes obj do
(
OnGeometryAltered()
)
Take an editable poly, select some faces and starting moving them around and you will see it.
However, I agree with you, that for consistency, perhaps there could be a callback to handle these situations.
I think callbacks for mouse clicks and key presses would be very useful, like: when the user double clicks, right clicks, presses C, etc. A callback that would return the SO the mouse is over (or closest for edges/verts), and the SO (left/right/middle) mouse button clicked on would be great too. Also a callback returning the SOs being moved by a relative and absolute coordinates.
I can think of some more later.
Thanks,
Light
Yes, i know about that. But the change handler isn’t that much fun to work with. It’s also a broad callback for lots and lots of things.
/A
A series of callbacks for use DURING rendering would be great. Right now it’s impossible to do update a scene per frame while rendering unless you do a messy workaround. I know that’s more to do with how max caches before render, but it would be nice.
A callback that registers when you’re typing in the maxscript window would also be wonderful!