public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: chris.bird@ctsu.ox.ac.uk
Subject: Re: Multimedia keys interpreted as alphabetic keys
Date: Tue, 20 Apr 2010 14:45:00 -0000	[thread overview]
Message-ID: <4BCDB293.9010007@dronecode.org.uk> (raw)
In-Reply-To: <4BCD8E43.70807@ctsu.ox.ac.uk>

On 20/04/2010 12:21, Chris Bird wrote:
> Thanks very much for getting back to me so soon.
>
> That seems to have fixed the problem, and I will use this version until
> it's in the main build, thanks.

Thanks very much for testing the fix.

> There are a couple of side effects:
>
> 1) XWin dies immediately after outputting a message on startup if I pass
> it both -multiwindow and -logverbose - either in combination with other
> parameters seems to be fine. I have included output into XWin.0.log in
> this instance below.

A numeric verbosity level is mandatory after -logverbose, as the usage info 
should make clear, so the command line below is invalid.

> -logverbose verbosity
>         Set the verbosity of log messages. [NOTE: Only a few messages
>         respect the settings yet]
>                 0 - only print fatal error.
>                 1 - print additional configuration information.
>                 2 - print additional runtime information [default].
>                 3 - print debugging and tracing information.

If you can construct a command line using -logverbose without a numeric 
verbosity level which is accepted, this is another bug in XWin.

> 2) When I ssh to another machine and start the Kate text editor, the
> fonts of the menus and the file being edited are larger than usual (ie.
> larger than when I use it with my old version of XWin). I restarted the
> old XWin and did the same and they were back to normal size. I'm not
> sure where to look for useful logging information on this.

This is expected, as the build I provided is based on the xorg-server 1.8.0-1 
test release [1], which includes a change for the default DPI value used by 
the X server from 75 to the value reported by Windows (usually 96)

You can override the dpi value using the '-dpi' command line option.

[1] http://cygwin.com/ml/cygwin-xfree-announce/2010-04/msg00000.html

> ----------------XWin.0.log starting with with %RUN%
> XWin.20100418-git-9594fb420a063608.exe -multiwindow -clipboard
> -silent-dup-error -xkblayout gb -logverbose-------------------
>
> Welcome to the XWin X Server
> Vendor: The Cygwin/X Project
> Release: 1.8.0.0 (10800000)
> Snapshot: 20100418-git-9594fb420a063608
>
> Contact: cygwin-xfree@cygwin.com
> XWin was started with the following command line:
>
> /usr/bin/XWin.20100418-git-9594fb420a063608 -multiwindow
> -clipboard -silent-dup-error -xkblayout gb -logverbose
>
> ddxProcessArgument - Initializing default screens
> winInitializeDefaultScreens - primary monitor w 2560 h 1024
> winInitializeDefaultScreens - native DPI x 96 y 96
> winInitializeDefaultScreens - Returning
> use: X [:<display>] [option]
>
> [displays usage info]
>
> --------------------------

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2010-04-20 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 16:21 Chris Bird
2010-04-18 21:15 ` Jon TURNEY
2010-04-18 21:15   ` [PATCH 1/3] Cygwin/X: Generate X keycodes for multimedia keys Jon TURNEY
2010-04-18 21:15   ` [PATCH 2/3] Cygwin/X: Generate X keycodes for a few 'internet' keys Jon TURNEY
2010-04-19 14:45   ` [PATCH 3/3] Cygwin/X: Better keyboard debugging output Jon TURNEY
2010-04-20 13:56   ` Multimedia keys interpreted as alphabetic keys Chris Bird
2010-04-20 14:45     ` Jon TURNEY [this message]
2010-04-21 14:57       ` Chris Bird

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=4BCDB293.9010007@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=chris.bird@ctsu.ox.ac.uk \
    --cc=cygwin-xfree@cygwin.com \
    /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).