- May 10, 2022
-
-
Rob Swindell authored
-
- Jun 03, 2021
-
-
Deucе authored
1) setfont() after loading fonts 2) In X11 mode, don't translate ASCII characters from unicode... this was causing non-ASCII characters to be translated twice.
-
- Jun 01, 2021
-
-
Deucе authored
Fixes sourceforce issue number 60. Reported by WitNik (Thanks!)
-
- May 23, 2021
-
-
Deucе authored
Any screen mode where the description and the enum value were not identical (ie: ones with spaces or parenthesis) would not be used at startup correctly. Reported by DigitalMan via Discord
-
- May 22, 2021
-
-
Deucе authored
Setting the scaling and size before changing modes does weird things. Those things should be fixed, but at least this makes the problem go away in SyncTERM for now.
-
Deucе authored
-
Deucе authored
He's old, and should keep his blood pressure down. Do not walk on his lawn.
-
Deucе authored
-
- May 21, 2021
- May 20, 2021
-
-
Deucе authored
-
Deucе authored
It will be used in the future, so the code shouldn't be deleted, but not using it causes a warning.
-
Deucе authored
While we're doing that, actually use it in SyncTERM so the offline scrollback retains fonts. Also, fix an issue where the current mode would be updated with the custom parameters when you changed them. Finally, remove some unused variables.
-
Deucе authored
It seems that at least LORD has upper-case in the ZIPs and lower-case in the queries.
-
Deucе authored
The biggest issue with SkyPix is the fact that it's *not* a character cell mode. The cursor is pretty much impossible to position correctly, and all the text "stuff" basically needs to be bypassed.
-
Deucе authored
-
- May 19, 2021
-
-
Deucе authored
-
Deucе authored
-
Deucе authored
Now that ALT-Up/Down no longer have an effect on window size, they can go back to their previous bindings of changing the emulated output speed. At the same time, remove AltGr support from keysym parsing since it should be properly handled by the text input stuff now.
-
Deucе authored
Caused the initial window to be the wrong size.
-
Deucе authored
People are used to thinking about the aspect ratio of displays and used to not thinking at all about that of pixels. Most of the modes are simplt 4:3 modes and the text area is the entire window. The only oddball here is the Commodore 64 and 128 40-column modes. Because they have a border around them that's wider on the sides than the top/bottom, the display aspect ratio is actually narrower than a normal NTSC screen (6:5). It seems the PAL version actually has square pixels, but nobody has asked for a PAL Commodore mode, and I think that has a different colour palette too so I'm not doing it. Just to frustrate DigitalMan a bit, the default custom aspect ratio is now 4:3 (but can be configured). At present, modifying the custom mode while *in* the custom modes "works", which no sane person would want when adjusting the aspect ratio.
-
- May 18, 2021
- May 15, 2021
-
-
Deucе authored
Make it the default.
-
Deucе authored
-
Rob Swindell authored
-
Rob Swindell authored
#pragma clang causes an error __attribute__ not supported
-
Deucе authored
This uses the 720x400 with 9x16 character cell that always made BBSs look so terrible.
-
Deucе authored
I do, so you should too!
-
- May 14, 2021
- May 11, 2021
-
-
Deucе authored
Do multiple before divide, and use an lround() to get the same results on Win32 with mingw32 as Clang on FreeBSD.
-
- May 10, 2021