public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mick Pearson <mick.pearson@wildblue.net>
To: cygwin@cygwin.com
Subject: X: wglMakeCurrent error: 0006 on XUnmapWindow->XMapWindow
Date: Tue, 20 Jun 2017 13:24:00 -0000	[thread overview]
Message-ID: <446686543.160825905.1497965042546.JavaMail.zimbra@wildblue.net> (raw)
In-Reply-To: <396829209.160817565.1497964511987.JavaMail.zimbra@wildblue.net>

I was asked by the freeglut mailing list to alert the X/Cygwin
team to problems with the WGL context handles becoming invalid
if a window is hidden and then the error in the subject is out
putted when the window is revealed again.

There are also issues with iconification, where the windows are
in need of repainting when restored. But when unmapped they lose
their WGL context, meaning that OpenGL textures are probably lost
and the context is inoperable, which is a whole other class of 
problems.

The freeglut developer Chris Marshal confirmed this experience.
There is a resizer.exe demo in the freeglut development package
that demonstrates both problems.

In GLUT the problem presents itself when doing glutHideWindow and
then glutShowWindow. Which is not the same as XIconfiyWindow.

I hope this is a temporary development and not the state of X on
Cygwin. I found Xming to supplement the X server. I spent a couple
afternoons attempting to determine the root of the problem. I 
thought perhaps the backing-store fields needed to be set, but it
became clear that most X servers are simply very lenient and most
clients expect them to be, and that there's most likely oversights
in Cygwin/X in the direct rendering mode with WGL.

P.S. I have not subscribed to the Cygwin mailing list. You know if
I receive a CC, but I'm just throwing this out. It may well not be
the first report. Thank you :)

-- 
As with mail, anyone who wishes may send email from your email address. In the case you receive obscene or unusual email from an address with which you are familiar. It could be someone is impersonating that email address. Always return a copy of the email to the sender for review and response. 


--
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:[~2017-06-20 13:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <396829209.160817565.1497964511987.JavaMail.zimbra@wildblue.net>
2017-06-20 13:24 ` Mick Pearson [this message]
2017-06-23 14:22   ` Jon Turney

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=446686543.160825905.1497965042546.JavaMail.zimbra@wildblue.net \
    --to=mick.pearson@wildblue.net \
    --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).