00:00:00 --- log: started forth/08.03.03 00:22:17 --- quit: nighty^ ("Disappears in a puff of smoke") 03:02:21 --- quit: sauvin (Remote closed the connection) 05:15:40 --- join: nighty^ (n=nighty@p9154-adsau17honb13-acca.tokyo.ocn.ne.jp) joined #forth 05:59:21 --- quit: ecraven ("bbl") 08:54:44 --- join: JasonWoof (n=JasonWoo@unaffiliated/herkamire) joined #forth 08:54:44 --- mode: ChanServ set +o JasonWoof 09:06:19 --- join: Quartus__ (n=Quartus~@205.205.178.4) joined #forth 09:26:09 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 09:47:51 --- quit: Al2O3 () 09:50:46 --- quit: ccfg (brown.freenode.net irc.freenode.net) 09:50:46 --- quit: rbarraud (brown.freenode.net irc.freenode.net) 09:50:46 --- quit: warpzero (brown.freenode.net irc.freenode.net) 09:51:20 --- join: warpzero (n=warpzero@208.74.136.138) joined #forth 09:51:20 --- join: ccfg (n=pitkajus@tuomi.oulu.fi) joined #forth 09:51:20 --- join: rbarraud (n=rbarraud@gateway.quickcircuit.co.nz) joined #forth 10:27:47 --- join: Quartus__ (n=Quartus~@205.205.178.4) joined #forth 10:47:49 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 10:53:39 --- quit: JasonWoof ("Leaving.") 11:13:23 --- join: ygrek (i=user@gateway/tor/x-b3ba083eacc85453) joined #forth 11:13:32 --- join: Quartus__ (n=Quartus~@205.205.178.4) joined #forth 11:33:27 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 11:39:29 --- join: neceve (n=ncv@unaffiliated/neceve) joined #forth 12:08:40 --- quit: neceve (Read error: 104 (Connection reset by peer)) 13:49:35 --- quit: nighty^ (Remote closed the connection) 14:06:01 --- join: snoopy_1711 (i=snoopy_1@dslb-084-059-110-220.pools.arcor-ip.net) joined #forth 14:11:13 --- quit: ygrek (Remote closed the connection) 14:14:19 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 14:14:43 --- nick: snoopy_1711 -> Snoopy42 14:52:33 --- join: Quartus__ (n=Quartus~@205.205.178.5) joined #forth 15:09:22 --- join: crest__ (n=crest@p5B1079FC.dip.t-dialin.net) joined #forth 15:16:20 --- quit: crest_ (Read error: 101 (Network is unreachable)) 15:33:09 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 16:11:09 --- join: adu (n=andrew@pool-71-178-230-157.washdc.fios.verizon.net) joined #forth 16:19:35 --- quit: adu () 17:31:55 --- join: nighty^ (n=nighty@210.188.173.246) joined #forth 18:28:06 Quartus, I actually had a chance to mess around a bit with your Forth under Garnet VM. It works! There are a few annoying bits, like that I can't use the enter key on my keyboard to execute a line - I have to perform the Graffiti stroke - but I haven't gotten it to crash yet. 18:28:11 Haven't tried very hard, mind. 18:28:24 aspect, ping? 18:40:39 --- join: adu_1 (n=andrew@pool-71-178-230-157.washdc.fios.verizon.net) joined #forth 18:41:23 --- nick: adu_1 -> adu 19:00:52 --- join: adu_1 (n=andrew@pool-71-178-230-157.washdc.fios.verizon.net) joined #forth 19:16:24 --- quit: adu (Connection timed out) 19:23:57 --- join: andydude (n=andrew@pool-71-178-230-157.washdc.fios.verizon.net) joined #forth 19:24:50 --- join: andydude_ (n=andrew@pool-71-178-230-157.washdc.fios.verizon.net) joined #forth 19:26:11 --- quit: andydude_ (Client Quit) 19:39:20 --- quit: adu_1 (Read error: 110 (Connection timed out)) 19:40:43 --- quit: andydude (Read error: 110 (Connection timed out)) 19:53:23 --- join: snoopy_1711 (i=snoopy_1@dslb-084-059-124-246.pools.arcor-ip.net) joined #forth 19:56:38 gnomon, interesting. Thanks for the feedback! 19:56:50 I wonder what event the enter key generates. 19:57:14 I can probably tune for it. What version of Quartus Forth are you runnign? 19:57:53 The 2.0.1 evaluation version. 19:58:04 Ok. 19:58:10 How would I go about determining what code the keypress generates? 19:58:16 key . 19:58:29 (facepalm) 19:58:39 One mo'. 20:00:35 Right, let's see what this crazy thing thinks. 20:00:54 I'll bet it's 13. 20:00:56 46, apparently. 20:00:58 whoa. 20:01:01 That's odd. 20:01:02 Whiskey tango foxtrot? 20:01:26 That's ascii for . 20:01:28 are you sure? 20:01:40 Positive. 20:01:43 Just double-checked. 20:01:50 Run a loop....... : foo begin key . again ; foo 20:01:56 hit enter a few times 20:02:10 I've also discovered that the Enter key doesn't break lines in memopad, for what it's worth; it's possible that there's some strange interaction with the host keyboard subsystem here. 20:02:58 !? 20:03:05 It doesn't seem to register the Enter key at all. 20:03:37 ok. Now try it with ekey. 20:04:11 0 20:04:24 you'll get a 0 at intervals from ekey. Try other keys too. 20:04:38 They should generate a 4. 20:04:46 Yup. 20:05:00 Ok. So possibly the host enter key generates nothing the garnet vm sees. 20:05:06 Shift-enter, maybe? 20:05:14 OK, Enter is indeed generating a 4 in that case. So it's passing *something* through to the guest OS. 20:05:21 oh. Ok, so not 0. 4. 20:05:41 Right, sorry - when I used ekey in the loop, it was generating a 4. 20:05:49 That's a good sign. 20:05:52 I should have been more specific there. Apologies. 20:06:51 So now : foo begin ekey ekey>char if . then again ; foo 20:07:02 no, hang on, sorry 20:07:10 So now : foo begin ekey ekey>char if . else drop then again ; foo 20:07:52 a should give 97, for instance 20:07:57 enter may give nothing with this loop 20:08:38 a, space and other keys generate the expected output; enter generates nothing. 20:08:48 ok. So it's generating a keydown event, probably with some special flags. 20:09:37 I'm checking around to see if anyone else has been running into issues with the enter key on a Bluetooth keyboard. 20:10:08 I'll want a dump of the event buffer after an enter keypress; I'll have to draw you up a bit of code, if it isn't obvious to you how to do that. 20:10:48 It really isn't, I'm afraid. 20:10:59 Not to worry. It's not as bad as it sounds. 20:11:14 I really appreciate your help with this, by the way. 20:11:44 --- quit: Snoopy42 (Read error: 110 (Connection timed out)) 20:11:47 No problem. 20:11:51 --- nick: snoopy_1711 -> Snoopy42 20:12:55 gnomon, do you do any Forth, or are you coming at it cold? 20:14:40 I have some passing familiarity with it. A couple of harebrained implementations, not a lot of working application code. 20:14:47 Typical wannabe level, I suppose. 20:15:09 Ok. What you want here is a loop that runs ekey until it gets a 4; if it gets a 4, it does a CR and then displays, in hex, the 24 bytes starting at the address that the word 'event' returns. 20:15:27 Write that, run that, tell me what 24 bytes the enter key gives you. 20:16:27 so ....... begin ekey 4 = if ..... then again with the 24-byte display code called from inside the if/then 20:18:07 Whoo, crashy. 20:18:24 That's all in a : foo ... ; setup 20:18:34 Wait, whoops. I'm a toolbag. I was trying to read from the address at which the word event was stored. 20:18:43 Right, yeah. 20:18:50 er, hmm. Event returns an address on the stack. 20:18:57 Yeah. 20:19:03 Soy estupido. 20:22:27 --- join: adu_1 (n=andrew@pool-71-178-230-157.washdc.fios.verizon.net) joined #forth 20:22:35 --- quit: adu_1 (Client Quit) 20:25:43 time's up, pencils down. :) 20:27:16 --- join: adu (n=andrew@pool-71-178-230-157.washdc.fios.verizon.net) joined #forth 20:31:07 Heh. 20:31:10 Almost there. 20:31:49 Blarg. 20:32:27 c@a seems to crash Garnet. 20:32:50 shouldn't. One wonders what you're using it for. 24 0 do event i + c@ . loop 20:33:07 I was using a for loop to read 'em backwards. 20:33:12 good heavens. 20:33:26 I need them forwards, please. event does not return a 32-bit address. 20:33:39 Ah, that's good to know. 20:33:53 (I'm reading through your manual as I work on this; it's really very well done) 20:34:02 Thanks! 20:37:12 Wait, what? Can I not have an if inside a begin / again loop? 20:37:18 sure you can. 20:38:08 : foo begin ekey 4 = if cr dump-event then again ; 20:38:11 There we go. 20:38:16 Yeah, it's OK, I got it. 20:40:46 In hex: 00 04 00 01 00 22 00 D2 01 36 00 00 00 08 00 D2 00 00 00 00 00 00 00 00 20:41:29 Thanks. I should be able to decipher that and enhance ACCEPT to read that as an enter key. 20:41:46 That, sir, is some of the best news I've heard in a good long while. 20:41:55 I am indebted for your patience and consideration. 20:42:03 It produces that reliably, even when you press other keys in between? 20:42:13 Let me verify. 20:43:25 --- join: adu_ (n=andrew@pool-71-178-230-157.washdc.fios.verizon.net) joined #forth 20:44:24 No, it is not reliable. 20:44:31 which parts change? 20:44:48 Hang on, let me enhance the output a little to more easily answer that. 20:44:50 and are you just testing with the keyboard, or with graffiti? 20:45:10 I'm only using Graffiti to create the first Enter keystroke. Everything else is pure keyboard. 20:45:24 you mean to start the thing running. 20:45:53 --- quit: adu (Nick collision from services.) 20:46:11 --- nick: adu_ -> adu 20:46:43 Yessir. 20:46:47 Hm, interesting. 20:47:08 Now it's being consistent but returning different values from the first ones that I reported. 20:47:18 I'm prepared to discard the original numbers as errors on my part. 20:47:23 ok. 20:47:23 This at least is repeatable. 20:47:32 Your dump-event, resembles mine in some way? 20:47:41 Yessir. 20:47:52 you're not using @ or jumping forward by 2, or going backward or anything? 20:48:07 04 0 1 0 34 0 198 1 54 0 0 0 8 0 198 0 0 0 0 0 0 0 0 20:48:13 I am not. 20:48:16 That's not hex. 20:48:22 No, 'tisn't. 20:48:35 I'm using "." for output. 20:48:48 which will output hex if you type 'hex' first 20:49:16 ...I've mentioned that I'm a tool, right? 20:49:20 Couple times. 20:49:27 Yeah, I thought I might have. 20:50:43 OK, consistency in hex achieved. 20:51:10 0 4 0 1 0 2E 0 CC 1 36 0 0 0 8 0 CC 0 0 0 0 0 0 0 0 20:51:17 Good--thanks. 20:51:52 hang on. 2E? Where it was 34 in decimal? 20:52:45 Possibly nothing to worry about. I'll dig into this tomorrow. 20:53:20 That's a great idea right there. 20:53:33 Digging into things tomorrow, I mean. I'm just about dead on my feet. 20:53:36 Well, butt. Same deal. 20:53:48 Thanks for the info; I'll work up a trial build. 20:53:57 Thanks again for all your help. I'll check in again tomorrow if and when I can. 20:54:00 Ok! 20:54:09 --- join: adu_ (n=andrew@pool-71-178-230-157.washdc.fios.verizon.net) joined #forth 20:55:53 --- quit: adu_ (Remote closed the connection) 20:57:29 --- quit: adu (Nick collision from services.) 21:49:36 --- join: Quartus__ (n=Quartus~@205.205.50.1) joined #forth 22:12:43 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 22:47:03 --- join: sauvin (n=sauvin@c-98-213-78-251.hsd1.il.comcast.net) joined #forth 23:46:58 --- quit: Quartus (Read error: 110 (Connection timed out)) 23:59:59 --- log: ended forth/08.03.03