Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Ornedan

Pages: [1]
1
DF General Discussion / Re: FotF: Dwarf Fortress 40d16
« on: January 03, 2010, 01:33:15 pm »
Quote from: qwert on January 02, 2010, 03:22:32 pm
Until someone manages a 3xSomething tileset, the smallest available is 4xSomething which has a 320px horizontal width. So unless you know of a method of getting a tileset to only 3 pixels wide while still usable, and you would want a width between 81 and 84 tiles, I think it is safe to assume this is a non-issue.  :P
It's more an issue of magic values (or value-ranges in this case) being bloody ugly.

Edit: Oh, hey, new page where I got ninjad by several hours. Succes!

2
DF General Discussion / Re: FotF: Dwarf Fortress 40d16
« on: December 31, 2009, 12:23:37 pm »
The whitespace for structure thing in Python only really amplifies existing problems. Which I don't consider a particularly bad thing, since then you have to fix the real problem, being that your code is an unreadable mess of randomly indented crap. As far as sharing goes, there are these things called coding conventions.

Lua is however a better choice, because it's tiny compared to Python yet still has an adequate base library. About the only advantage Python would have is an enforced base standard of readability on that "shared code".

3
DF General Discussion / Re: Future of the fort: Help test the output code for the next version of DF (40d11)
« on: March 29, 2009, 01:57:26 pm »
Tried Linux 40d11. Keyboard fails on my Lenovo T61 laptop with finnish keyboard layout. Distro is Debian (testing + unstable) w/ KDE 3.5.10.

In 40d, it just misidentified the keys, but that was workable around by performing some experimental surgery on interface.txt. But d11 refuses to acknowledge the existence of some keys. It doesn't react in any way to pressing [åäö], with or without shift.

xorg.conf keyboard section:
Spoiler (click to show/hide)

Problematic keys: (Listing all of them while at it)
Character, keycode and keysym as recorded by xev. Character is the "XLookupString gives" part.
DF interpretation is what is shown when that key is bound in the key bindings screen.
CharacterKeycodeKeysymDF interpretation
å340xe5
Å340xc5
ä480xe4
Ä480xc4
ö470xf6
Ö470xd6
'510x27Key DE
*510x2aShift + Key DE
:600x3a>
;590x3b<
<940x3c,
>940x3e<
|940x7c,
+200x2b=
?200x3fShift + =

4
DF Suggestions / Re: Support for non-US keyboards
« on: October 14, 2008, 02:32:54 am »
I know. The problem is that the weird key equivalences greatly reduce the set of keys I can bind stuff to. Hadn't yet noticed when I was writing the last post, but the arrow keys are also treated as numbers.

I did eventually manage to set up a usable layout, but it took rather longer than necessary (though part of that was messing with the display part of interface.txt to get the game to display the correct character instead of "Shift + Key C0" or the like).

5
DF Suggestions / Support for non-US keyboards
« on: October 13, 2008, 01:40:35 pm »
As the topic says. It was pretty much insignificant on a desktop keyboard with a numpad, where there wasn't any overlap, so it was merely an issue of memorising what actual key on the keyboard whatever key DF said mapped to.
However, on a laptop without numpad, this is really starting to cause me pain. Especially the assumption that Home,End,PgUp,PgDn are equivalent to 7,1,9,3 respectively.

Please let the OS do the keyboard signal -> character code translation for you?

Pages: [1]