Stonesoup Keyboard issues

On Jan 11, 9:53 am, Rachel Elizabeth Dillon <rac....RemoveThis@akrasiac.org>
wrote:
> On 2008-01-11, andrew.air....RemoveThis@gmail.com <andrew.air....RemoveThis@gmail.com> wrote:
>
> > I've posted on here before but haven't got much of a response. It
> > seems that when I try to define macros in crawl, my keyboard gives off
> > some strange signals. The weirdest thing about it, is that it seemed
> > to work fine up until the 0.3* versions of Crawl started to come out.
> > I figured out that the F-Lock key will fix some of the problems, but I
> > can't seem to get Crawl to recognize when I hit any of the function
> > keys.
>
> > Can anyone help me out?
>
> I can't promise I can help you out, but if you can be more specific,
> I can give it a shot... What OS, what build, and what signals are you
> getting versus expecting?
>
> (for my part I've noticed occasional weirdness with iTerm, but I blame
> iTerm, not crawl...)
>
> -r.

I'm using Vista with StoneSoup .32 (at least I think that's what I was
using). Whenever I hit F1 I get something like this:
/{0};
Ctrl-F1 results in:
/{0}^

I though that the signal would be something like this:
/{###}
Where ### was some number.

Also, after saving the macro file and re-reading it, the macros
strangely are degenerated.
 >> Stay informed about: Stonesoup Keyboard issues 

On Jan 12, 9:35 am, Darshan Shaligram <scinti....DeleteThis@gmail.com> wrote:
> andrew.air....DeleteThis@gmail.com writes:
>
> [macro issues]
>
> > I'm using Vista with StoneSoup .32 (at least I think that's what I was
> > using). Whenever I hit F1 I get something like this:
> > /{0};
> > Ctrl-F1 results in:
> > /{0}^
> > I though that the signal would be something like this:
> > /{###}
> > Where ### was some number.
>
> This seems to be behaviour unique to Vista, or at least I don't see it
> on XP (as Martin notes, this is disconcertingly DOS-like behaviour).
> However, this in itself is not a problem.
>
> > Also, after saving the macro file and re-reading it, the macros
> > strangely are degenerated.
>
> There is a bug in Crawl's handling of null bytes (the \{0} you saw)
> when loading macros, this should be fixed in 0.3.4.
>
> Thanks for the bug report.
> --
> Darshan Shaligram <scinti....DeleteThis@gmail.com> Deus vult

Yeah! Thanks. I haven't been able to really play the game since it
went to the .3 series. Thanks a bunch!
 >> Stay informed about: Stonesoup Keyboard issues 

andrew.airmet.TakeThisOut@gmail.com wrote:
>On Jan 11, 9:53 am, Rachel Elizabeth Dillon <rac....TakeThisOut@akrasiac.org>
>wrote:
>> I can't promise I can help you out, but if you can be more specific,
>> I can give it a shot... What OS, what build, and what signals are you
>> getting versus expecting?
>
>I'm using Vista with StoneSoup .32 (at least I think that's what I was
>using). Whenever I hit F1 I get something like this:
>/{0};
>Ctrl-F1 results in:
>/{0}^

That looks like an ordinary Microsoft function key console character
sequence - ASCII NUL followed by another character. Function keys in
Microsoft consoles have emitted that kind of sequence since, um, MS-DOS.
--
\_\/_/ some girls wander by mistake into the mess that scalpels make
\ / are you the teachers of my heart? we teach old hearts to break
\/ --- Leonard Cohen, "Teachers"
 >> Stay informed about: Stonesoup Keyboard issues 

andrew.airmet.TakeThisOut@gmail.com writes:
[macro issues]
> I'm using Vista with StoneSoup .32 (at least I think that's what I was
> using). Whenever I hit F1 I get something like this:
> /{0};
> Ctrl-F1 results in:
> /{0}^

> I though that the signal would be something like this:
> /{###}
> Where ### was some number.

This seems to be behaviour unique to Vista, or at least I don't see it
on XP (as Martin notes, this is disconcertingly DOS-like behaviour).
However, this in itself is not a problem.

> Also, after saving the macro file and re-reading it, the macros
> strangely are degenerated.

There is a bug in Crawl's handling of null bytes (the \{0} you saw)
when loading macros, this should be fixed in 0.3.4.

Thanks for the bug report.
--
Darshan Shaligram <scintilla.TakeThisOut@gmail.com> Deus vult
 >> Stay informed about: Stonesoup Keyboard issues