Skip to main content
Closed

Possibility to select no rows in a treelist

Related products:Windows GUI
Henk Nicolai
Frank Wijnhout
Peter Verwijs
Raj Rozendaal
Robbert van Tongeren
+5
  • Henk Nicolai
    Henk Nicolai
  • Frank Wijnhout
    Frank Wijnhout
  • Peter Verwijs
    Peter Verwijs
  • Raj Rozendaal
    Raj Rozendaal
  • Robbert van Tongeren
    Robbert van Tongeren
  • Jop ter Horst
    Jop ter Horst
  • Marco van Brenk
  • Dennis van Leeuwen
    Dennis van Leeuwen
  • Ricky
    Ricky
  • André Noorlander
    André Noorlander

Good day,

We would like to have a possibility exists to select no row in a treelist (webGUI)

 

Explanation:

Right now, when a user opens a screen, the first row is selected by default.

This is not always desirable for our customers. Let me explain this in a use case:

 

Project structure: a tree list

The + button at the left side creates a new project one level beneath of the project that is currently selected.

However, because the first row is selected by default, it is never possible for customers to create a project on the same level as the project that is currently selected. 

Kind regards,

Ronald

Did this topic help you find an answer to your question?

6 replies

Jasper
Superhero
  • 678 replies
  • April 2, 2021

Hi Ronald,

The user interfaces are designed to always have a selected row when data is available, so this would be quite a challenge. Is it an option to provide separate tasks for adding children and siblings of the selected node?


Mark Jongeling
Administrator
Forum|alt.badge.img+23
Updated idea status NewNeeds feedback

Forum|alt.badge.img
  • Author
  • Apprentice
  • 5 replies
  • April 6, 2021

Good morning,

Thank you for your response. At first sight your suggestion sounds like a proper solution to us.

However, I think I need to elaborate a bit more on the use case.

At this moment we are trying to improve our CTA buttons. This also implies the creation of a '’project'’. Therefore, we would like to achieve this (or maybe even a better alternative):

What we want to achieve

As you may have noticed, there is merely one button in the picture. This is our first CTA button in the software. A user has to create a project, otherwise not so much is possible for him/her. This is also why we only want one button over here. We would like the design to be clear and concise. Two button is of course an alternative, but it is not preferable in this case.

To us it is preferable that this one button allows a user to create siblings and children, depending on the conext.

Is a project or a child project selected? → Then another child (one level below the selected one) is created.

Is nothing selected? → Then a project is created on the highest level. Reason: having to click on another project before adding a project on the same (highest) level is not really userfriendly. This is why we would like to enable the user to create a project on the highest level when nothing is selected.

I hope this has clarified my use case better.

Kind regards,

Ronald

 

 


Mark Jongeling
Administrator
Forum|alt.badge.img+23
Updated idea status Needs feedbackOpen

Jeroen van den Belt
Administrator
Forum|alt.badge.img+9

Unfortunately, this idea has not received enough votes. Because we want to keep the focus on ideas that are in high demand, we are closing this idea.


Jeroen van den Belt
Administrator
Forum|alt.badge.img+9
OpenClosed

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings