public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Chris Marshall <devel.chm.01@gmail.com>
Subject: Re: opengl render size too small in X11 window
Date: Sun, 14 Oct 2018 17:13:00 -0000	[thread overview]
Message-ID: <f5ec8d17-1189-8911-901e-a7c8f0c1b7dc@dronecode.org.uk> (raw)
In-Reply-To: <CAPTtexK1fA3caz5RpD8eUoyKQRUjh7n_HNJLfQvYrHZHvu0pBw@mail.gmail.com>

On 11/10/2018 18:40, Chris Marshall wrote:
> I've verified that if I use the -nowgl option for the X11 server then the
> opengl visualization is correctly rendered and sized for the containing
> window.
> 
> On Wed, Oct 10, 2018 at 12:15 PM Chris Marshall
> wrote:
> 
>> Dear Cygwin-
>>
>> Using cygwin X11 under windows 10 with a high dpi display (3840x2160)
>> laptop resulted in far too small font and widgets using -multiwindow for
>> the XWin option.  If I set the windows setting display resolution to
>> 1920x1080 and following the suggestion for the ~/.Xresources file from
>> https://stackoverflow.com/questions/42211564/cygwin-xwin-scaling-broken-when-using-windows-scaling-on-high-resolution-displa
>> I was able keep windows, widgets, and title/menu bars at a reasonable size
>> for reading.
>>
>> However, when I display some OpenGL graphics content (using a FreeGLUT
>> window), then the visible OpenGL rendered area is about 2/3 the apparent
>> widget area of the X11 window.  If I try the same in a non-multiwindow Xwin
>> session then the rendered area is correct.  This problem is even worse if I
>> try with the full screen resolution.  At the moment I think I have narrowed
>> it down to the -multiwindow support for OpenGL contexts.
>>
>> This is with a couple of versions of the freeglut libraries with no effect
>> and the current cygwin and cygwin X Server.

Interesting.  Thanks for reporting this issue.

I suspect this might be caused by:

- the X server is marked as high-dpi aware (via manifest)
- when using WGL, OpenGL drawing takes place in the client (to a window 
handle retrieved from the X server)
- the GL client you are using is not marked as high-dpi aware (the default)

(-wgl is only currently supported in multiwindow mode)

If that's the case, I think I see what is needed to fix this, but this 
is not possible for me to test.

I've built an updated libGL1 with this potential fix, perhaps you can 
try it, to see if it improves things. Install it with:

wget ftp://cygwin.com/pub/cygwinx/x86_64/libGL1-18.0.5-1.1.tar.xz
tar -C / -xvf libGL1-18.0.5-1.1.tar.xz

(This is built for x86_64. If you need x86 instead, please ask)

Reinstall the libGL1 using cygwin setup to get things back to their 
previous state.

-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

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

  reply	other threads:[~2018-10-14 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 19:16 Chris Marshall
2018-10-11 17:41 ` Chris Marshall
2018-10-14 17:13   ` Jon Turney [this message]
2018-10-14 18:02     ` Chris Marshall
2018-10-14 18:21       ` Chris Marshall
2018-10-14 18:26         ` Chris Marshall

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=f5ec8d17-1189-8911-901e-a7c8f0c1b7dc@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=devel.chm.01@gmail.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).