Page 1 of 1
disable word wrap from command line
Posted: Tue Nov 29, 2016 8:34 pm
by FrizzleFry
Is there a way to disable word wrap from the command line?
I tried /command(4209) but that just toggles word wrap on/off. I want to force word wrap off when I run AkelPad from specific scripts.
Posted: Wed Nov 30, 2016 7:15 am
by Skif_off
FrizzleFry
Maybe
Code: Select all
var oSet = AkelPad.ScriptSettings();
var nWordWrap;
if (oSet.Begin("", 0x61 /*POB_READ|POB_PROGRAM*/))
{
nWordWrap = oSet.Read("WordWrap", 1 /*PO_DWORD*/);
oSet.End();
if (nWordWrap == 1)
AkelPad.Command(4209 /*IDM_VIEW_WORDWRAP*/);
}
Save as
WordWrapOff.js and try
Code: Select all
AkelPad.exe /Call("Scripts::Main", 1, "WordWrapOff.js")
Posted: Wed Nov 30, 2016 8:39 am
by FeyFre
Skif_off
Я что-то не понял. Читаете скриптом настройки скрипта же(которых не существует, потому всегда будет читаться значение по умолчанию) и реагируете на значение по умолчанию. Begin("", ...) означает "почитать конфигурацию текущего скрипта" а не АР в целом.
Posted: Wed Nov 30, 2016 11:58 am
by Skif_off
FeyFre
Не только скрипта, смотрите описание:
Code: Select all
0x20 //POB_PLUGS Настройки плагина, pScriptBaseName - имя плагина без расширения.
0x40 //POB_PROGRAM Настройки программы, pScriptBaseName - игнорируется.
Posted: Wed Nov 30, 2016 9:14 pm
by FrizzleFry
That did not seem to have any effect.
I put the WordWrapOff.js script in
D:\tools\AkelPad\AkelFiles\Plugs\Scripts
here is my command line...
D:\tools\AkelPad\AkelPad.exe /Call("Scripts::Main", 1, "WordWrapOff.js") /x file1 file2
I'll mess with it some to see if I can get it to work but this seems incredibly complicated for something that should be pretty simple. I really do not see the point of a command line option to toggle word wrap. There should be separate commands to enable and disable it.
Posted: Wed Nov 30, 2016 9:22 pm
by FrizzleFry
I got it to work!
I changed this line...
nWordWrap = oSet.Read("WordWrap", 0 /*PO_DWORD*/);
from 0 to 1 /*PO_DWORD*/
and it seems to do the trick.
Thanks
Posted: Thu Dec 01, 2016 6:58 am
by Skif_off
FrizzleFry wrote:I changed this line...
Sorry, I incorrectly corrected: of course, we need value type 1 (32-bit number). I Fixed post.