- May 20, 2021
-
-
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
-
-
Deucе authored
-
Deucе authored
Being stritly less/greater causes a one pixel gap at the start/end of the ellipse, meaning flood fills can escape.
-
Deucе authored
Clamp coordinate translation max Fill using native pattern, not scaled pattern Add a bad, broken, and slow even/odd fill Fix logging when RIP is enabled Use the same ellipse algorithm for partial as full ellipses Detect diagonal movement in ellipse drawing and don't make the edge fat Only recurse once in the flood fill Implement the v2 poly bezier command Enable filled pie slices Add RIP_POINT command (basically a scaled pixel using line width)
-
- May 07, 2021
-
-
Deucе authored
Consistently use map_rip_color() Optimize flood fill to not clobber the stack Fix small full ellipses to match RIPTerm 1.54
-
- May 06, 2021
-
-
Deucе authored
-
- May 05, 2021
-
-
Deucе authored
Mostly tightening things up and fixed some text things.
-
- May 03, 2021
-
-
Deucе authored
-
- May 02, 2021
-
-
Deucе authored
color_value() is in the hot drawing path, so should be as fast as possible... remove all the bit shifting and have the palette just be colour values. For RIP, the reset wasn't resetting the global coordinates, so a scaled image would cause everything to be scaled down later.
-
Deucе authored
Used extensively on Black Flag BBS.
-
- May 01, 2021
- Apr 30, 2021
-
-
Deucе authored
We still need to pass ANSI through to the parser though because Synchronet goes apeshit if it doesn't get a response to a location request... it tries twice and eats any data it receives that isn't a valid position report, which obviously breaks menus. It's also very weird that on Booch's BBS at least it's sent during the main menu display rather than just on answering. Not sure why this is, but it means we can't implement the RIP requirement of "ignoring all non-RIPscrip bytes" with a zero window without digging deep into Synchronet guts.
-
Deucе authored
Generate conversion tables rather than do float math twice for each virtual pixel.
-