Isn't it the same to what you suggested before?
As I told in my previous post, this approach is very inconvenient both for programming and for using.
To me it's not, first solution means keeping a modifier pressed, second solution means pressing a hotkey once and I hoped you would have meant it like that, sorry... Maybe it's inconvenient to program but it will multiply the power of NoClose.pif and for me the only inconvenience is that a little waiting period is needed. What is a second of waiting when you got so much advantages?
But one can start the program noclose.pif manually with some other command-line switches. And it is possible (and quite simple) to implement starting some other command processor if the parameter not /C, but for example, /cmd1. In this case one should run noclose.pif from some other place, for example, from the Start menu. That is create a Start menu item like noclose.pif /cmd1 %P%N and assign some hotkey on this item, so using this new hotkey will start the program with the other command processor.
I really was afraid that you meant it exactly like that, too bad. I don't see any use for that because
1) I don't need NoClose.pif when I want to start *whatever* shell with fixed parameters. I would simply make a start menu entry like that:
Code: Select all
command: shell.exe /whateverparameter (this string equals /cmd1)
parameter: "fixed command like dir, ipconfig /all, etc..." <parameters>
/cmd1 would mean less typing, sure, so at least it can be useful, but what does %P%N do? Do you want users to mark the command to be executed?
2) Your proposal has nothing to do with the TC command box and pressing Shift-Enter anymore. I use command box because the commands I enter there always change so I need an application that will read the content out of that box, insert the shell before and additional parameters last and that's why I was so excited about your app. With using start menu entries I would need to use ? in parameter line be able to modify the command I want to execute.
Of course, there are some inconveniences in assigning hotkeys for Start menu items (you mentioned them), but this is unavoidable.
With AutoIt this is completely avoidable because I can create a script which reads the TC command box (or the TAR box) and passes it to a shell when pressing a hotkey, no problem.
That's why for me NoClose.pif should concentrate on extending the use of the TC command box and Shift-Enter plus additinal triggers, either pressed hotkeys that are executed once or modifiers that need to be held down until NoClose.pif takes over.
Do you change the order of Start menu items frequently?
I do because I prefer alphabetically sorting. And because the start menu is not a modern implementation I am forced to use the mouse in most of the cases to execute. I use only a few hotkeys there, the rest I do with buttons or the application TypeAndRun.
If yes, then one additional item means nothing.
How can one entry be sufficient if the command to be executed always changes? I really don't understand the use of that %P%N parameter, sorry. %P%N means that I have to mark a file (the program to start) so I would have to go search it first on my hd and it would make using commands like "dir" impossible because it's inside the shell.
So, because I don't think that you really think that complicated I probably have got you wrong again...
Icfu