soruk42
commented
5 years ago I'm not sure I'll take all of this - for one, I see you moved the .spec file into the build directory. For RPM to build from a tar.gz file it needs to be at the top level.
Closed jgharston closed 5 years ago
soruk42
commented
5 years ago I'm not sure I'll take all of this - for one, I see you moved the .spec file into the build directory. For RPM to build from a tar.gz file it needs to be at the top level.
jgharston
commented
5 years ago On 28-12-2018 16:44, Michael McConnell wrote:
I'm not sure I'll take all of this - for one, I see you moved the .spec file into the build directory. For RPM to build from a tar.gz file it needs to be at the top level.
I think I uploaded too many files all in one go, leave it for the mo and I'll have another go tomorrow. When it said "updating 97 files" I raised an eyebrow for a moment, as I was sure I'd only worked on four or five files.
Acording to the datestamps here the changes should be textonly, graphsdl, error, keyboard.h, keyboard.c, brandy.
Hmm. I think what I did was drag&drop 'matrix' into Git instead of 'src' so it uploaded all my miscelaneous extras.
-- J.G.Harston - jgh@mdfs.net - mdfs.net/jgh
28-Dec-2018
GIT claims dozens of files changed - a quick skim shows about half are just cosmetic.
All kbd_init() and kbd_quit() code all pulled together.
-ve INKEY on DOS works for modifier keys. DOS only has an API call for modifier keys, but this should be a sufficient implementation as it allows ON ERROR IF INKEY-1 THEN ... ELSE ... type constructions. Will also allow future DOS targets to implement VDU 14 and Shift-Ctrl pausing. If running in a DOSBox on Windows is possible to call the parent Windows API, but would be more sense to run a Windows target.
Tweeked text palette of physical colours in 16-colour MODEs to match specifications, see BeebWiki.
Builds tested: DJGPP, MinGW, WinSDL Not yet tested: Linux, RISC OS Not able to test: all other builds