Copy of complex BLF fields to other computer

[stappaf]

Hello Tomek, Hello github team,

i installed Tomek´s wonderful tSIP on a windows system. I created a lot of BLF buttons (more than 50) and other stuff ... Works great, but now i want to copy this to a other computer for a other extension, I only wanted to change the extension passwort and keep all the other buttons. But if i copy the directory with all data the changes are all gone. I do not find anything at %appdata% or elsewhere to copy additional. Am i blind or what is the trick

thank you for any support Stefan from Munich/Germany

[tomek-o]

Hello, typically (with exception for when /profiledir command line parameter is being used, but let's ignore that) settings are stored in two files placed next to tSIP.exe: tSIP.json ("main" file) and tSIP_buttons.json (big array with all programmable buttons). Copying entire folder should work also. One exception might be situation when tSIP was "installed" in Program Files folder (or somewhere else where user cannot write to) - operating system starting from Windows Vista might redirect all file writes to VirtualStore in user home folder (e.g. C:\Users\Tomasz\AppData\Local\VirtualStore) then - sometimes it might get misleading. My personal preference is not using system partition for portable applications at all (thus storing these applications on D: \, E: \, etc.), but if PC would have multiple users then I guess placing separate copy of tSIP in each user directory might also make sense.

If VirtualStore mechanism might be a problem, I would recommend checking tSIP_buttons.json file content if this is the "right" copy. Let me know if this is the case.

I would also add that main settings and buttons settings can be merged - either with script (https://tomeko.net/software/SIPclient/howto/provisioning.php) or manually under "Configuration" menu - this might allow e.g. to let users customize part of the GUI (say, buttons 0...14 that are normally placed near DTMF buttons) while keeping other part in sync. General method for creating "patch" files is to take settings file and delete (using e.g. JSONedit) from it everything that should not be changed. For arrays position is important - buttons that should be unchanged should be represented by empty objects.

[stappaf]

Hello Tomasz, thx for the detailed answer. I did not really „install“ prog. My installation was: copying the zip files content tree to c:\program\TSip… (not to c:\program (x86)…) of first machine and transferring c:\program\TSip - tree after configuration to second machine‘s c:\data\tZip… And now the customized jason files seem to be unknown to second machine.

I will check your tips. I will try to find tSIP.json and tSIP_buttons.json elsewhere on first machine and replace it to the files in directory of tsip.com on second machine.

br Stefan

Am 21.10.2021 um 19:14 schrieb Tomasz Ostrowski @.***>:

 Hello, typically (with exception for when /profiledir command line parameter is being used, but let's ignore that) settings are stored in two files placed next to tSIP.exe: tSIP.json ("main" file) and tSIP_buttons.json (big array with all programmable buttons). Copying entire folder should work also. One exception might be situation when tSIP was "installed" in Program Files folder (or somewhere else where user cannot write to) - operating system starting from Windows Vista might redirect all file writes to VirtualStore in user home folder (e.g. C:\Users\Tomasz\AppData\Local\VirtualStore) then - sometimes it might get misleading. My personal preference is not using system partition for portable applications at all (thus storing these applications on D: , E: , etc.), but if PC would have multiple users then I guess placing separate copy of tSIP in each user directory might also make sense.

If VirtualStore mechanism might be a problem, I would recommend checking tSIP_buttons.json file content if this is the "right" copy. Let me know if this is the case.

I would also add that main settings and buttons settings can be merged - either with script (https://tomeko.net/softwarehttps/SIPclient/howto/provisioning.php) or manually under "Configuration" menu - this might allow e.g. to let users customize part of the GUI (say, buttons 0...14 that are normally placed near DTMF buttons) while keeping other part in sync. General method for creating "patch" files is to take setting file and delete (using e.g. JSONedit) from it everything that should not be changed.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[stappaf]

Hello the files have been at appdata thx everything works great now br Stefan

Am 21.10.2021 um 19:14 schrieb Tomasz Ostrowski @.***>:

 Hello, typically (with exception for when /profiledir command line parameter is being used, but let's ignore that) settings are stored in two files placed next to tSIP.exe: tSIP.json ("main" file) and tSIP_buttons.json (big array with all programmable buttons). Copying entire folder should work also. One exception might be situation when tSIP was "installed" in Program Files folder (or somewhere else where user cannot write to) - operating system starting from Windows Vista might redirect all file writes to VirtualStore in user home folder (e.g. C:\Users\Tomasz\AppData\Local\VirtualStore) then - sometimes it might get misleading. My personal preference is not using system partition for portable applications at all (thus storing these applications on D: , E: , etc.), but if PC would have multiple users then I guess placing separate copy of tSIP in each user directory might also make sense.

If VirtualStore mechanism might be a problem, I would recommend checking tSIP_buttons.json file content if this is the "right" copy. Let me know if this is the case.

I would also add that main settings and buttons settings can be merged - either with script (https://tomeko.net/softwarehttps/SIPclient/howto/provisioning.php) or manually under "Configuration" menu - this might allow e.g. to let users customize part of the GUI (say, buttons 0...14 that are normally placed near DTMF buttons) while keeping other part in sync. General method for creating "patch" files is to take setting file and delete (using e.g. JSONedit) from it everything that should not be changed.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[tomek-o]

Thanks for the info. My personal preference as mentioned would be avoiding Program Files altogether and use either user folder or even separate partition (back in Windows 98 days this was allowing me to overwrite whole system partition with Norton Ghost image and immediately resume normal work).