Radio Traffic Exchange (real-players' radio traffic)

[ExFishermanBob]

OK, I've spotted a problem - messages that are too long are not readable, so I need to add Part x of y" handling. Oh good.

[Fahnenbohn]

Originally Posted by ExFishermanBob

OK, I've spotted a problem - messages that are too long are not readable, so I need to add Part x of y" handling. Oh good.

Problem already spotted, isn't it ?

Originally Posted by Fahnenbohn

Your last message is too big. I can't read the end.

By the way, are you still working on short coded messages ?

F.

Originally Posted by ExFishermanBob

I will have to check on the length of messages (perhaps using 1 of x, 2 of x messages).

Ah, some captains are very reckless to write such long messages ! The allies have plenty of time to determine their position !

[ExFishermanBob]

Heh! I was hoping you wouldn't spot that you'd already mentioned this. Still, it got you out of hibernation, eh?

I'd not bothered implementing it (and the short-message stuff) as I'd hoped to find a way of reducing the font-size in the radio-message display. It can be done, but I should not really force that onto people. Also, some of us like telling long stories....well, alright, get carried away.

P.S. ...and I did implement your message display suggestion. Sort-of.

[Fahnenbohn]

Originally Posted by BL!TZKR!EG

1)
I am a bit confused: What is the name of your program now?
a) Captain's Toolkit for Silent Hunter 3 (on your website)
b) RTE/Radio Traffic Exchange (here in the thread, alternative 1)
c) Real Players' Radio Traffic (here in the thread, alternative 2)
d) ToolkitForKapitans (as per the file name)

The best is c) for me.

Originally Posted by BL!TZKR!EG

5)
I then CHECKED for messages and got 130 results. Upon pushing the "RECEIVE MESSAGES"-button, it prompts "Waiting messages: 130" and since minutes nothing happens.

All I can click is "CHECK MESSAGES", then the prompts changes to "Waiting messages: 0" and the program appears to be stuck in a loop. See the attached picture.

It's normal. When clicking RECEIVE -> messages are written in the file that you have chosen. Then, only new messages are shown (= you can't download them twice).

@ ExFishermanBob : it would be good if we could choose from what flotilla we want to see the messages, before having the windows for downloads.

F.

[ExFishermanBob]

Originally Posted by BL!TZKR!EG

Hey EFB

As you desired, here's some feedback:

1)
I am a bit confused: What is the name of your program now?
a) Captain's Toolkit for Silent Hunter 3 (on your website)
b) RTE/Radio Traffic Exchange (here in the thread, alternative 1)
c) Real Players' Radio Traffic (here in the thread, alternative 2)
d) ToolkitForKapitans (as per the file name)

2)
Upon start I get this text in the DOS-box:Is this warning message really needed or desired upon VERY first start?

3)
Connection works now. Got confirmation window.

4)
The selection of the "messages_xx.txt" is a bit non-intuitive to the unknowing player. I do know where to look, but could you please add an example in which directory to look for this file, such as

your-installation-path\data\Campaigns\Campaign

?

5)
I then CHECKED for messages and got 130 results. Upon pushing the "RECEIVE MESSAGES"-button, it prompts "Waiting messages: 130" and since minutes nothing happens.

All I can click is "CHECK MESSAGES", then the prompts changes to "Waiting messages: 0" and the program appears to be stuck in a loop. See the attached picture.

More feedback as soon as can come across this point.

Firstly, thank you for the feedback.

1. I call it the Captain's Toolkit as that's what it started out as - the radio traffic bit got added later. That's what it calls itself in the help-About dialogue. RTE is the name of the unmanaged 'flotilla' for public messages.

2. There was a bug in the formatting of messages in the messages_xx.txt file that has to be corrected. If you haven't got the message-file location set, then the conversion cannot be performed...however, that also tends to imply that you've never run the toolkit before, which means no conversion is necessary.

4. The on-line friendly instructions do tell you that: I wanted the toolkit to try to suggest the location but there are difficulties with reading the registry, and so on. It's a later-version job. I'll add an example in the tool-tip text (but the file's location varies).

5. You will have a Receive Messages button that lets you download those messages - IF you have set the location of the messages file (to which the messages have to be written).

[ExFishermanBob]

Originally Posted by Fahnenbohn

The best is c) for me.



It's normal. When clicking RECEIVE -> messages are written in the file that you have chosen. Then, only new messages are shown (= you can't download them twice).

@ ExFishermanBob : it would be good if we could choose from what flotilla we want to see the messages, before having the windows for downloads.

F.

