cmd: %COMMANDER_PATH%\tools\tcbl\tcbl.exe
parameter: -i %L imagik.Half
icon: what you want !
If it is not installed under total commander path in folder tools\tcbl, you should adapt it.
Some explanation :
Once you click on the button, you pass as option -i -> use inifile, the file of all selected files %L and the command to use inside the tcbl.ini imagik.Half.
===========================
In your case if you selected :
set PATH=C:\tools\graphic\ImageMagick\;%PATH%
set img_resize="50%"
mogrify.exe -resize "%img_resize%" "c:\My Images\img001.jpg"
mogrify.exe -resize "%img_resize%" "c:\My Images\img002.jpg"
mogrify.exe -resize "%img_resize%" "c:\My Images\img003.jpg"
That's what I guessed but I was not very sure. I recommend you clarify this relationship between the [script_header] and the command line parameter of TCBL in its doc, if you have not.
nsp wrote:
If you want to see it before execution, use -ei options instead of -i. You will get notepad launched with the file produced, you can modify it befor execution. In the console, you press a key and the execution continue !
...
The tools was intended for people that used lst2multi and wanted to have an external tool (like me to also use it outside of TC...
Now it's very clear to me. Thank you so much for your clarification and your great productive tool!
Last edited by min2max on 2009-12-27, 07:05 UTC, edited 1 time in total.
[cpar2filesblock]
pre=@echo off
pre=REM
pre=title copy all files, 1 par block for all files
pre=REM
pre=REM $1 = %%commander_path%%\.scripts\par2\par2.exe
pre=REM $2 = parsize
pre=REM $3 = %T (target dir)
pre=REM $4 = finish task
pre=REM
pre=if exist "%~dp0finish.cmd" del "%~dp0finish.cmd"
pre=copy "$4" "%~dp0finish.cmd"
cmd=copy "$f" "$3\$n"
end=echo invoking par2/.
end=$1 c -r$2 -t+ -l "$3\generated.par2" "$3\*.*" && echo . > "$3\.transferred" && echo . > "$3\.packaged"
end="%~dp0finish.cmd"
end=pause
... ...
Thank you for your examples.
If you also list the example command line parameters demonstrating your sample command sets, just like nsp, it would be much clearer and more helpful to me and any other who is at the similar level as me.
Thanks you for your further information. It's getting much clearer.
I'm currently not very familiar with .bar files and its role in the TC environment. Could you please give more introduction on how I can get all these stuff (TCBL+ini+bar) work?
Or, in other words, I know I can have .ini file work by feeding TCBL with -I <my .ini file path> parameters. Now I want to know how is the .bar file functioning.
And I would appreciate if anybody could give a more detailed explanation on the usage of TCBL + super_wdx - I have some difficulty understanding the concept "column" and the SSettings.exe program.
1) save the contents of the bar code to a file
2) name it par2.bar
3) drag and drop this file to the menu bar in tc 7.5 within tc
4) right click on the new entry in the menu bar/change and tick the option "show as menu"
5) to change the entries right click on the menu icon in the menu bar and click on "edit linked button bar" or you can mess around with the .bar file
each line in the bar file represents an input filed of the "edit linked button bar" dialogue.
if you don't like menus within the menu bar, you can have single items as well.
min2max wrote:And I would appreciate if anybody could give a more detailed explanation on the usage of TCBL + super_wdx - I have some difficulty understanding the concept "column" and the SSettings.exe program.
TCBL use SuperWDX as proxy/intermediate to call wdx plugins and do not need any column defined. But you need at least to initialize SuperWDX wdx plugins list using sseting.exe (Plugin->define plugins folder) .
SuperWDX syntax enclosed into $! is used to call wdx plugin.$!%Field@wdxplugin.wdx%$!
See help file in sseting.exe under "plugin setup" topic, and get more info on "Content strings adjustment and formatting" section.
TCBL can also call SuperWdx column using the syntax $!n$! where n is the column number (i do not recommend this usage unless you have a very stable SuperWDX seting).
Anyway wdx support is not as smooth as WdxInfopacker or using Multi Rename Tool.
min2max wrote:------8<----------
IIUC, one would better use WdxInfopacker instead of super_wdx for more function and smoother collaboration. It that right?
------8<----------
SuperWDX is fine for adding per extension wdx info under the same column it is a content plugin WDX.
WdxInfoPacker allow to generate a file using all available wdx plugin with a gui. THis is the best tool to generate HTML file List, it has a good website with help. but it is a packer plugin WCX
TCBL use SuperWDX as proxy for historical reason (first to provide source code and proxy like feature) and for laziness reason (it works almost good for what i do with it !).
TCBL is a mix of lst2multi and makebat with some enhancement, the aim is to "Select" some file and process them with an auto-generated script.
It also could be used to produce file listing but this is not the main purpose.
test it and if you like it share your command if you wish !
WdxInfoPacker allow to generate a file using all available wdx plugin with a gui. THis is the best tool to generate HTML file List, it has a good website with help. but it is a packer plugin WCX
It comes with a small exe that can copy the -output- to the clipboard ... with source code (D6)
TCBL use SuperWDX as proxy for historical reason (first to provide source code and proxy like feature) and for laziness reason (it works almost good for what i do with it !).
I have written a wdx proxy some time ago, to use wdx plugin easily with other tools...
Now I understand the 'user column' concept in TC - It's actually a named set of user columns - each corresponds to a field returned by TC or a wdx plugin.
I want to use TCBL for Imagemagick convert.exe. I have made an toolbar button for this. Only I can't get it to work. I want to convert the selected file with a resize of 25% and a quality of 75%.
to also use it outside of TC...
