New answers tagged desktop-application
Look this tutorial for validation rules: http://wpftutorial.net/DataValidation.html The error message is inside the tooltip, but you can put the error message in a storyboard and animate it. Like showing up only, if an error occured. This is how inline validation is used at websites. Don't ask me how I did it. It's some years ago, but feasible. I think ...
WPF has a great Validation framework. I find it to be intuitive with many options. And it conserves screen space. It uses borders and optional tool tips. Programming is not that easy but it is nice for programmers as it enforces rules at the data layer. The business / data layers does not have to care how enforcement of those rules bubble to the UI ...
The main problem seems to be the amount of buttons not the kind of their appearance. The goal is, that your user finds the right button fast. A visual hint would help, but if the icons ar not self-explanatory, the users would have to learn their meaning which only helps if they use this form often. Anyway, each time the user has to scan all buttons to find ...
There is no rhyme or reason as to the layout here. Consider grouping your buttons into logical groupings, perhaps emphasizing some over others based on priority of use.
It might be best to try an alternative layout for the buttons rather than icons as knowing what an icon means outside of the staple well known ones, for things like Play, Pause, Save, Delete etc. is not always easy. It might be more worthwhile spending time on a good translator and using something like i18n for internationalisation.
If all the buttons are required to be shown show them as a drop down menu with actions(like the hamburger icon and the drop down using it) and if not change the buttons contextually(which is easy with the basic JS)
With a slight adjustment, Grubermensch solution covers cases where you want something to kick in even if 0, for example for discounts. Start with [ 0 ] instead of [ 1 ] and I think all cases are covered.
Step back and consider the problem The goal of this interface appears to be to create a series of contiguous ranges (1-50, 51-99, 100-Inf), and then assign a unit price over each range. The key concept here is contiguous. You are currently allowing the user to input both the beginning and end of the range on each line. This is an example of ...
Totally agree with RogerAttrill's answer, but I would suggest you to give to the user a more intuitive option. I think the best option is what MS Word do when you select a text, a visual-friendly contextual menu (notice that the menu fades out when you take your mouse away from it): I would add something like this (of course you can put other options on ...
You don't need to provide only one solution! Escape should do it - to complete the line at the last point added. So should double click - to add a point and finish the line And yes, right click can mean other things, which is why right click should bring up a menu to resolve any ambiguity as to what the click actually means: eg. Finish Add point and ...
Top 50 recent answers are included