Oliver, On Tuesday, 2016-11-22 10:09:04 +0100, you wrote:
> ... > I think most users > ignore those buttons because they do not really understand what they are > good for. I think, ignoring buttons one does not really understand what they are good for, is wise to do. But that can't be really a reason for not pro- viding those buttons at all. In particular after you're already provid- ing these buttons for a few other features. And apart from that: the problem of users not understanding what a part- icular button is good for always boils down to deficiencies in the doc- umentation, be it online documentation, offline documentation, tool tips or balloon help. So it's clearly OUR responsibility to prevent users from not understanding any buttons. > And if you use them you can get easily confused by the > consequences. That's what's always happening to me anyway. Some software, in partic- ular software by Microsoft has plenty of what we used to call "surprise factors" :-) > Adding similar buttons to activity coloring and adding a new aspect > (global or project based) This was part of my question. If either "global" or "project based" is a new aspect, users should be clearly told what "all tracks" is really referring to, global or project based. And what will happen when green is specified for "all tracks" and red for "this track only", or what will happen to new tracks? This has to be documented. You as a developer are one of those persons having excessively read the "executable documentation" and thus you know. But normal users are not expected to have studied the program sources and thus they have to be clearly told in the documentation. Sincerely, Rainer ------------------------------------------------------------------------------ _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
