public inbox for
 help / color / mirror / Atom feed
Subject: Re: about boolean types
Date: Wed, 12 Jan 2000 00:10:00 -0000	[thread overview]
Message-ID: <E128IrG-00075a-00@horse> (raw)
In-Reply-To: <>

>Vladimir Tsyshevsky wrote:
>> Hi,
>> many parameters in gtk+ have formal integer type, but are booleans
>> really. Nevertheless, all they are mentioned as integer in Scheme
>> prototypes. I think, if is not very difficult to introduce 'bool' type
>> in guile-gtk to fix this problem.
>Boolena types are already included on guile-gtk. Eg,
>(define-func gtk_widget_set_sensitive
>  none
>  ((GtkWidget widget)
>   (bool sensitive)))
>However bool expects scheme values (#t #f) instead of C.

True. But I accidently bumped into one of the following
definitions, in which the parameters still defined as having type 'int'
(the definitions below are corrected already):

(define-func gtk_aspect_frame_new
  ((string label)
   (float xalign)
   (float yalign)
   (float ratio)
   (bool obey_child)))

(define-func gtk_aspect_frame_set
  ((GtkAspectFrame aspect_frame)
   (float xalign)
   (float yalign)
   (float ratio)
   (bool obey_child)))

(define-func gtk_progress_set_show_text
  ((GtkProgress progress)
   (bool show_text)))

(define-func gtk_progress_set_activity_mode
  ((GtkProgress progress)
   (bool activity_mode)))

(define-object GtkPlug (GtkWindow)
  (GdkWindow socket_window)
  (bool same_app)))

Vladimir V. Tsychevski
senior expert

                  Jet Infosystems
Krasnoproletarskaya 6,		Tel. (+7 095) 972-1182
Moscow 103006, Russia		Fax  (+7 095) 972-0791
Any opinions or recommendations herein are those of
the author and not of his computer.

      reply	other threads:[~2000-01-12  0:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-11  6:13 Vladimir Tsyshevsky
2000-01-11  8:37 ` Ariel Rios
2000-01-12  0:10   ` ÷ÌÁÄÉÍÉÒ ãÉÛÅ×ÓËÉÊ [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E128IrG-00075a-00@horse \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).