Feature Request: Initialize Indicator
awilder last edited by
I use the "Initialize" feature a lot on actors, and it's challenging to track and manage because I can't see at a glance if Initialize is enabled or not. Currently, the only way to tell is if you double-click the parameter's name, and look at the pop-up window to see if the Initialize box is checked.How about adding a visual indicator next to the parameter if "initialize" is enabled? It could be a very simple dot or checkmark just after the parameter name... anything that shows there's a hidden setting that's active. I'm guessing this would be fairly easy to implement, and would save a TON of time in programming and troubleshooting.Thanks!
primaldivine last edited by
Great idea. I second this one. :)
Kathmandale last edited by
Really great idea. I third it!
Bill Cottman last edited by
Keve last edited by
I just wanted to post this feature request.
Glad somebody came up with the same idea earlier on! :–)
I really miss this feature very much.
Maybe tint the initialized value?
How about adding a visual indicator next to the parameter
I agree, this is a great idea!
There is the control ID number in the parameter setting window that places a visual indicator as an extension on the actors input, so a visual indicator of the initialize parameter would be helpful. I think it would also be helpful to think about redesigning the basic Isadora actor block or UI so that all of these parameter settings are visible all of the time and can be checked and manipulated directly on the actor or a persistent parameter panel. The parameters like 'Scale min' and 'Scale max' have such a significant impact on how an individual actor functions. I know it might be too much going on the face of it, and it would disrupt the current Ui/UX, but it is also a great design challenge to think about.
deflost last edited by
mark last edited by mark
How about adding a visual indicator next to the parameter if "initialize" is enabled? It could be a very simple dot or checkmark just after the parameter name... anything that shows there's a hidden setting that's active. I'm guessing this would be fairly easy to implement, and would save a TON of time in programming and troubleshooting. Thanks!
Does anyone have a clever idea on how to do this visually? Because it is an ongoing thing people also want is to be able to see if there is scaling going on. I have played around with bold and/or underlines for the param titles, different shapes for the port, etc. and nothing I have tried has been terribly satisfying visually. Either it's too subtle or a it makes a mess of the patch because it ends up cluttering things up too much. If you have an idea on how to make such thing visually clear without cluttering up the user interface too much, I'd love to see a drawing of what you think would do the trick.
My idea: a ring around the port. White for initialize red for scaling and a mix of both.
@Michel is on to something. I assume you have tried the simplest and most obvious - marking parameter changes by color indicator of the text label and underline? I don't think that is too subtle personally. The flying labels might also work with a toggle to hide them
CitizenJoe last edited by
I was going to suggest changing the colour of the port, but I think that @bonemap's idea of the text is better. It might also work to change the colour of the black background? For me that's the most obvious and uncluttered.
jfg last edited by
I find that the color change of the text (3 colors for scale, init and both) and the proposol of Michel are the best one. The others take too much place and won't work in all actors.
CitizenJoe last edited by
@bonemap Oh for goodness sakes, I only saw the bottom half of example, showing the text in colour!
changing the color of the port will interfere with the concept of the green dot if a port is mutable.
I just wanted to see what it would be like.
I would probably appreciate seeing all of the scaling, initialize and control information like this with the option to toggle hide/show. The ‘int’ columns should be ‘ini’.
The defaults are also important to access - so it would not replace the pop-up default properties inspector .
Oh for goodness sakes
You know design challenges take a bit of process. So don’t mind me visualising these alternatives. This challenge has been hanging around for a while and I don’t know if it is getting any closer to a solution.
mark last edited by
Thanks for these suggestions everyone. I've got other tasks today, and probably won't be able to look this over carefully until later or first thing tomorrow. All ideas are welcome at this point if anyone else wants to make an attempt. Thanks @bonemap for the idea of showing it all. I guess that could be useful for a temporary examination, though for sure we wouldn't want that to be the norm. One thing to think about is mouse over: that simply pointing the mouse at something shows you the detail -- which you actually have now with the tooltips, but it could become something quicker to show and more detailed.
I really like your third image, with a shortcut to toggle this is a really powerfull way to showcase what is going on with an actor without messing with userthemes / etc. I clearly see that it has a scale, it is mutated to a Int type and has a init value of 1. Clean, to the point and fits with the excisting UI. Dont know about the output side..
I rather not have an mouseover to showcase this kind of criticial information when I working on a patch, I rather have a way to toggle a small UI and see some labels on my screen with each actor so I can quickly diagnose the problem and get on. Init values are mainly during 'crunch' times a pain and the shows that many of us are making are a bit to complex to go each single actor to see what is going on.
Maximortal last edited by
@bonemap I think that adding boxes can be confising..lets image a 3d particles acotor with all that boxes...it became a grid of numbers. I tink that colors as suggested before can be better ( personally I like a lot the two colored dots )