[Pharo-project] Issue 3878 in pharo: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText
Status: New Owner: ---- New issue 3878 by fernando...@gmail.com: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText http://code.google.com/p/pharo/issues/detail?id=3878 It's sent by the TextEditor, to ask the morphs for permision to change the contents. Attachments: enableTextChange.1.cs 2.2 KB
Updates: Status: FixProposed Labels: Milestone-1.3 Comment #1 on issue 3878 by marcus.d...@gmail.com: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText http://code.google.com/p/pharo/issues/detail?id=3878 (No comment was entered for this change.)
Comment #2 on issue 3878 by stephane...@gmail.com: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText http://code.google.com/p/pharo/issues/detail?id=3878 can you deprecate enableTextChange because this class is used by other clients?
Comment #3 on issue 3878 by fernando...@gmail.com: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText http://code.google.com/p/pharo/issues/detail?id=3878 (No comment was entered for this change.) Attachments: enableTextChange.2.cs 2.8 KB
Comment #4 on issue 3878 by stephane...@gmail.com: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText http://code.google.com/p/pharo/issues/detail?id=3878 tx !
Updates: Status: Closed Comment #5 on issue 3878 by stephane...@gmail.com: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText http://code.google.com/p/pharo/issues/detail?id=3878 in 13118 :)
participants (1)
-
pharo＠googlecode.com