Quote:
Originally Posted by wareck
hello
I think I found a little bug, probably only a typo or return to line issue.
in this function :
it makes weird xtool.ini file like this :
or
if I use only plugin like bk2 it works because xtool.ini is comming from the plugin, but if I use several fuction in one row, it may not works
in the last beta I downloaded , this issue is still there:
|
When you use the command line, such as:
Code:
[function.XTool_SetINI]
INI: {param1}\XTool.ini; Action: WRITE; Section: {param2|cpk}; Key: Encode; Value: {param3|crilayla.exe d <library>};
INI: {param1}\XTool.ini; Action: WRITE; Section: {param2|cpk}; Key: Decode; Value: {param4|crilayla.exe e <library>};
[function.XTool_Bink]
PSC: function.XTool_SetINI|{param1}|bink|clsw.exe c:bpk - - <stdin> <stdout>|clsw.exe d:bpku - - <stdin> <stdout>;
or
[function.XTool_Crilayla]
PSC: function.XTool_SetINI|{param1}|cpk|crilayla.exe d <library>|crilayla.exe e <library>;
The value of {param1} is inherited from the section that called the function (see red text below).
Code:
[Copy.Bik_Plugin]
PSC: function.XTool_Bink|PRE\XTool_2020;
or
[Copy.XTool_Crilayla]
PSC: function.XTool_Crilayla|PRE\XTool_2020;