Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: UIDefaults key? Date: Wed, 06 Aug 2014 14:38:59 -0400 Organization: A noiseless patient Spider Lines: 46 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 6 Aug 2014 18:39:02 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="bd4e1cba8d8592bec5d5ed9e4537fbfd"; logging-data="29820"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/jcZT7yVWB94ZKHNMlt6LN" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 In-Reply-To: Cancel-Lock: sha1:lSNsikKQRrMHMujGwlAUj9VVZRA= Xref: csiph.com comp.lang.java.programmer:29579 On 8/6/2014 2:17 PM, Knute Johnson wrote: > On 8/6/2014 10:31, Eric Sosman wrote: >> On 8/6/2014 12:25 PM, Knute Johnson wrote: >>> JComponent has a method, getUIClassID(), to return the UIDefaults key >>> for the ComponentUI subclass. A JTextField returns a key of >>> TextFieldUI. A typical subclass is >>> javax.swing.plaf.metal.MetalTextFieldUI. >>> >>> All the interesting details in the UIDefaults however use keys such as >>> TextField.foreground, TextField.border, TextField.margin etc. Is there >>> any way to get the prefix, TextField, from the component other than >>> stripping the UI off the end of the UIClassID? >> >> Climbing the class hierarchy from MetalTextFieldUI up to >> BasicTextFieldUI, I find the method >> >> /** >> * Fetches the name used as a key to lookup properties through the >> * UIManager. This is used as a prefix to all the standard >> * text properties. >> * >> * @return the name ("TextField") >> */ >> protected String getPropertyPrefix() { >> return "TextField"; >> } >> >> ... which sort of looks like what you're after. (But I haven't >> researched any other delegate classes, so it's possible they're >> different.) >> > > I think that is the answer Eric but I just not sure how to get there > from here yet :-). Sorry: I somehow thought you already had your hands on an instance of the ComponentUI subclass -- But now I think you've got nothing but a JComponent object. Also, I see that the method I stumbled upon is defined for some ComponentUI subclasses, but not for all. Perhaps it's time to take a step back and think about the eventual goal rather than about one particular (and possibly unworkable) route toward it. What problem are you trying to solve? -- esosman@comcast-dot-net.invalid