Names of ITOs are getting trunca...

JSN

Having to work with ITOs a lot again and it reminds me everytime of those things … in a file with lots of ITOs (even if they are well named and structured, which is truly not always the case) it feels like looking through a tiny keyhole. Due to the lack of ITO-management features, truncated information, a tiny dropdown menu, missing navigation features (< and >) lots of repetive tasks and clicks are necessary … even if someone has three screens on his desk the software would not allow him to unleash the full potentials and clearly limits us here.

E.g. think about deleting many ITOs in a smc file with lots of ITOs which have been created over the time. It feels like a punishment as I always have to select the next one from the drop down menu first once one gets removed as it always automatically jumps back to the list. Please make this better or at least add more methods to the API so that I can at least build my own ITO-Management-View!

Pasi Paasiala

@JSN Thanks for making this issue clear with the illustration! I’ve reported an enhancement request for this.

JSN

Any chances to see improvements on this matter with the upcoming release?

JSN

@JSN said in Names of ITOs are getting trunca...:

Not sure where I have mentioned it before but as switching through lots of ITOs is, … well, like it is, I would definitely favor buttons to at least be able to quickly switch between the previous and the next ITO …

Would have tinkered it togehter myself but the above explains what’s keeping me from it …

An addtionaly method in the interface for setItoDefinition would be highly appreciated. Calculate only seems to switch to a given <ItoDefinition> if there really was a recalculation performed … so my workaround to improve the usability for working with lots of ITOs is not really satisfying me so far.

… not in real life, but for sure when it comes to software engineering, project management and cat years.

JSN

@JSN said in Names of ITOs are getting trunca...:

An addtionaly method in the interface for setItoDefinition would be highly appreciated. Calculate only seems to switch to a given <ItoDefinition> if there really was a recalculation performed … so my workaround to improve the usability for working with lots of ITOs is not really satisfying me so far.

At the very least, please allow us to improve the usability ourselves.