Search options (Page 7 of 12)

Hello and welcome,

You're right version 2-3 changes associated to command line usage have not been listed.

Under windows, the standard option prefix is "/" (not "\"). It is the only one authorized by Siren 2.
As Siren3 is multiplatform you can use "-" or "/".
I did not specify this in the Help but you can see it in the command line usage : siren /h
I'll add this in the "History" page.

You are right. I'll add this in the "History" page.

The "/I" parameter has been changed to "/P" because the "ini" extension is Windows centric and I wanted something more generic.
I'll add this in the "History" page.

No change have been done here.
By default the "siren.ini" is located in the executable directory and contains all settings.

I've just made some tests and did not see any problem.
Can you post an example ?

Regards,

Remi

Yes, a DOS batch file can maybe do the trick.

Something like (I surely missed things) ? :

• dir /AD /B /S %1 | sort /R : to get the directory tree names in reverse order

• a "FOR" to parse the result

• execute some code explained here to change the case of the name

• execute the "REN"

Maybe this batch could be used as a "Tool" in Siren. After execution the directory should have to be reloaded.

It could be easier to use another "language", no ?

Glad to know that a solution has been found.

About examples, what do you think is missing ?
If you've got remarks or suggestions, please post them.

Regards,

Remi

The problem is the volume separator (":").
A "simple" solution can be (another trick ) to substitute and then replace it. With a "@" for example:
%e=P@\\Photo\\_Photo\\%dm{"%Y"}\\%dm{"%Y%m"}\\%dm{"%Y_%m%d_"}\\%dm{"%Y-%m-%d_%H%M%S"}%T{"C:\\sr_dta.txt",%nc{1,0}}.%e;%fc[2,1,"="]("@",":")

Regards,

Remi

About C:
During the renaming/copy Siren doesn't do any magic.
It goes through the selected file list and simply calls the rename/copy system function with the current and new names.

During this operation if a file already exists your operating system should refuse to rename/copy and give back an error to Siren. Finally Siren will display a window summarizing all the errors, if any.
All the files for which a problem appeared are displayed with an orange like background color and when they have the focus the associated message is displayed in the status line.

Under Windows, you can try to achieve the same in a command line window without Siren using "copy" and "ren" commands.

Tell me if you need more information.

You are right.
In versions 2 the regular expression library used was Boost.org.
Since version 3 Siren uses the one included in wxWidgets. It may not include all the extra features present in Boost.org but it is compliant with the "standard" and is perfectly integrated in its code environment.

I am sorry for the users who get into the habit of using these advanced features but for now I don't think to go back on this.

About your "B)" point.

Using Siren 3.00 build 888 (it corrects a bug present in previous versions), a way to solve this could be :

1) Create a text file containing the converted numbers you want to use.
In your case :
aa
ab
ac
...
az
ba
bb
...

Let's say its name is "C:\sr_n2a.txt"

For test purpose I've created mine. I can send it you if needed.

2) Use an expression like : %b(1,1)%T{"C:\\sr_n2a.txt",%nc{1,0}}.%e

%b(1,1) : choose the collision part you want. For the test I've chosen the first character of the base name.

%T{"C:\\sr_n2a.txt",%nc{1,0}} : will extract the text lines from "C:\sr_n2a.txt" (don't forget to double the "\"),
The second parameter is the number of the line you want to extract. In this case it will be the collision number.
If this number is invalid (0 for example) the string returned is empty.
%nc{1,0} is the collision number non padded with zeros and starting at 0.
Therefore the first element of a collision group will have an empty identifier. The second will be "aa", the third "ab" ...

%e : is the extension of the name

3) If you want to add a separator between the two parts (for example a "_") and do not want it on the first element of the collision group then the expression can be :

%b(1,1)_%T{"C:\\sr_n2a.txt",%nc{1,0}}.%e;%b(s/_$//).%e

_ : is inserted in the first sub-expression just before the "%T"

; : the semicolon separates the two sub-expressions

%b(s/_$//).%e : this second sub-expression will remove the last "_" of the base name

Hoping this will help.

Remi

The modification has been added in the last build (881).
You can activate it through a new preference in "Preferences/General".

I've been able to reproduce the bug and I think I have fixed it.

Thanks a lot for your help.

Thanks to your explanation I've been able to reproduce and correct the "double click" bug but unfortunately I can't reproduce the "column width" one.
I am surely missing something. Can you please post a "step by step" example ?

About the GTK selection issue, I'll try look at amule source code.