Dear MC developpers,
Please consider the following usabilty enhancements, which I am sure will save a lot of time and hassle for many users:
- Signals status change:
It would be much better to have check boxes to switch signals status. Right now it is a bit of a pain to have to select them one by one, then click on "Status" button, with the risk of clicking on the "Remove" button by mistake (which is just next to it). Here is attached a sample of how it could look like:
- True/Fulse Inputs:
Currently one has to manually type "True" or "False" to change the status of a conditional input, which is a bit of a pain when testing back and forth several combinations. It would be much easier to just click on a button to switch state of the parameter. This could be for instance with a radio button as illustrated below:
I made related PM requests. Please vote !
https://www.multicharts.com/pm/public/m ... es/MC-2171
https://www.multicharts.com/pm/public/m ... es/MC-2170
Thank you
Usability enhancements
Re: Usability enhancements
Please be aware that many other great feature request regarding usability are not successfully implemented.
U can easily multi-select the studies & systems and set their status on/off at once. Don't take this hostile but you can program these true/false options as an int (0/1). This way they are easily to optimize as well ... You just have to open your mind and think a little bit beyond the problems you have.
Regards
Ben
U can easily multi-select the studies & systems and set their status on/off at once. Don't take this hostile but you can program these true/false options as an int (0/1). This way they are easily to optimize as well ... You just have to open your mind and think a little bit beyond the problems you have.
Regards
Ben
Re: Usability enhancements
Thank you bensat your your feedback. You probably know the difference between a workaround and an enhancement. Obviously we can always deal with things as they are, but why would you refrain from improving them, specially when the cost/benefit might be ok ?
Multi-select studies/signals does not avoid the extra click on the Status button. Do that 50 times a day, with a mistaken click on the Remove button once in a while, and you'll probably want to "think a bit beyond" the current interface.
Same for the True/False inputs: since they exist in many existing codes, why not trying to better deal with them without rewriting them ?
Multi-select studies/signals does not avoid the extra click on the Status button. Do that 50 times a day, with a mistaken click on the Remove button once in a while, and you'll probably want to "think a bit beyond" the current interface.
Same for the True/False inputs: since they exist in many existing codes, why not trying to better deal with them without rewriting them ?