From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-lf0-f44.google.com ([209.85.215.44]) by ur; Wed Jul 13 05:56:05 EDT 2016 Received: by mail-lf0-f44.google.com with SMTP id f93so35424344lfi.2 for <9front@9front.org>; Wed, 13 Jul 2016 02:56:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=wsSQcWubfcn6exCaqoWzBpkm+LFA8hF1RhI/I3hpqj8=; b=DG4jC3E+EdSj6vMwH4VGLRtIo5GH2FvfdH9OrGT1yYDvQxhuEs0R7mXGaoyOAMvt94 s0SgYjnMveQoTg2zDC0+lHt34uis9iSSVau1mIofQPMpuLS1LJnd8jLOST5plYwKzQMN w/9ZX56+DU8QPQRMpFi5sCUFHV25eM182wT3wIuf7x1yJ76HXTK91wg7xOFegU2RPFag cpNTFu06wvyab1U+V6WO7KS6wn8bOSxT4DUvNUaiSxCAPVERirA2Pmc2cePMcS0drlGz k/mx410WZSvpr88zGIuIRH9KM90nfI9ntATkFuuXpExTsMo7XgdHCn352OJ+81Ao8l7M YM8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=wsSQcWubfcn6exCaqoWzBpkm+LFA8hF1RhI/I3hpqj8=; b=Tr4x9EkbVWTUnq0LcqprNtYf6fj6M59zdpwO8P/od2a4cssva7fX3kWaivitoeRuUQ 5sqBRtaYuxlGm9W470Dr4L83fMwjEoww/jncCpew0tbXwpJxFp9kyAV9rYGxVXLaIFIY D22sFT6s4J+sey1Ziy+uem2mRNmJEzkGNqE+IpBNnjKlRBCnpUxwQcIfe4FM8Yn0iLGe PqX2GV60fO9NtdD/ZKJ2qQ/8ihXRI+yyOcPpwIALqdh3RaDJYDckZuFa1Yo0IKkd/JWE LmvPuLE9S741jgiMjAFnxBmmZKOuNvDxVJVhrMgp8FilbWzTXQBWNyewbL9KShFhg8KA ddDQ== X-Gm-Message-State: ALyK8tJT03kwyVldqTXGqyYzmuD+ZhHnZLge23qt1QF76EnHN0KFzV9ucVzzLrzRBvn9pEMY77KjqXUAaAwgqQ== X-Received: by 10.25.17.228 with SMTP id 97mr4348053lfr.154.1468403762427; Wed, 13 Jul 2016 02:56:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.214.231 with HTTP; Wed, 13 Jul 2016 02:56:01 -0700 (PDT) In-Reply-To: <82ce0e72-31d0-4c6e-88f4-8e89590a64ca@email.android.com> References: <53e1050bb6a13f58ad4026ea6814b8dd@dl.attlocal.net> <9eacbf8e-72f0-41f7-b7a5-b8c119a1b1b4@email.android.com> <82ce0e72-31d0-4c6e-88f4-8e89590a64ca@email.android.com> From: hiro <23hiro@gmail.com> Date: Wed, 13 Jul 2016 11:56:01 +0200 Message-ID: Subject: Re: [9front] drawterm mouse settings To: 9front@9front.org Content-Type: text/plain; charset=UTF-8 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: virtualized shader just-in-time CMS component-scale generator If I understand correctly this is how the mouse works: case MotionNotify: me = (XMotionEvent *)e; s = me->state; ms.xy.x = me->x; ms.xy.y = me->y; ms.msec = me->time; break; On 7/13/16, stanley lieber wrote: > Dave MacFarlane wrote: > >>On Tue, Jul 12, 2016 at 8:22 PM, stanley lieber >>wrote: >>> hiro <23hiro@gmail.com> wrote: >>> >>>>I was under the impression this is handled by your OS (Xorg for >>>>example), not inside drawterm. >>> >>> So, mousectl is simply not implemented? >>> >>> sl >>> >> >>What would it do? Change the settings on the OS of the machine that >>you're connecting >>from? >> >>- Dave > > No, why would anyone expect activity inside the drawterm session to change > the behavior of the host OS? > > The expected result would be to change the behavior of the mouse inside the > drawterm session, just as the mouse(3) bits that are currently implemented > facilitate the current behavior of the mouse inside the drawer term session. > If I understand correctly, all that is missing here is implementing those > bits (namely, ctl messages). > > Maybe I'm misunderstanding and this is impossible, but if so, how can the > mouse work at all? Drawterm already intercepts and interprets the mouse, > right? > > sl > >