Open benfry opened 4 years ago
@benfry What's the status of this issue given the above merged PRs?
No status update, really. During the 4.x process it looked like this would be a higher priority (i.e. to support LWJGL or other rendering systems) but it turned out to be less important, so less time was spent here.
There have been changes to allow more separation, and make it clearer where we're crossing that boundary, should we want to complete the exorcism. And it should be possible to run without it, but these methods still won't work.
More here: https://github.com/processing/processing4/wiki/Exorcising-AWT
We need either 1) an alternative/native method to make these work, or 2) a per-Surface version of them.
The second option is still problematic since we don't know what
PSurface
will be used whensettings()
is called. So either we need to start passing that to the command line, or do something more clever, i.e. oncesize()
orfullScreen()
is called, use therenderer
to create an object that can handle these device settings on a per-surface type basis.For now,
displayWidth
anddisplayHeight
will be0
when--disable-awt
is used.