From: Chris Marshall <devel.chm.01@gmail.com>
To: cygwin@cygwin.com
Subject: Re: opengl render size too small in X11 window
Date: Thu, 11 Oct 2018 17:41:00 -0000 [thread overview]
Message-ID: <CAPTtexK1fA3caz5RpD8eUoyKQRUjh7n_HNJLfQvYrHZHvu0pBw@mail.gmail.com> (raw)
In-Reply-To: <CAPTtex+HUf7-4+vF+dVRRhRBgPOT3H+a2B8nUGPp+Oj5FFZgxw@mail.gmail.com>
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 <devel.chm.01@gmail.com>
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.
>
> Thanks,
> Chris
>
>
>
--
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
next prev parent reply other threads:[~2018-10-11 17:41 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 [this message]
2018-10-14 17:13 ` Jon Turney
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=CAPTtexK1fA3caz5RpD8eUoyKQRUjh7n_HNJLfQvYrHZHvu0pBw@mail.gmail.com \
--to=devel.chm.01@gmail.com \
--cc=cygwin@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).