public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mick Pearson <mick.pearson@wildblue.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: XWin can't hold OpenGL picture, has WS_DISABLED and WS_EX_TRANSPARENT styles?
Date: Sat, 16 Nov 2019 17:03:00 -0000	[thread overview]
Message-ID: <1343504374.11717315.1573911582968.JavaMail.zimbra@wildblue.net> (raw)
In-Reply-To: <1501149975.8378096.1573630073765.JavaMail.zimbra@wildblue.net>

I've put forward a patch (https://sourceware.org/bugzilla/show_bug.cgi?id=25170) to this for anyone interested. I'll
explore putting it elsewhere, but I really think these mailing lists are an albatross, not sure I want to join another.

----- Original Message -----
> From: "Mick Pearson" <mick.pearson@wildblue.net>
> To: "cygwin" <cygwin@cygwin.com>
> Sent: Wednesday, November 13, 2019 1:27:53 AM
> Subject: Re: XWin can't hold OpenGL picture, has WS_DISABLED and WS_EX_TRANSPARENT styles?

> Sorry (I don't know how to you L A Walsh reply so am replying to myself with the
> same subject)
> I think I meant to include this
> (https://sourceware.org/bugzilla/show_bug.cgi?id=25170) link that
> includes this link:
> 
> https://www.mail-archive.com/search?l=cygwin-xfree@cygwin.com&q=subject:"Re\%3A+Probable+bug+in+WGL+implementation+\(AIGLX\)+of+GLX+calls+in+XWin+\-wgl"&o=newest&f=1
> 
> I was too zealous to be brief, and I think now the window styles are a red
> herring. In any case the
> problems arise in "overdraw" scenarios wherein a window passes over the OpenGL
> windows, that
> is when the background is "erased" and the picture is lose (not held) which
> makes it impossible to
> use XWin for anything but one screen demonstrations of graphical effects. Some
> applications use
> multiple windows and do rendering with OpenGL instead of GTK widgets for
> example. Those can't
> use XWin. I think OpenGL doesn't work with MS Windows X servers. I hope it works
> with Linux ones.
> 
> The other X servers available to Windows are in disarray with regard to OpenGL.
> So it would be good
> if one of them could be made to work. XWin is closest since it doesn't crash and
> does draw correctly
> other than it can't hold a picture.
> 
> ----- Original Message -----
>> From: "Mick Pearson" <mick.pearson@wildblue.net>
>> To: "cygwin" <cygwin@cygwin.com>
>> Sent: Saturday, November 9, 2019 3:49:12 AM
>> Subject: Re: XWin can't hold OpenGL picture, has WS_DISABLED and
>> WS_EX_TRANSPARENT styles?
> 
>> P.S. Sorry to add, the WM_ERASEBKGND message occurred to me, or setting the
>> class-background to the "null" brush is a likely culprit. It is behaving like
>> a front-buffered old-fashioned application somewhat. Clipping and own-DC style
>> should prevent damage, but I don't know, something seems to be responding to
>> PAINT like events, that don't make sense for OpenGL.
>> 
>> Below is line formatted version of the old text. I have to do this manually for
>> new text, but the > quoted text is already hard-wrapped.
>> 
>>> XWin has never had a permanent picture with OpenGL. Any movement "damages" all
>>> windows. I know I've looked at it before, but I checked its window/class styles
>>> with MS's Spy++ tool today. The normal styles that govern clipping and
>>> permanence look fine, but it has some weird styles that normally for disabled
>>> and transparent windows that I wonder are the cause for its abnormal behavior
>>> in this regard. No OpenGL apps that just draw only OpenGL on a window have
>>> XWin's problem.
>>> 
>>> To be brief, it has these unnatural window-styles in this mail's subject line.
>>> Other than that, I think it may use Direct3D instead of OpenGL, but normally
>>> drawing OpenGL or Direct3D onto plain windows doesn't clobber other windows. I
>>> mean, you have to work hard to make it do something like that.
>>> 
>>> A second, unrelated, oddity is the window decorations are sometimes classic
>>> style, and sometimes current style. It's very odd. It's random in the same
>>> session. The windows seem to undergo a transition from classic to current, but
>>> get stuck in classic sometimes. Maybe they are using the old "animated" show
>>> functions that didn't survive the version of Windows that introduced them.
>>> 
>>> Niggling things like this could be fixed. But I don't know how many people use
>>> Cygwin. I've used it a lot over the years myself, to do development work. XWin
>>> is the most stable X server. Others don't really get close. But it's kind of
>>> too comfortable with its crumminess too. Not that I'm going to shove my work
>>> aside to try to remedy it myself.
>>> 
>>> --
>>> 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.
>> 
>> --
>> 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.
> 
> --
> 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.

-- 
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:[~2019-11-16 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09  9:21 Mick Pearson
2019-11-09  9:49 ` Mick Pearson
2019-11-13  7:27   ` Mick Pearson
2019-11-16 17:03     ` Mick Pearson [this message]
2019-11-16 17:31       ` Brian Inglis
2019-11-22  6:57         ` Jon Turney
2019-11-11 20:58 ` L A Walsh

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=1343504374.11717315.1573911582968.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).