In my oppinion Terry's way is still more clean, since, by coincidence, it might happen for someone to just write !! in a button text name, and then again what happens if someone wants to write that on purpose? (Im not a double exclamation lover myself, but we shoulndt restrict to those guys the opportunity to have double !! buttons..) hehe. Well jokes aside I think it would lead to less confussion to just separate that as a new comand as Terry suggested, but well its only my view. =) Glad you have you back hope you enjoyed some great travelling!
On Saturday, June 29, 2013 2:55:01 PM UTC+2, Edward K. Ream wrote: > > On Thu, Jun 20, 2013 at 7:10 AM, Fidel Pérez <[email protected]<javascript:> > > wrote: > >> Problem: Buttons cant show literal caption, making them ugly. If the user >> try to make a button with literal caption of a node containing '{}' or more >> strange characters, it will not work. >> >> I would like to suggest an extra attribute to the function: >> >> createIconButton (self,text,command,statusLine,bg=None,kind=None) >> >> > Terry's way is best so far, but there is another way. > > Suppose we add a convention to the text argument. If it has a certain > form, say A!!B, then A becomes the button text and B becomes the command > name. > > What do you think? > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
