Pre-Release V2.2.20341

Robert: CFGMaint has no provision for selective Exports. But the Export file can be edited down to JUST the KBD table.

Then if you're careful, you could edit the stripped version and modify is (very carefully) any way you want and then run Import of just that table. CFGMaint only touches the tables that are present in the Import file.

The format is straightforward, but you must be careful, altering is fine, inserting, deleting or re-arranging is a big no-no.

Here's the 1st part of a KBD table


KBD Import.txt (776 B)

So yes, your idea could work.

George

George

First and foremost.... The new code for the 'Maintain screen position after LCmds' option" works well, thank you.  However, there might(!) be gremlins.



LOCATE <linenumber> or <.Linelabel>  command

Hi Robert

Re keyboard switches...
   CFGMaint always exports the entire CFG file, BUT...  it can selectively IMPORT data 'at the table level'
   Unless I'm mistaken, you should be able to import just the KDEFAULT table and keep the rest of the CFG file untouched.

  Load each Export file into SPFLITE and delete everything except the lines from [KDEFAULT] to the next '==========' inclusive.
To switch between keyboards, execute CFGMAINT -IMPORT and point it at the keyboard file of your choice.

Stefan:

Re:

I've had 2 crashes, each time during the run of edit play and for no apparent reason.

I tried to recreate them after restarting SPFLite but was unsuccessful.



First time this afternoon at 15:43, SPFLite presented 3 panels in quick succession

First C005 (KRCHAR)

then Internal Loop Detected (KRCHAR)

then Internal Loop Detected (KRCHAR). I replied CANCEL.



Can't recall what I was doing in detail.

I think I was playing in HEX ON mode, looking at all the characters from X'20' upwards, deciding which to classify as 'invalid' for the picture string P'.' notation.

I'd entered the hex code along two fairly long lines so some LEFT/RIGHT Scrolling was involved.

I think the crash came on one of those.



Second time this evening at 20:00, again 3 error panels in quick succession

First C005 (ADJUSTPENDING)

then C005 (DISPSCEREEN)

then Internal Loop Detected (DISPSCREEN). I replied CANCEL to that one.



This time is was chasing down an apparition following a PROFILE primary command.

The display was showing the file from about 10-12 lines or so down (i.e. line 1 was not the first visible line).

I hit the HOME key and typed PROFILE <ENTER>

But nothing appeared at the top of the screen.

Scrolling back, I see the profile lines were inserted, but ABOVE the top visible line on the display.

I entered RESET to remove them and re-entered the PROFILE command - Worked as it should do.

Scrolled down a few lines and repeated the PROFILE command.

SPFLIte crashed.



It didn't feel like PROFILE caused the error.

More likely, PROFILE was a victim of some error whilst determining the top visible line on the display and hence it inserted the lines in the wrong place.

That's what had me thinking about 'gremlins' in the 'Maintain Screen position...' code.



Sorry - there's not much to go on. I attach the crash reports - renamed slightly to show times.


OK, again I can't get it to crash.  However, V255 only does PROF positioning properly when Maintain Screen position is OFF.  V343 does it correctly whether Maintain Screen Position is ON or OFF, so the fix for screen positioning in V343 seems to have 'fixed' this.
Now as to the crash.  I can't re-create it.

George