rcmaniac25

freeglut doesn't have any computation implementation, so it has no part in device selection, which is possible without freeglut support. From what I read, on the graphics/display, that isn't possible with OpenGL (and freeglut) or Direct3D 11 and earlier. You'd need Vulkan or Direct3D 12. Outside of using one of those, it's an application-level thing, not a framework/API thing. AMD and Nvidia both offer applications for making application profiles to specify if the app uses the dedicated or integrated...

I'm fine with this. I don't see any recent issues/PRs that I think "must" be done before release. Vinnie From: John Fay fayjf2@users.sourceforge.net Sent: Tuesday, June 12, 2018 9:43 PM To: [freeglut:bugs] Subject: [freeglut:bugs] Re: #245 Win32: Fixed a bug regarding WM_SIZE processing. Is it time for a new release? On 6/10/2018 4:29 AM, Diederick C. Niehorster wrote: Hi Marc, They aren't in the release indeed, they are in svn trunk. All the best, Dee On Sun, Jun 10, 2018, 03:14 Marc Berger zzador@users.sourceforge.net...

I don't know about former case, but in terms of the latter: If you call glutGetModifiers outside an input handler, we do log a warning. If you call glutWarpPointer, we also already have a warning saying it isn't supported. Just need to register a warning handler (glutInitWarningFunc) and it will get called with those warnings. If you were expecting a printout to stderr, you need to have compiled freeglut with "FREEGLUT_PRINT_WARNINGS" defined.

I don't know a lot about Wayland, but from doing some searches, Wayland doesn't support pointer warping. I did find https://phoronix.com/scan.php?page=news_item&px=XWayland-Pointer-Warp-Emulate but I don't see anything say warping exists... just that they now can use relative positions and people emulate warping with virtual pointers.

You don't need to remove the static modifier in fg_joystick.c, which prevents te function from being exported. All you should need is to add "static" to the foward declartion you made in fg_joystick_x11.c

I have no knowledge of how to make it work (I have not done Android development), but I do know you need an AndroidManifest.xml. You may want to look at "freeglut-3.0.0/progs/test-shapes-gles1" as it is setup to support building for Android. It might be a little outdated though. If you hit the issue with the sample app, then I see it as a bug. If not, then try adding a manifest and setup your project in a similar way. If it works, great. If not, then we'll take it from there.

I think I realized why this is happening. I'm looking into a different task and was going through fgPlatformOpenWindow in fg_window_x11.c and noticed we create and push a ConfigureNotify event directly after creating the window so we "Fake configure event to force viewport setup even with no window manager." ConfigureNotify events invoke a position and reshape callbacks (if they aren't default values). Thus, my guess: by sending our own ConfigureNotify, we end up causing a reshape notification before...

John Fay indicated this appeared to be fixed. Double checking, I can confirm the ActionOnWindowClose variable is not changed before testing it's value.