Re: [hatari-devel] Hatari window embedding issue (was: Preparing hatari 2.3.1)

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On 12/16/20 5:30 PM, Jens Guenther wrote:
> > Hatari shows just black screen when user starts with, or switches to
> > either TT or Falcon emulation (= videl.c based render mode).
>
> Tested github "hatariui" master and the embedded SDL2 window is overlapped
> by the black GTK3 window right from the start

I think the black area is actually Hatari SDL2
window, as it seems to be getting the key and
resize events fine.

I think SDL2 just isn't refreshing its window
for some reason.


> - regardless of the selected Atari model.

Hm.  After user switches to TT/Falcon mode, switching back to ST/STE 
mode doesn't restore the window, and what's worse, after that one cannot
switch to fullscreen either, i.e. Hatari isn't
anymore receiving key events.

I think only at that point Hatari window isn't
anymore embedded to the the Gtk socket widget.


If one switches to fullscreen and back *before*
changing mode further, rendering is restored
though, and one can use TT & Falcon modes too.


> Disabling the "Embedded window ID change"

What this means?


> shows the correctly
> updated SDL2 renderer in the GTK3 window of "hatariui", but switching from
> fullscreen to window mode brings back the black screen ...


Btw. I noticed that Python UI Gtk window scaling
doesn't work very well either, Hatari window is
scaled only in vertical direction, and menu bar
above is scaled also, which looks ugly.

I'll do something for that, now that Hatari
supports any scaling factor with SDL2.


Because of the Falcon IDE delay with Hatari v2.3,
I probably should add "fast boot" option to the
main UI, or reset dialog, or enable that always
with Hatari...


	- Eero