Usage
|
Application incompatibility
|
*Non-substitute applications
I guess non-substitute applications are non-scriptable applications,probably.
I think it not bad in some case. For the product designed to high quality
and stability, to suppress scripting may be better decision. Of course,
I hope more better to design high stability with scripting. |
|
*Abort applications
Some applications are crashed by script sent from Lexy.
I have not found cause of crash. But generally, to suppress "control
substitute" is effective at stability.
Are aborted applications wrong? No.
No one expected that external software would substitute own labels. I
never say aborted applications are wrong.
Best way is to set exception to the applications. |
|
*Problem of Replicant container
Lexy distinguish applications by signature. Therefor,Lexy-incompatible
replicant embedded replicant container is received a script from Lexy. And
replicant container are crashed by Lexy-incompatible replicant. (e.g. Tracker
that embedded Netpositive)
Generally for safety, replicant container should be set a exception. |
|
Structure of Dictionary
Structure of Lexy 1.0 Dictionary format is very simple.
|
*Fromat of substitute word dictionary
Tab and LF delimiter Text. Default name is "LexyDict.txt".
- Line 1 : File identifier
- After line 2 : "Target word" (tab) "Substitute word"
(LF)
|
|
*Format of exception applications list
Tab and LF delimiter Text. ON=1,OFF=0. Default name is "LexyExcept.txt".
- Line 1 : File identifier
- After line 2 : "Control substitute ON/OFF" (tab) "Menu
substitute ON/OFF" (tab) "Title substitute ON/OFF" (tab)
"signature of exception application" (LF)
|
Stuff files location
Lexy uses following stuff except dictionaries. When you uninstall Lexy
for reference.
(Parent path of Lexy)/LexyHelp/*
/boot/home/config/settings/MFukuStuff/LexyPrefs
|