From mint-bounce@lists.fishpool.fi  Fri Dec 26 19:28:10 2008
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:sender
         :to:subject:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references
         :x-google-sender-auth;
        bh=gWAA9bcD6fcmfW6IzgSuiT4hCgYO+UNO152zvR2Ug/0=;
        b=MOLqOgTaMIEB3Xl0K+8jCmhYc7V63bwKHbPDLzajzu1HOuBLbqX8EXR1sWVQ13bNwy
         YIkXG8oOHZt1a+RNwB9MkOd5wnekwF0WkvIACo0KmWB2Z6/DPt8ch6IMIb7NlRfHQVj6
         1OmF79NLk6yKb/97KegbrYdO5yvUUWE86MxUI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=bAyhh+CIRGvFHnxNQNDLIk9nKjtV42sWrjWNzwOySs6FcY6mhdupy4BXTyia5AKXbX
         UxDABeKamE/6K2+jbRhUVKwVjoKj5no0sgQQUJ5N9McKb2a0K90q+A02P6NPAIEHu7Za
         PTQsWogP+gVN1kO4cEpRIWm0lFe+suJ8Dd5Yw=
Message-ID: <fbbaf0fb0812261626l41da7399x76a7c04f11bf23d1@mail.gmail.com>
Date: Sat, 27 Dec 2008 01:26:19 +0100
From: "Johan Klockars" <johan@klockars.net>
To: mint@lists.fishpool.fi
Subject: Re: [MiNT] an urgent GEM question :-)
In-Reply-To: <20081223172329.6b2125e8@phineus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1230022147.7318.6.camel@joy> <20081223172329.6b2125e8@phineus>
X-Google-Sender-Auth: 995cb73f744715af
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: johan@klockars.net
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

>> could someone please help me with this off-topic question: I'd need to
>> position the mouse pointer/cursor at defined coordinates on screen. I
>> have tried using v_dspcur(x, y) but it didn't work. Even my PureC help
>> file mentions that the function actually never worked. I was curious
...
>> with the v_dspcur() - is it really wrong in all VDI versions? Or am I
>> just calling it incorrectly?

I don't think it was intended to work, in a graphics mode at least.
If you look at the actual VDI call number for v_dspcur() it's in the
same group as v_enter_cur(), v_exit_cur(), v_curdown(), v_eeol(),
v_rvon(), etc. That is, functions that mainly make sense for a text
based (non-graphics) mode.
I believe v_dspcur() and v_rmcur() were meant to display/remove the
hardware mouse cursor that some (all?) PC graphics cards made
available in text mode.

Still, I suppose it wouldn't have hurt to make the functions actually
useful on the Atari machines...
(Under fVDI, v_dspcur() currently does move the mouse (a relatively
"recent" change, IIRC), but then disables the internal event handling
meant to be used by a mouse driver (to force the mouse pointer to stay
where it was told to be).)

> I remember having the same problem ca. 10 years ago. AFAIR there are
> only two reliable ways of setting the mouse pointer:
>  1) Use appl_tplay(), that's the clean solution
>  2) Poke the address into the corresponding Line-A variables, that's
>    the ugly solution.

Using the lineA variables has never worked under fVDI (by design).

/Johan