setEditable(false) in 1.1.8 does not shade TextComponent as did 1.1.6

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Duplicate
    • Priority: P2
    • None
    • Affects Version/s: 1.1.8
    • Component/s: client-libs
    • x86
    • windows_98



      Name: krT82822 Date: 05/01/99


      Bug 4182554 is similar but I am unsure if they are requesting the 1.1.8 behavior? It appears to me that uneditable TextComponents would want to be easily identified as being uneditable. Setting the color independently is possible but the intuitive approach should be the default - why have every program in every instance invoke two methods when one should suffice?
      (Review ID: 57715)
      ======================================================================

            Assignee:
            Eric Hawkes (Inactive)
            Reporter:
            Kevin Ryan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: