| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
.cc, moving its contents into the new stepdown.cc and strings.cc.
(The latter also got many donations from libutil.h.)
Down with stuff! Up the new flesh!
|
| | |
|
| |
|
|
|
|
| |
There's really no reason not to show the line; in other options, having
the default always be the case can be annoying, but if you don't want
to look at the gold/turns display, you can just not.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When you strip away the fundamentally broken tension mechanic, you're
left with a species that is essentially "Hill Orcs WITH FIRE". No effort
has come forward with code to fix either aspect of them despite the
length of time they've been around in trunk, and the code is littered
with a very large number of special cases in their presence.
Current lava orcs should be able to finish their games fine, but new
starts are disallowed.
There are a couple of bits I've left present but which will have no
function for the moment, mostly related to interactions with lava (as
there are a couple of species proposals floating around that benefit
from having those interactions).
|
| |
|
|
|
| |
This coincides with the actual client-side height and still fits into
24 lines. Of course, this still needs a more permanent solution.
|
| |
|
|
|
| |
Since they are recorded at 80x24, the game could otherwise fail to
start because there's not enough vertical space.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was possible to get e.g. "Terminal too small (80,25); need at least
(79,24)". Now we have a slightly different message when the problem
is the layout rather than the absolute (79,24) limit; and we include
the actual required size.
The required size reported by this commit isn't perfect because there
doesn't seem to be a good way of asking for the true minimum size along
a sufficiently-large axis (leftover_x() is zero even though things could
be shrunk). We currently report the absolute minimum for such axes,
even though the true limit could in fact be somewhere between that and
the current size.
|
| |
|
|
| |
This is exceedingly kludgy, but it works.
|
| |
|
|
| |
Signed-off-by: Raphael Langella <raphael.langella@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
I had to rename distance() (in coord.h) to distance2() because it conflicts
with the STL function to compare 2 iterators. Not a bad change given how it
returns the square of the distance anyway.
I also had to rename the message global variable (in message.cc) to buffer.
I tried to fix and improve the coding style has much as I could, but I
probably missed a few given how huge and tedious it is.
I also didn't touch crawl-gdb.py, and the stuff in prebuilt, rltiles/tool
and util/levcomp.*, because I have no clue about those.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
server record ttyrecs.
Crawl compiled with WEBTILES=y should now be playable
normally (i.e. indistinguishable from one compiled without WEBTILES)
when run from a terminal. (This is not yet completely the case.)
The Webtiles data is written on a Unix-domain datagram socket; the
Crawl parameter -webtiles-socket determines a path on which the Crawl
process receives control messages.
The Webtiles server then runs Crawl in a pseudo-terminal and records its
console output into a ttyrec file.
The goal of all this is of course to be able to watch Webtiles games
from ssh, and later the reverse.
|
| |
|
|
|
| |
The display sucks, it could be inserted into the gold_turns line, except
that some heretics might have it disabled.
|
| |
|
|
|
| |
I don't really understand the point of lay_inline.valid and
crawl_state.need_save, so I've left them as a safety.
|
| |
|
|
|
|
|
|
|
|
| |
Sadly, we can't do this in the ASSERT() #define itself, as in GCC
versions up to 4.5 warning pragmas are global, setting them in any
place in the file affects the entire compilation unit no matter where
you specify it.
GCC 4.6 and new Clangs allow you to flip warnings as often as you please,
so we'll be able to do this properly then.
|
| |
|
|
|
|
| |
I did review it manually to find places where they made sense (like some
tables), but for a massive sed job like this there might be places that
I missed.
|
| | |
|
| |
|
|
|
|
|
| |
Rather than using explicit offsets (e.g. buffy[0] and buffy[1]), store
colour, glyph, and tiles for each cell in the view buffer in a struct
with named members. This refactoring will also theoretically allow for
the tiles version to display glyphs instead of tiles.
|
| |
|
|
|
|
| |
This eliminates a duplicate function that had gotten out of sync with the
original viewwindow. (In particular, this fixes a bug where using X in
the Abyss would show out of sight tiles and the presence of items.)
|
| |
|
|
|
|
|
|
|
|
| |
This is FR 2814313.
This required adding a new option msg_min_height
defaulting to 6 to keep the same default layout.
I don't believe anything requires a message window
of more than 5 lines (acquirement is fine with that).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Set messages_at_top=true to use.
This is not quite aesthetically pleasing since character name
and title which form a kind of heading for the screen are now
in the middle. It might be better to display them in an extra
line across the top.
Also, the layout should really be moved out to lua and made
completely user configurable.
|
| |
|
|
|
|
|
|
|
| |
This was causing scrolling problems, but now that scrolling is off,
this shouldn't occur anymore.
For reference, if problems with writing to the bottom right corner
of the terminal show up:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311345
|
| |
|
|
| |
This change also gets rid of the ugly intermediate macroing.
|
| |
|
|
| |
Also make view.cc use crawl_view_geometry.tbuf for tiles drawing.
|
| |
|
|
|
| |
Before, the code implicitly assumed that you.pos() hadn't already
been updated.
|
| |
|
