I'm thinking now ZEP needs to modify the full-screen so all it does is maintain its current size but put a black background behind the full-size of the screen.
By doing so, you don't have problems with hardware snap and you can still see your normal icons in the taskbar below.
I'm thinking it's the hardware snap that is causing the problem.
Hi. I am currently running PICO-8 in Win10 with the anniversary update. It runs fine in full screen, but as soon as I try to switch to windowed mode, the application crashes as well.
as stated by gamax in another thread, sdl2.dll is outdated.
not saying those problems stem from there, but it might be worth an update:
https://www.libsdl.org/release/SDL2-2.0.4-win32-x86.zip
the SDL2 team is obsessive about being backward-compatible, so that shouldn't bring more trouble. of course, your mileage may still vary.
alternatively there are three options for fullscreen in config.txt:
fullscreen_method 2 // 0 maximized window (linux) 1 borderless desktop-sized window 2 fullscreen
Hey :)
I get this one when trying to leave fullscreen:
System Info:
./+o+- bastetfurry@katzenrechner yyyyy- -yyyyyy+ OS: Ubuntu 16.04 xenial ://+//////-yyyyyyo Kernel: x86_64 Linux 4.4.0-38-generic .++ .:/++++++/-.+sss/` Uptime: 5h 20m .:++o: /++++++++/:--:/- Packages: 1633 o:+o+:++.`..```.-/oo+++++/ Shell: bash 4.3.46 .:+o:+o/. `+sssoo+/ Resolution: 3360x1050 .++/+:+oo+o:` /sssooo. DE: LXDE /+++//+:`oo+o /::--:. WM: OpenBox \+/+o+++`o++o ++////. CPU: Intel Core i5-2400 CPU @ 3.4GHz .++.o+++oo+:` /dddhhh. GPU: GeForce GTX 960 .+.o+oo:. `oddhhhh+ RAM: 2171MiB / 7964MiB \+.++o+o``-````.:ohdhhhhh+ `:o+++ `ohhhhhhhhyo++os: .o:`.syhhhhhhh/.oo++o` /osyyyyyyo++ooo+++/ ````` +oo+++o\: `oo++. |
(Yeah yeah, such a beast using LXDE... i like my UI lean and mean. ;) )
Fixed for 0.1.9b, which will be up tomorrow. I've also included the updated SDL2.dll too for good measure.
When config.txt was not found, the window size was defaulting to 0,0 -- causing a divide by zero (the size < 128,128 crash bug that is also now fixed). Many thanks for the reports in this thread -- it made it much easier to track this down.
[Please log in to post a comment]