THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 28/10/2012 at 13:55, xxxxxxxx wrote:
Q1: I am wanting a GUI element to only exist while a user is modifying a very specific parameter. This element is used as a temp guide while adjusting, then it should go away. So, in the Message method, I read of a CHECKUPDATE which is great so far. However unlike COMMAND data (button), the DATA argument passes None instead of telling me what parameter is being called. Like with a button it tells you which button is being hit so you can do something with it.
So at this point, I know when a user is modifying ANY parameter but not WHICH parameter. Any ideas how to get to the point I can know when a parameter is being modified AND which one it is? I can check the last cycle for a change in value of course, but then when it settles, the result would be False even if the user still keeps the mouse_button down.
Q2: I have on screen GUI displays that should be like a HUD and overlay whatever is going on in the eidt view. Meaning my elements should have no 3D values what-so-ever in the viewport, only float on top in strictly 2D space. I've built my widgets with various draw parameters being called in the Draw pass. However, my elements disappear behind objects in the scene as the camera moves around the world. I've messed with the Z space stuff quite a bit and set depth and all that and nothing seems to make a difference. It looks like in the C++ SDK I can use SceneHook, but that doesn't appear to be implemented in Python. Any advice as how to get my GUI stuff to live on the very "surface" of the viewport and always show despite what is going on in the scene?