Skip to main content
9 events
when toggle format what by license comment
Mar 15, 2012 at 8:53 comment added Bart Gijssens I think you need to look at this case by case. Are you displaying a message in a messagebox? If yes, what style of messagebox? If no, what type of message is it? It seems there is no general rule for all messages. In all cases the UX Interaction Guidelines are a good place to look for the correct guideline.
Mar 15, 2012 at 7:26 comment added krishnajay So does it mean all messages should've a main instruction and it shouldn't be in multiple sentences. If there is a need for multiple sentences, is it supposed to be split? Moreover does it apply for contextual messages such as the ones displayed below the input fields
Mar 15, 2012 at 7:00 history edited Bart Gijssens CC BY-SA 3.0
added 175 characters in body
Mar 15, 2012 at 6:57 comment added Bart Gijssens You are right. Mind that this is only for the "main instruction", not for the "supplemental instructions". Most of the time, when using standard messageboxes, there is not main instruction.
Mar 15, 2012 at 6:51 comment added Bart Gijssens @krishnajay: what is your source? Do you have a reference for that?
Mar 14, 2012 at 18:48 comment added krishnajay Here is the rule... //Don't include final periods if the instruction is a statement. If the instruction is a question, include a final question mark.//
Mar 14, 2012 at 18:45 comment added krishnajay Refer msdn.microsoft.com/en-us/library/windows/desktop/aa511267.aspx for windows messages
Mar 14, 2012 at 7:02 history edited Bart Gijssens CC BY-SA 3.0
added 4 characters in body
Mar 14, 2012 at 6:53 history answered Bart Gijssens CC BY-SA 3.0