Re: [Flightgear-devel] Disabling legacy GL features

[James T. <ja...@fl...>]

> On 7 Aug 2023, at 21:41, TheFGFSEagle <the...@gm...> wrote:
> 
> Hmm, but exactly why do we need to switch FG to GL core profile if I want to be able to run HDR ? I mean, without HDR it runs fine using the compatibility profile … also, do the compatibility functions (such as glBegin) really have to go out of the code or would it be enough for them never to be called ? (which should be the case if I disable the menu bar and hud, start over water (where there is no PAPI) and open no PUI / Canvas dialogs, right ?)

The problem is macOS: there is no compatibility profile.

The ‘remaining’ work is more or less:

	- use the non-Shiva Canvas backend which works on Core profile (Erik has this mostly working I think)
	- fix some bugs in my non-PUI grid layout code, which makes the existing dialogs look ‘wonky’
	- add some missing ‘complex’ widgets (but these can be avoided to start with, eg the airport list box and Nasal console widget)
	- add new Menubar C++ impl (we have most of this, just some C++ driver needed same as PUICompatDialog)
	- live without 2D panels / HUD until they use Canvas internally

But again, if you are Windows or Linux you can use HDr today with compatibility profile, no further work needed :)

Kind regards,
James