Re: Refund Claim
St: I just filled out a Refund Claim form over at element5. MP: Based on what? Well, like someone else said: To get bugs fixed now (in software you paid for) you have to get the next version, and I should add: and pay for it once more. I don't want to go into details, but they didn't deliver what they promised. -- St Current version is 3.00.00 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
[St's TB Annoyances] thebat.IPC
From the TB help file: For those who are familiar with programming, here's a handy hint: The Bat! checks a file called TheBat.IPC which is located in the same directory in which The Bat! executable (TheBat.exe) file is located. Within this text file, each line represents one command that can be executed by the program, so you can write commands to this file directly and control The Bat! on your PC even over a local network. Note that TheBat.IPC is deleted as soon as all commands from it have been executed, so if this file does not exist, you will have to create it to make use of it. BUT: Every now and then TB apparently fails to read this file, and from then on it simply ignores further checking thebat.IPC. Unless you restart TB, it won't check thebat.IPC. Now, exactly how do you send TB new commands (like the rather liberating /EXIT (to restart)) when TB fails to read the file that contains the request? The help file further states: Note that you can run only one copy of The Bat! on your PC at one time, but if you try to start another copy of The Bat!, all Command Line parameters will be seamlessly passed to the running copy of the program and executed. Apparently, if TB failes to read the IPC-file just _once_, some error code instructs TB to give a dudu about trying to read the file later on! And exactly how do you send TB that IPC command when TB fails to read the file that contains the request!?! -- St Current version is 2.12.00 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
[St's TB Annoyances] View Message Source
View Message Source should not (default) to show the code of the attachments. Big messages take a long time to open on a modest PC. In message source attachments could be represented by an icon that one could click on to see the code. -- St Current version is 2.12.00 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
[St's TB Annoyances] Message Dispatcher
Double-clicking a message in Message Dispatcher does NOT open the message. And when you do open it by hitting Enter, and then select Message - Move to Folder, the message is copied to the folder (and not deleted from server). -- St Current version is 2.12.00 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
[St's TB Annoyances] Command line parameter: /PARK
Command line parameter PARK doesnt work with importing of messages. -- St Current version is 2.12.00 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
[St's TB Annoyances] Windows Show Desktop
TB does not react to Windows Show Desktop try Windows- button + M and see for yourself. -- St Current version is 2.12.00 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
thebat.IPC
Huh? I am sending a bunch of start-up parameters to TB, but TB fails to execute them. The commands just pile up in the thebat.IPC-file - why is that? Deleting or emptying thebat.IPC does not fix it. Exiting the TB and then restart does not fix it. Rebooting the entire PC fixes it - but that's not elegant! Is this a known problem? -- St Current version is 2.04.7 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
