unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: GNU G-Golf 0.8.0-rc-2 available for testing
Date: Fri, 22 Dec 2023 01:52:57 -0300	[thread overview]
Message-ID: <20231222015257.3d471e2f@tintin> (raw)
In-Reply-To: <CA+XASoUeiiS=Rjw4H=c0uAg-THNNknk8h6-T9w0EURjBgCYacQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]

Hi Aleix,

> ...
> Anyways, guile-cairo is fine going back to stable 3.0.9.

Ok, so just to make sure, now both the gtk4/simple-paintable.scm and
gtk4/animated-paintable.scm examples work fine on 'your' platform as
well?

> > - drawing-widget.scm, peg-solitaire.scm.
> > ...

> The issue seems to be here:

> (define-vfunc (snapshot-vfunc (self <drawing-widget>) snapshot)
>   #t)

a-

And does that works? It should, but/and obviously not drawing
anything, but no bug/no crash?

b-

Can you try, in a repl:

  ,use (g-golf)
  (gi-import-by-name "Gtk" "Widget")
  $5 = #<<gobject-class> <gtk-widget> 7fe9c1681d20>

  (gi-import-by-name "Gtk" "init")
  $6 = #<<function> 7fe9c1555360>
  
  (gtk-init)

  (graphene-rect-alloc)
  $7 = #<pointer 0x560e4855d1c0>

	;; below you'd substitute the $7 appropriately if for some
        ;; reason you happen to have a diff repl var $<id> flow,
        ;; you need the result of (graphene-rect-alloc)

  (graphene-rect-init $7 0 0 50 50)
  $8 = #<pointer 0x560e4855d1c0>

c-

Let's see, but if all the above work, can you poste the error you get
with no modification of the upstream version of the example, or does it
segfault?

If no segfault, in a repl:

  (load "<your-golf-repo-path>/examples/gtk-4/drawing-widget.scm")
  (main '())
  => error

  ,bt #:width 1000 #:full? #t

If it segfault, we'd need to get a gdb backtrace - would that be
possible?

David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-12-22  4:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  3:50 GNU G-Golf 0.8.0-rc-2 available for testing David Pirotte
2023-12-01 17:51 ` Aleix Conchillo Flaqué
2023-12-02  0:10   ` David Pirotte
2023-12-04  4:15     ` Aleix Conchillo Flaqué
2023-12-04  4:16       ` Aleix Conchillo Flaqué
2023-12-05  4:21         ` David Pirotte
2023-12-05  4:14       ` David Pirotte
2023-12-09 20:49         ` Aleix Conchillo Flaqué
2023-12-21  8:44         ` Aleix Conchillo Flaqué
2023-12-22  4:52           ` David Pirotte [this message]
2023-12-22  7:01             ` Aleix Conchillo Flaqué
2023-12-22  7:34               ` Aleix Conchillo Flaqué
2023-12-22 23:22               ` G-Golf- [subject changed] cairo based examples fail in homebrew David Pirotte
2023-12-22 23:43                 ` David Pirotte
2023-12-22 23:55                 ` Aleix Conchillo Flaqué
2024-01-01  2:12                   ` David Pirotte

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=20231222015257.3d471e2f@tintin \
    --to=david@altosw.be \
    --cc=aconchillo@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).