Post by George on May 24, 2021 11:36:26 GMT -5
Interesting. Had a look at the code. Don't know how I ever got it all to work.
It would either be incredibly simple, or incredibly awkward, depending on whether I can figure out how it all works.
Remember, all that was written back in Version 5, about 10 years ago. And other than minor stuff when we went to the CFG file, it's never been looked at.
George
[UPDATE]
It was interesting, still amazed that it all works so well. The KEYMAP dialog is the most complex one in SPFLite, both in drawing it, and in handling all the interactions.
Turns out the Master KB defaults are not stored anywhere as a table. They are used to build the initial KB table, then they are overlaid with the User's customized definitions, and then a 'working' table is built that contains only the non-(Null) entries. (To speed up searches in the KB handler)
So to get the default value for a key meant reading and parsing the raw master table.
Here's one to try out.
[\UPDATE]
SPFLite25.exe (493 KB)
It would either be incredibly simple, or incredibly awkward, depending on whether I can figure out how it all works.
Remember, all that was written back in Version 5, about 10 years ago. And other than minor stuff when we went to the CFG file, it's never been looked at.
George
[UPDATE]
It was interesting, still amazed that it all works so well. The KEYMAP dialog is the most complex one in SPFLite, both in drawing it, and in handling all the interactions.
Turns out the Master KB defaults are not stored anywhere as a table. They are used to build the initial KB table, then they are overlaid with the User's customized definitions, and then a 'working' table is built that contains only the non-(Null) entries. (To speed up searches in the KB handler)
So to get the default value for a key meant reading and parsing the raw master table.
Here's one to try out.
[\UPDATE]
SPFLite25.exe (493 KB)