From mint-bounce@lists.fishpool.fi Wed Jan 25 21:27:45 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de X-ME-UUID: 20060125201820714.AE77F1C002AA@mwinf0208.wanadoo.fr Date: Wed, 25 Jan 2006 21:18:20 +0100 From: Patrice Mandin To: Mint list Subject: [MiNT] [Q] About /dev/mouse usage Message-Id: <20060125211820.42e71135.mandin.patrice@wanadoo.fr> Organization: Chez moi X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: mandin.patrice@wanadoo.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=2.2 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, RCVD_IN_SORBS X-Spam-Level: ** Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id k0PKRion017137 Hello, I am trying to add support for /dev/mouse device to SDL under MiNT, to avoid using XBIOS (or IKBD) to read relative mouse motion events. I noticed that when the device is opened, the AES has its mouse cursor blocked (i.e. can not move it anymore). Is it a normal/known behaviour? Is mouse device reading blocking or non-blocking when not enough bytes are present in buffer? My guess is 'blocking', but I set it to non-blocking, just to be sure. And what is the use for moose device? Is it only for xaaes? -- Patrice Mandin WWW: http://pmandin.atari.org/ Programmeur Linux, Atari Spécialité: Développement, jeux