Re: CAPI push button borders

Martin Simmons <[email protected]>
Newsgroups gmane.lisp.lispworks.general
Message-ID <[email protected]>
There is an undocumented mapping from keywords to the Cocoa numbers using this
alist:

'((:rounded .           1)
  (:regular-square .    2)
  (:thick-square .      3)
  (:thicker-square .    4)
  (:shadowless-square . 6)
  (:circular .          7)

  (:disclosure .    5)
  (:texture-square . 8)
  (:help-button . 9)
  (:small-square . 10)
  (:texture-rounded . 11)
  (:round-rect . 12)
  (:recessed . 13)
  (:rounded-Disclosure . 14)

  (:no-border  . :no-border)
  )

:no-border make it call setBordered: with false, otherwise it calls
setBezelStyle: with the number.

-- 
Martin Simmons
LispWorks Ltd
http://www.lispworks.com/



>>>>> On Fri, 13 Feb 2026 13:58:56 +0000, John DeSoi (as john at desoi dot dev) said:
> 
> I did find there are integer values in the COCOA package for these. You can find them with the Symbol Browser using "bezel". For example, COCOA:NS-ROUNDED-BEZEL-STYLE = 1.
> 
> It would be really nice if you could just pass these to the :BEZEL-STYLE initarg, but that gives an error for any that I tried.
> 
> John DeSoi, Ph.D.
> 
> 
> > On Feb 13, 2026, at 2:53 AM, MK (as mkuuskan at yahoo dot com) <[email protected]> wrote:
> > 
> > 
> > 
> >> On 12. Feb 2026, at 16.14, John DeSoi <[email protected]> wrote:
> >> 
> >> Is there a way to get the integer constant value from the name using the objc bridge, e.g. "NSBezelStyleCircular".
> > 
> > At least I don't know any way to do that. Maybe there isn't one...
> > 
> 
> 
> _______________________________________________
> Lisp Hug - the mailing list for LispWorks users
> [email protected]
> http://www.lispworks.com/support/lisp-hug.html
> 

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
[email protected]
http://www.lispworks.com/support/lisp-hug.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.