What might be handy is some kind of “useTooltipIfEmpty” property. Then the end user would not need to parse the text to eliminate the “call to action” from the real data before working with it, t hen adding the “call to action” back when done.
Bob S > On Jul 2, 2015, at 08:28 , Richard Gaskin <ambassa...@fourthworld.com> wrote: > > Peter Haworth wrote: > >> So my technique of setting showname to false if the text is empty is the >> only way round this? >> >> Also, you can have a label for an option menu with empty text. Try setting >> the text of an option menu to empty, then use the message box to set its >> label to some value. > > With the OS X HIGs not nearly as complete as they used to be I can no longer > find the relevant section on this, but I believe most HIGs suggest that we > avoid giving the user the impression the control may be broken by replacing > empty items with some explanation of why it's empty, or perhaps a disabled > item simply saying "None". > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
