Oolite Bulletins

Hi,

I have just installed the latest build of Oolite on my computer, and now I'm looking for the key to see the communications log. I can see in the reference sheet that this key is "`" (without quotation marks). I can also see that on non-US keyboards, some keys may vary, and I think that this may be one of those keys.

I have looked under Keyboard Controls in the Wiki ( http://wiki.alioth.net/index.php/Oolite ... d_Controls ), but this page also lists "`" as the key to use.

I am on a Danish keyboard, and to make this character, I have to press Shift + the key with the character symbol. This does not produce the character, however, since I also have to press space afterwards. That is: Shift + key followed by space. I guess this might be why it will not work.

There is a character that look almost identical to ` - namely ' , but this does not work either.

Does anyone of you know how to see the Comms Log, that is, which key to press when on a non-US keyboard?

In cases like this, maybe the best solution is to assign the comms log to a different key altogether. Open the keyconfig.plist file in a text editor (avoid Notepad) and find the entry key_comms_log = "`";. Change the character inside the quotes with an unused key of your choice, e.g. "b". Save the file, restart Oolite and you should be able to use the new key to bring up the comms log.

Unfortunately SDL (the cross platform library used by Oolite) tends to assume you've got a US keyboard, and totally ignores what you really have. Windows' SDL library is especially bad in this respect.

When Oolite asks for the "`" key, sdl looks for the key position, instead of the character. The "`" character is on the key just above the 'tab' key on a US keyboard: on a typical danish keyboard that's the § / ½ key - pressing that will make Oolite believe you've just pressed "`".

I had a similar problem with my German keyboard. In the end I assigned the comms log to the RETURN key, which isn't used otherwise in Oolite and seemed kind of convenient for displaying the log.

Thanks for the replies.

Kaks was right - I found the comms log by pressing the § key (above the Tab key)