How to make settings stick

Akuro · Post by **Akuro** » Wed Apr 01, 2015 7:10 am

Found great scripts that modify the interface. But the changes won't survive a restart, they are retained for the current instance only. If I understand correctly, I have to trigger those script-calls at startup? But how?

In TabFonts.js for instance, the instructions tell me to insert
/Call("Scripts::Main", 1, "TabFont.js", `"8"`)
into AkelPad.ini
When I do so, my ini gets totally messed up, it loses most of its entries on the next startup.
Obviously, I am missing something here, some kind of Autostart-section? Or is there any other way to make certain script settings stick across sessions?

Instructor · Post by **Instructor** » Wed Apr 01, 2015 4:17 pm

Akuro

TabFont.js wrote:// For autostart, in AkelPad.ini or registry CmdLineBegin/CmdLineEnd key, need to add eg:
// /Call("Scripts::Main", 1, "TabFont.js", `"8"`)

See CmdLineBegin and CmdLineEnd manual settings in AkelHelp-Eng.htm.

Akuro · Post by **Akuro** » Thu Apr 02, 2015 8:17 pm

Thanks.

KDJ · Post by **KDJ** » Thu Apr 02, 2015 8:46 pm

Akuro
To change manual settings: AkelPadManualSettings.js

Akuro · Post by **Akuro** » Fri Apr 03, 2015 5:48 am

Thanks KDJ - have never been much of a command line afficionado, so this script really helps.