[wdx] WinScript Advanced Content Plugin (x86\x64) (new)

[Fla$her]

2Native2904
What do you mean by "I have"?

I've never understood the practice of adding a common unit to column fields.
It is always more practical to indicate this in one place — the tabstop header.

[Native2904]

What do you mean by "I have"?

In line 21 of your script, I extended it on my side so that the output now looks the same as in the Exif plugin.

Code: Select all

2023-07-25 13-07-41.heic |‪1536 x 2049 | 1.057 kB | Apple | iPhone 13 | 51°11'41.110"N | 5°58'58.850"E	| 22.26m | 42.928 km

I've never understood the practice of adding a common unit to column fields.
It is always more practical to indicate this in one place — the tabstop header.

Yes, that certainly makes sense, but in the context of the custom column view I consider it irrelevant — or rather, more coherent this way.

[Fla$her]

In line 21 of your script ...

Ah, understood.

Code: Select all

... | 22.26m | ...

What's it?

but in the context of the custom column view

Do I even have a different context?
There is one moment here — sorting. If I had done this through Autorun, I would have specified a floating-point numeric type, which would have given the correct result, in which case it would be inappropriate to specify letters there. Unfortunately, the author of WinScriptsAdv didn't provide for specifying a field type other than a string.

[Native2904]

Code: Select all

... | 22.26m | ...

What's it?

Altitude

Do I even have a different context?
There is one moment here — sorting. If I had done this through Autorun, I would have specified a floating-point numeric type, which would have given the correct result, in which case it would be inappropriate to specify letters there. Unfortunately, the author of WinScriptsAdv didn't provide for specifying a field type other than a string.

Yes, a comma would have looked better than a dot — at first it actually made me unsure whether the values were correct at all. A dot can also be read as a thousands separator, so not 16 km and 150 m, but 16.150 km… but I don’t want to be pedantic. That said, in the Exif plugin decimal places are also shown with dots — unfortunately, the space between the value and the unit is missing there.

[Fla$her]

Yes, a comma would have looked better than a dot ...

You are thinking in the wrong direction. A dot or a comma has nothing to do with it. It's easy to fix this via .replace('.', ','). It's only about the field type, which affects the correct sorting of numbers. That means, in this case, you get

1,010 10,100 2,100

` instead

1,010 2,100 10,100

.

[Native2904]

Ok, I believe I get it... when i sort a column by clicking the header, I see automatically the Unit of the Digits so that it was not necessary to put this Unit after each Digit in the panel right?
That makes sense and looks tidy and reduced to the bare essentials—minimalistic, cutting away everything that can be cut away.

[Fla$her]

This only applied to conditions where there is a type setting, i.e., Autorun. In this plugin, it won't matter. As I wrote:

Unfortunately, the author of WinScriptsAdv didn't provide for specifying a field type other than a string.

[AkulaBig]

There are 21 columns missing to display data. The simplest solution is to use two scripts. That's how it all works. But there is a nuance. Then you need to run the program from which I receive the data twice. That is, run the program in each script. And this increases execution time. Scripts on AutoIt. Can you somehow-then display more than 21 values ​​using WinScriptsAdv itself?

[Fla$her]

These are the limitations of the plugin:

Features:

* Multiple columns per one script (up to 21);

Each script can have multiple columns (up to 21) and display info simultaneously with other scripts that
also can be with multiple columns.

Features:

* Multiple columns per one script (up to 21);

In Core.pas, the limit is set on line 9 (MAX_SCRIPT_FIELDS = 21). Try to compile with the new value or ask Progman13 (he had already worked with it).

[AkulaBig]

In Core.pas, the limit is set on line 9 (MAX_SCRIPT_FIELDS = 21). Try to compile with the new value or ask Progman13 (he had already worked with it).

Interesting solution. Thank you. It is clear in which direction to move. TC understands 32 columns. It was necessary to do so.

[AkulaBig]

Try to compile with the new value

Everything worked out. WinScript Advanced now works with 32 fields.

[Fla$her]

Great! It would be logical to share a link to the solution.

[AkulaBig]

Modified version of WinScriptsAdv. The number of columns has been increased to 40 (content...content39).
https://www.dropbox.com/scl/fi/h8b5rucs8oswvj0xunqyp/WinScriptsAdv_mod.7z?rlkey=dgyny3x9s8jyd5ejvu4z7b40i&st=0w0xx197&dl=1

[Fla$her]

Thanks! The plugin has become smaller and started up, which is already good. I'll check the limits later.