In a Windows Form, where should the Add / Remove buttons go when you have a header record with single attribute children, as below? Should the "Child Items" label be above the list box?
Update:
Trying to apply DripDrop's suggestion:
5
- In an optimum situation, there probably shouldn't be a separate dialog for adding an entity in the first place, so the question is moot.Jawa– Jawa2014-12-04 23:14:11 +00:00Commented Dec 4, 2014 at 23:14
- In an optimum situation you would not be using WinForms. Remove should not even be enabled if an item is not selected.paparazzo– paparazzo2014-12-05 00:09:32 +00:00Commented Dec 5, 2014 at 0:09
- @Jawa it's just an input box. Could have been a textbox on the main form, I just found it easier.John– John2014-12-05 15:57:40 +00:00Commented Dec 5, 2014 at 15:57
- @Blam WinForms is what we're using in my company right now. What would you use, WPF?John– John2014-12-05 15:58:06 +00:00Commented Dec 5, 2014 at 15:58
- This is a more of a developer talking but WPF is a league up. I can not only do more with less code but with the controls and how they layout deliver a better UX. In WPF everything is a content control so you can put an image or text in a button. You have styles to modify presentation and keep things consistent. WPF has a higher resolution and more colors.paparazzo– paparazzo2014-12-05 16:03:16 +00:00Commented Dec 5, 2014 at 16:03
Add a comment |
1 Answer
What you have is fine, and I would!dent move it. What I would suggest is that you group the list and the buttons together, so the user immediately knows that they are together.
EDIT: Yes, that looks great.
- Please see my update with a new screen shot. Is that what you had in mind? A group box? I think it looks better...John– John2014-12-05 14:39:35 +00:00Commented Dec 5, 2014 at 14:39