This ist most likely because I've configured TC that I only want to allow one TC instance. However, the quasi-standalone lister should not be considered as TC instance.
Additionally, a lister.exe which simply runs totalcmd in lister mode would be useful for programs where you can only specify a .exe without any arguments which will be used to open something (e.g. logfiles).
Code: Select all
@start "" %0\..\TOTALCMD.exe /S=L %1
I recommend to use value 2, 3 or larger for OnlyOnce INI parameter (new in TC 7.55) - to allow having specified ammount of TC instances - so your TC will start even if another TC is already started in lister mode. Also you may start TC with /N parameter - to start new instance anyway.
Some programs do not ALLOW you to specify arguments. And such a lister.exe is written in 5 minutes.
And using a higher OnlyOnce parameter is also not really a solution: I never want more than one instance of the actual file manager. However, I don't want to limit the lister instances at all (so I'd have to disable OnlyOnce completely!) since those are not directly related to the file manager at all. I'd even use the standalone lister, but unfortunately it was abandoned long time ago...
Code: Select all
MIME-Version: 1.0 Content-Type: application/octet-stream; name="Lister.7z" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Lister.7z" N3q8ryccAANietSrSAIAAAAAAABfAAAAAAAAAGtTqbAAJpaOcAAX9+wFu+r0/5QBL0TuTr0JP39V wXIs+2C8FAvofZL9OQyrmdRJ6fFEUwUox4AepJrWfamkx9MSo1AMPur1FMg8of0jfCyT3T8/4QjX pnYCV1i9CxcUJvNEOklmnQP+DzHzvphuXQcZpsZbZXCz1ZXBShMV3bCSb1Q8x/i8ZlCx9Rzf9SWS OAFLtRQtK/eWqUXjzxT5T9OhsQUspNs8BP5nzkcN1qKHi5tgJ58Zm2SonJvlUWudAtnWNdJBHuds l3bDm4wFNxfkx0fY0KJmpPa8iVuUafSKpl+y299wGC/pAMT5lnygpURDGLAgTIie1OAQipgxXAqh izZOcp5PJm7a0tCryOWZ0VD/XXFK41Uj3CtoGKfAXdP0vGDyDvp2TO1PYLgX0oBK31D6OTTA2Vs2 RxRCyruvyB2gSQi7514vQrf9jBPi+g/ta5Xytc0FCTKWrBpIAB7Xbd3MRaW0oIpn4fgZniBDIE8m r5wpTM3x8LMMpgHf4Z4DWMvas5IUzCrXRzCuZpF2BAxCR7WJ+iki8oHxta1bePs6e07g9kvx7Tx6 zGBS8IyPCs+9wmgIUFwhQjOVqFsQRU+rF9BkQEcLlU/XPor4e0AG7XNX4juY0h0dK/OnF/CY3PYQ TUhBwubzRb2wo48rtEnoohvxam+WkHHc/U7Z1acOn+l+pcV1dmT2lcXNYjgggyxU1/qJzUUtlteu CmGvqZ8qZ7T4RmEACxOniKj954CiuIYFSIynrNl9WLawR0HzrvTwI27K04UOAAEEBgABCYJIAAcL AQACIwMBAQVdAAABAAQDAwEDAQAMiACIAAAICgF5Qr+WAAAFAREXAEwAaQBzAHQAZQByAC4AZQB4 AGUAAAAUCgEA8njfQ4XZygEVBgEAIAgAAAAA
I use the lister as a log viewer in mIRC. In my log folder there are thousands of log files (I'm staff in a large IRC network so I join lots of channels and get pms from users - that causes lots of log files) due to this and I don't want to go to that folder, search for my file, etc. just to view a log when I can just have a command in my IRC client which opens the log file with an applications.Why you not using normal TC lister? As for me, I have TC running almost all time and I use F3 to start lister.
However, I only have TC running when I need it so it might be possible that I open a log file and then want to start TC for some reason - and that fails. However, i can start multiple TCs in lister mode which makes this behaviour even more inconsistent.
But I don't know how TC determines if there is a working copy (I thought that it searches windows with "TTOTAL_CMD" class but TC in lister mode have no such window).
So, let's wait for Mr Ghisler's answer.
- Site Admin
- Posts: 36425
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
Then you could simply only create/check the mutex if TC is not started in Lister mode.
Maybe it would be easier to search for windows with class "TTOTAL_CMD"? Every main instance have such window and every lister-mode instance have no such window. I don't see any benefits to search for hidden TApplication window instead.ghisler(Author) wrote:When you use the option "only one copy", it allows to open additional copies of TC in Lister, Compare or Sync mode, but not other main program copies. Currently it's not possible to change it, because the detection is done via the hidden TApplication object. I will check if there is some other way, but I cannot promise anything yet.