draw but 9 images, with the non-corner ones being scaled as appropriate.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2856 542714f4-19e9-0310-aa3c-eee0fc999fb1
if they are fringed on by any SPECIFIED tileId (ie, not the default tileId)
that is impassible.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2852 542714f4-19e9-0310-aa3c-eee0fc999fb1
public follow mode constants, instead of having a different method for
enabling each different follow mode.
Added a new follow mode: track, which aligns the upper-left coordinate of the
view with the hotspot of the pathable.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2851 542714f4-19e9-0310-aa3c-eee0fc999fb1
thing with unescaped ticks (') which led me to modify MessageBundle to
automatically escape ticks before passing things to MessageFormat. This
allows us to use unescaped ticks willy nilly in our translation strings.
Yay! No more annoying worrying about whether we should use \' or '' or
having things be booched because we forgot one or the other.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2850 542714f4-19e9-0310-aa3c-eee0fc999fb1
don't leave any unversioned bundles lying around after a conversion.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2847 542714f4-19e9-0310-aa3c-eee0fc999fb1
named according to its version number so that when we patch an old version
to create a new version, we don't have to do any renaming, we just create
the new version directly and hopefully avoid this bullshit problem on
Windows where we're unable to rename a goddamned file.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2846 542714f4-19e9-0310-aa3c-eee0fc999fb1
milliseconds. I want to know what in the fuck those were.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2840 542714f4-19e9-0310-aa3c-eee0fc999fb1
services that registered (ignoring unregisters) but I can't get it to
cough up the problem on my machine, so it's a little hard to test. If you
fine cvs readers want to take a peek that would be great. Hurray for
debug code.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2836 542714f4-19e9-0310-aa3c-eee0fc999fb1
post events to an object that is already destroyed, we'll allow
transactions to be started on non-active objects and we'll just log a
warning when the transaction is finally committed like we do for all other
events on non-active objects.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2835 542714f4-19e9-0310-aa3c-eee0fc999fb1
space, it ends up considering up to 10,000 nodes with a max path length of
50 which causes the client to hang for like 5 seconds. Not so good. With a
max path length of 20, that comes down to about 1,300 nodes which ends up
being non-linearly faster.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2825 542714f4-19e9-0310-aa3c-eee0fc999fb1
client is disconnected, unsubscribe immediately. We normally unsubscribe
when the client loses its connection but it's possible for a subscription
request to come in and the client to lose connection before we can
communicate the object available response.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2824 542714f4-19e9-0310-aa3c-eee0fc999fb1
erroneously decide that we have stale subscriptions around, and log stale
subscriptions if we do end up clearing them.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2817 542714f4-19e9-0310-aa3c-eee0fc999fb1
pirate selection and the time we manage to load up their pirate.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2816 542714f4-19e9-0310-aa3c-eee0fc999fb1