>The purpose of the start script is that the application which uses sakit does > not need to know internals about the sakit file and directory names and.
Yep, it was a excellent idea, it is why i use sak.ini. In fact, it has the same goal but not inside a script. => example sak.ini for linux 64 ----------------------------------------- # Config file for linux64 BINESPEAK=speak_x64 # speak or espeak binary LIBESPEAK= # needed for espeak binary DIRESPEAKDATA=./ # directory of espeak-data LIBPORTAUDIO=libportaudio_x64.so # portaudio library ------------------------------------------ > "sak.ini" surely is an alternative but less flexible. Why ? With sak.ini you can even choose to use espeak/speak (with/without espeak.lib). > If not, what do you think to use a TProcess ? > tmseprocess has some advantages. I don't use TProcess myself. OK, i will not touch to main sak_mse.pas (but i did already the transition in sak_mse_fred >PS: It seems you don't use git merge (see attachment)? >Please write if you like to know how to use git merge, mergetool and difftool. Indeed (because i deeply analyze your code before to merge and do the modif from my code. I agree it is not the "git" way. OK, convert me to use git merge, mergetool and difftool. FreD
------------------------------------------------------------------------------
_______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk