From: Clemens Ladisch <clemens@ladisch.de>
To: Ru Vuott <vuott@yahoo.it>
Cc: alsa-devel@alsa-project.org
Subject: Re: Can ALSA invoke a Callback ?
Date: Mon, 29 Aug 2011 11:12:44 +0200 [thread overview]
Message-ID: <4E5B580C.4060503@ladisch.de> (raw)
In-Reply-To: <1314566910.38637.YahooMailClassic@web29620.mail.ird.yahoo.com>
Ru Vuott wrote:
> you wrote:
> > These functions are designed to be used with poll(); to use
> > them with Gambas, extract the file descriptors and their event masks
> > from the pfds array and call GB.Watch() with these values.
>
> << GB.Watch() is an internal interpreter API. You can't use it in Gambas code.>>
Then how do you get access to the snd_seq_* functions? I assumed that
you have some module that offers a Gambas API on top of the ALSA C API;
that module then should also wrap the snd_seq_poll_* calls.
> I need a "file", so I could use in Gambas:
>
> hfile = Open "....." for Read W A T C H
You would need some mechanism to watch a file that is identified by its
already opened file descriptor, not by its name. It looks as if the
only such mechanism is something that uses the internal interpreter API.
Regards,
Clemens
next parent reply other threads:[~2011-08-29 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1314566910.38637.YahooMailClassic@web29620.mail.ird.yahoo.com>
2011-08-29 9:12 ` Clemens Ladisch [this message]
[not found] <1314978948.16516.YahooMailClassic@web29618.mail.ird.yahoo.com>
2011-09-02 16:32 ` Can ALSA invoke a Callback ? Clemens Ladisch
[not found] <1314385032.22194.YahooMailClassic@web29616.mail.ird.yahoo.com>
2011-08-26 22:03 ` Clemens Ladisch
[not found] <1314369942.41651.YahooMailClassic@web29613.mail.ird.yahoo.com>
2011-08-26 15:54 ` Clemens Ladisch
2011-08-26 14:24 Ru Vuott
2011-08-26 14:34 ` Clemens Ladisch
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E5B580C.4060503@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=vuott@yahoo.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.