[REQ] Unified Parameters System

[Flint]

Vochomurka
I don't understand: how can global variable in a script help to get the list of currently selected files in TC?

(BTW, about "replacing content", why not restore the clip after processing the parameters?)

If it would be so simple, there were no programs that use the clipboard and do not restore it in some cases.

[majkinetor !]

I don't agree , I don't disagree, I don't need, no more, no less.

Very un-apropriate from moderator to use its own needs as a value measure.

[Vochomurka]

2Flint
This script creates a global variable v being vector with size equal to Counter. There is no need to make Counter global - if some other script catches the v vector, it can find its size. Of course, each v element is a file name selected before the script was called.
Another way is to send to TC window some LB_ (listbox) messages. AFAIK, they allow to get the quantity of files selected and their numbers in list, but not their names. I think, WSH can even retreive the names (may be I'm wrong). That's why I said "more powerful scripting languages".

there were no programs that use the clipboard and do not restore it in some cases

Yes, but it's two code lines to do that. Example is here.

[Flint]

Vochomurka
Please, read personal message on the Russian forum. Either I don't understand you, or you don't understand me...

[XPEHOPE3KA]

Two weeks passed since this improvement was requested.
May I dare to ask about your opinion, Christian?

[majkinetor !]

HA HA HA

[XPEHOPE3KA]

I will post that message every two weeks from now.

[majkinetor !]

HA HA HA

[szlori]

Well, this is all very nice, but:

• What it adds is only serving power users and is not really a must
• TC has already a system that partially does this
• I think it is pretty hard to do these code changes

So, what I want to say is that I don't think this system will be implemented like this as a whole...

However, I suggest we extract what is the most useful part and adapt it for the existing system, extending that.
So we could come up with a much simpler suggestion that would have much more chance of being considered.

I guess the %@ parameter is the most useful feature.
What do you think?

[majkinetor !]

Maybe I've misunderstood you, but how all this can be done?

It can be done, don't tell me to tell you how, as you know already. It is inconvinient but it is possible.

So I agree with

What it adds is only serving power users and is not really a must

and still don't with

Code: Select all

I think it is pretty hard to do these code changes

So 1 vote more for this from me.
But, why we are still talking about this ? If it was up to me, i would know what to do, but since it is up to Mister Ghisler don't expect this. This will not be benefitial to regular newbee user, or even advanced user. Power users will only have benefits for that, and you know what Mister Ghisler think about power users....[/quote]

[XPEHOPE3KA]

What it adds is only serving power users

Disagree. This improvement will serve for scripting, and scripts are used by all kinds of users.

[szlori]

What it adds is only serving power users

Disagree. This improvement will serve for scripting, and scripts are used by all kinds of users.

Disagree. Scripts are used by power users.
Believe me, if you use scripts, you can consider yourself a power user.
There are many more users who don't even know what a script is...

On the other hand, I support this request.
I just want to size it down to give it more chance.

[XPEHOPE3KA]

2szlori

Scripts are used by power users.

Sorry, but those who think so are total noobs without experience. Almost any Powerpack contains several scripts, so the users use them but they will never know they do .
BTW, the users don't need to know what is a script. They need to know HOW it should be used, and FOR WHAT REASON a particular script serves.

[majkinetor !]

XPEHOPE3KA

You told him Ex.

[szlori]

2szlori

Scripts are used by power users.

Sorry, but those who think so are total noobs without experience. Almost any Powerpack contains several scripts, so the users use them but they will never know they do .
BTW, the users don't need to know what is a script. They need to know HOW it should be used, and FOR WHAT REASON a particular script serves.

Yeah, sorry, you're right. (You shouldn't have called me a noob, though. )
I was only thinking about people directly using scripts.
I keep forgetting about those "power" packs. I like to select the extensions myself.

But we are drifting away from the main point...