Re: FOX 1.7.78 OpenGL not working?

Greetings JVZ,

Sorry My bad.  In the previous email, I attached two snapshots - not 
sure if you were able to view it.

Here are more information:

-  I used the gltest project that is included in the FOX code base
-  Windows Server 2016 (on a VMWare Virtual Machine),  Visual Studio 
2019; but on the SAME virtual machine,  gltest project compiled with Fox 
version 1.6.57 work normal.
-  I tested the gltest project both 32 bit and 64bit,  and both Debug 
and Release.  The issue seems prevailing on all of them
-  I didn't make any changes to the source file, compiler flags, or 
preprocessor macros
-  I haven't done any further tracing work (yet, I am still learning Fox 
but I'd love to be helpful and contributing once I can)
-  I sent out the email just to check if it is known or someone else has 
already encountered the same.

I suspect the OpenGL driver (that comes with VMWare ?) somehow is 
"incompatible" with Fox v1.7.78.  It works with Fox v1.6.57, though.  
That is why I wonder what has changed between the two versions.

Thank you again.

Best
Wuping

------ Original Message ------
From: [email protected]
To: "Wuping Xin" <[email protected]>
Cc: "FOX Users" <[email protected]>
Sent: 8/18/2021 12:25:51 PM
Subject: Re: [Foxgui-users] FOX 1.7.78 OpenGL not working?

>On 2021-08-18 11:08, Wuping Xin wrote:
>>It seems the latest 1.7.78 OpenGL (FXGLVisual) has some changes.
>>
>>The gltest with v1.7.58 now all "blackout".
>>
>>
>>Previously, it works fine with v1.6.57 .
>>
>>Any advice?
>
>
>There's a fine art to reporting bugs.  Just a few suggestions:
>
>1) Assume I'm not clairvoyant, able to do ESP, or anything like that.
>    Basically, all I know is what you tell me.  And you haven't told
>    me anything that would help.
>
>2) So, what O.S. are you running, what GPU, did you compile FOX
>    with VC++ 2008, or some other version of VC++.
>
>3) Did you compile 64-bit or 32-bit.
>
>4) Did you compile for debug, or release?
>
>5) Any alterations made to compiler flags or source files?
>
>6) After deciding it didn't work, did you compile for debug and
>    generate tracing output to potentially diagnose path through
>    code?
>
>7) If it core dumped, did you have a stack trace?  Location in
>    code where things went wrong?
>
>It is unreasonable for you to expect me to put more effort into
>SOLVING your problem than you did REPORTING it.
>
>Cheers,
>
>
>      -- JVZ