Sync dirs enhancement

[Fla$her]

2wanderer
You didn't answer the first question.
And with regard to the above button, a comment would also not hurt.

[wanderer]

You didn't answer the first question.

I thought it was clear. I added a button from TC's UI, copied your command in TC's field and then i tried to change the path to what i posted. It just stopped 1 char short because of TC's char limit in that field. That's all. After that i dumped this solution and followed Horst.Epp's suggestion which i liked.

And with regard to the above button, a comment would also not hurt.

https://www.ghisler.ch/board/viewtopic.php?p=428540#p428540

I thought it was obvious in this post, i implemented it so i've ended up using it. Works fine, does wat i asked for so... Yeah! Thanks for it.

[Fla$her]

I thought it was clear.

Unclear. I have provided the button codes to insert them into the toolbar immediately. In the first code, there are 139 characters in the first field, so there is nowhere to trigger the restriction after adding a couple of characters.

I thought it was obvious in this post, i implemented it so i've ended up using it.

If it were obvious, then I would not have offered a more competent way out of the situation. A strange conclusion.

[sa16]

2wanderer
There is also a way to write a command (including a very long one) to the [Items] section of the TCFS2.ini, for example, like this:

Code: Select all

SyncMysetting = tcm(2020,1) eval(send_wait(,findwnd(TCmpForm))) sendmsg(if(#1==64, findwnd(LCLComboBox,,findwnd(Window,,findwnd(TCmpForm),1)), findwnd(TMyComboBox,,findwnd(TPanel,,findwnd(TCmpForm)))),334,1)

then call in the TC:

Code: Select all

%COMMANDER_PATH%\Addons\TCFS2\TCFS2.exe /ei "SyncMysetting(%PROCESSOR_ARCHITECTURE:~-2%)"

[wanderer]

I thought it was clear.

Unclear. I have provided the button codes to insert them into the toolbar immediately. In the first code, there are 139 characters in the first field, so there is nowhere to trigger the restriction after adding a couple of characters.

Well, you have provided a working solution. How the user will choose to implement this solution (since there are multiple ways) is up to him. You thought the natural way for me would be to copy/paste the solution to the .bar file, to me was to insert it through the UI and adjust the path to something that's convenient to me, hence the misunderstanding. Hopefully it's clear now.

I thought it was obvious in this post, i implemented it so i've ended up using it.

If it were obvious, then I would not have offered a more competent way out of the situation. A strange conclusion.

As with my reply above, it all depends on how the solution is implemented. Anyway, as i said, followed Horst.Epp's suggestion and used an external command, so all's good,

[sa16]

Way with sending keystrokes:

Code: Select all

%COMMANDER_PATH%\Addons\TCFS2\TCFS2.exe /ef "tcm(2020,1) eval(send_wait(`+{TAB 4}{RIGHT}{DOWN 2}{TAB}{RIGHT}{TAB 2}`,findwnd(TCmpForm)))"

[Fla$her]

Way with sending keystrokes:

It's not a competition for the shortest line. By itself, the keystrokes approach is obviously slower and more unreliable.