If you are in a flotilla (that is, you complete the section "I am a member of a flotilla and want to send and receive radio traffic via the flotilla's exchange" with the username and password, you can then 'update flotillas' and choose the flotilla name from the list. You will then ONLY receive that flotilla's messages.

If you are NOT in a flotilla, you can be a member of the "RTE" (unmanaged) flotilla, using the first option (or the second if you have a name and password for posting to the RTE flotilla). You will then receive any RTE messages AND any from a flotilla with its messages marked as 'Public' (currently Lone Wolf).

I agree with you, though: for options one and two in the settings, a list of 'public' flotillas could be provided that you can choose to unsubscribe from.

[ExFishermanBob]

The DOS box is enabled for versions where we need debugging of some sort - usually it is / will be disabled.

I am currently thinking of moving the public (RTE) reception / sending into a separate program from the flotilla stuff, as the combination seems to confuse people.

Edit:
Also, the RTE program could be skinned to look like a radio.

Actually, that might clear the name confusion as well.

[Becker67]

Have got version 7 installed and wish to connect to the DEF flotilla message exchange. Are the user name and password the same as my forum login or is this something separate? Loving this been playing with the message generator and sending messages to my boat in-game no problems.

[ExFishermanBob]

Originally Posted by Becker67

Have got version 7 installed and wish to connect to the DEF flotilla message exchange. Are the user name and password the same as my forum login or is this something separate? Loving this been playing with the message generator and sending messages to my boat in-game no problems.

Many thanks - have sent a PM to you with the information you require.

[areo16]

Originally Posted by BL!TZKR!EG

Of course! That's what you asked me for. And I will continue as time passes is you want me to.


I find that "Captain's Toolkit" does not really explain what it is doing. But I come to that on another occasion. Let's have a chat this week.

2.ok


4. "It's a later-version job. I'll add an example in the tool-tip text (but the file's location varies" - which is why I brought a proprietary example

5. You will have a Receive Messages button that lets you download those messages - IF you have set the location of the messages file (to which the messages have to be written) - I still hold to the view that there must come some info instead of "let nothing happen".

Best regards, keep up that good job, I like your program and make S3F support it.

Therefore: Can you include a way to pass command-line-parameters such as

ToolkitForKapitans.exe /p: d:\SilentHunterIII-stock\

to your program?

I think a messages rollback function would be great. So you can revert to stock or pre-toolkit messages at the press of a button. So keep a backup of the original en_messages file.

[ExFishermanBob]

Originally Posted by areo16

I think a messages rollback function would be great. So you can revert to stock or pre-toolkit messages at the press of a button. So keep a backup of the original en_messages file.

There is a button for that "Manage the messages file". However, if you click on it you will notice that it isn't working yet.

[ExFishermanBob]

I can add command-line parameters, but you will have to tell me what they are intended to mean.

[ExFishermanBob]

Dear All,

OK, I've decided to split up the "badly-named-toolkit-radio-bdu-thingy" into 4 programs: although they all talk to the same database, I've realised that that does not mean that they have to be jammed together into one jumbled program. Also, the current program appears to be confusing for some people which is, of course, entirely my fault. So, I shall split the tools as follows:-

1. "Real Players' Radio Traffic" - can receive public messages. Can also (with a name and password) send messages and join in with a public SH3DC (Dynamic campaign).
2. "Captains' Toolkit" - Generate forum messages from information stored in the game's save files (optionally writing them to your personal messages file). Can also turn a BdU forum posting into an in-game message. Does not require name and password, really just a forum tool (this is, in fact, what most people seem to use the current program for, anyway).
3. "Flotilla-members' Toolkit" - with a name and password, members of a flotilla can send and receive messages (optionally to their message file) to and from their flotilla. They can view the score-table for their flotilla. Messages sent are also copied to the clipboard in case cross-posting to a forum is required. Can also optionally join in with the public SH3DC (possibly subject to the flotilla's decision to do so).
4. "BdU Toolkit" - allows a flotilla-admin to manage members, boats, tonnage and so on, send BdU messages to flotilla-members, view flotilla-members' messages, track flotilla locations, view the 'war-diary' and so on.

In addition, I've had requests for at least two 'bots' to be able to extract information for those agreeing to allow it (one for mapping, one for another mod), so I shall also document the views available in the database to do this, along with how to access it.

This splitting should clarify what each tool does and also allow me more on-screen space for each of the tools, particulary for the settings dialogues. I might even be able to make the tools a little prettier (looking like a radio, for instance).

[ExFishermanBob]

I see what you are getting at now, with the command-line parameter. What might be easier is to specify the minimum configuration file settings needed, so that it can just be written by any calling program. Or both (probably both in fact).

Thank you for your feedback.

[ExFishermanBob]

Yes, I'll add command-line parameter parsing to one of the next updates.

For the 4-part toolkit, I'll try to make that be akin to KParts, so that the group of programs can ALSO be presented in a single enclosure, as if they were one program. For anyone using Kontact under KDE, that is how it works - the individual components (Kmail, Calendar, To-Do, etc.) can be run separately or as one program via Kontact.