Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.folklore.computers > #213882 > unrolled thread
| Started by | Dan Espen <dan1espen@gmail.com> |
|---|---|
| First post | 2020-09-07 19:51 -0400 |
| Last post | 2020-09-08 19:59 -0400 |
| Articles | 11 on this page of 171 — 28 participants |
Back to article view | Back to alt.folklore.computers
Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-07 19:51 -0400
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-07 21:03 -0400
Re: Keyboards again Quadibloc <jsavard@ecn.ab.ca> - 2020-09-07 18:16 -0700
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-07 21:50 -0400
Re: Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-07 22:12 -0400
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-07 23:51 -0400
Re: Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-12 17:40 -0400
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-12 18:04 -0400
Re: Keyboards again drb@ihatespam.msu.edu (Dennis Boone) - 2020-09-08 13:19 -0500
Re: Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-08 14:48 -0400
Re: Keyboards again Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-09-08 21:26 +0000
Re: Keyboards again Peter Flass <peter_flass@yahoo.com> - 2020-09-08 14:48 -0700
Re: Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-08 17:52 -0400
Re: Keyboards again Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-09 00:51 +0100
Re: Keyboards again scott@slp53.sl.home (Scott Lurndal) - 2020-09-09 17:42 +0000
Re: Keyboards again Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-09 19:50 +0100
Re: Keyboards again scott@slp53.sl.home (Scott Lurndal) - 2020-09-09 19:49 +0000
Re: Keyboards again Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-09 21:18 +0100
Re: Keyboards again scott@slp53.sl.home (Scott Lurndal) - 2020-09-10 15:44 +0000
Re: Keyboards again Freddy1X <freddy1X@indyX.netX> - 2020-09-08 21:59 -0400
Re: Keyboards again gareth evans <headstone255@yahoo.com> - 2020-09-09 11:10 +0100
Re: Keyboards again Quadibloc <jsavard@ecn.ab.ca> - 2020-09-09 15:27 -0700
Re: Keyboards again Andreas Kohlbach <ank@spamfence.net> - 2020-09-10 17:47 -0400
Re: Keyboards again Dave Garland <dave.garland@wizinfo.com> - 2020-09-11 01:26 -0500
Re: Keyboards again Thomas Koenig <tkoenig@netcologne.de> - 2020-09-12 06:20 +0000
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-12 12:27 +0000
Re: Keyboards again Bob Eager <news0073@eager.cx> - 2020-09-12 13:07 +0000
Re: Keyboards again Andreas Kohlbach <ank@spamfence.net> - 2020-09-12 20:15 -0400
Barcodes (Was: Keyboards again) Jan van den Broek <fortytwo@xs4all.nl> - 2020-10-03 21:57 +0100
Re: Barcodes (Was: Keyboards again) Ahem A Rivet's Shot <steveo@eircom.net> - 2020-10-03 22:11 +0100
Re: Barcodes (Was: Keyboards again) Bob Eager <news0073@eager.cx> - 2020-10-03 22:00 +0000
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-03 19:26 -0400
Re: Barcodes (Was: Keyboards again) Bob Eager <news0073@eager.cx> - 2020-10-04 09:02 +0000
Re: Barcodes (Was: Keyboards again) Ahem A Rivet's Shot <steveo@eircom.net> - 2020-10-04 12:22 +0100
Re: Barcodes (Was: Keyboards again) Bob Eager <news0073@eager.cx> - 2020-10-04 16:42 +0000
Re: Barcodes (Was: Keyboards again) mjb@signal11.invalid (Mike) - 2020-10-04 22:39 +0100
Re: Barcodes (Was: Keyboards again) Bob Eager <news0073@eager.cx> - 2020-10-04 22:06 +0000
Re: Barcodes (Was: Keyboards again) Andy Burns <usenet@andyburns.uk> - 2020-10-04 08:30 +0100
Re: Barcodes (Was: Keyboards again) the "Swampster" <fortytwo@xs4all.nl> - 2020-10-06 12:13 +0000
Re: Barcodes (Was: Keyboards again) mjb@signal11.invalid (Mike) - 2020-10-04 14:30 +0100
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-04 10:06 -0400
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-04 11:17 -0400
Re: Barcodes (Was: Keyboards again) mjb@signal11.invalid (Mike) - 2020-10-04 22:30 +0100
Re: Barcodes (Was: Keyboards again) John Levine <johnl@taugh.com> - 2020-10-04 19:13 +0000
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-04 19:07 -0400
Re: Barcodes (Was: Keyboards again) John Levine <johnl@taugh.com> - 2020-10-05 01:23 +0000
Re: Barcodes (Was: Keyboards again) Andy Burns <usenet@andyburns.uk> - 2020-10-05 09:54 +0100
Re: Barcodes (Was: Keyboards again) Peter Flass <peter_flass@yahoo.com> - 2020-10-05 05:34 -0700
Re: Barcodes (Was: Keyboards again) Andy Burns <usenet@andyburns.uk> - 2020-10-05 13:47 +0100
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-05 11:22 -0400
Re: Barcodes (Was: Keyboards again) Quadibloc <jsavard@ecn.ab.ca> - 2020-10-05 11:03 -0700
Re: Barcodes (Was: Keyboards again) Peter Flass <peter_flass@yahoo.com> - 2020-10-05 11:10 -0700
Re: Barcodes (Was: Keyboards again) Niklas Karlsson <anksil@yahoo.se> - 2020-10-05 18:27 +0000
Re: Barcodes (Was: Keyboards again) Ahem A Rivet's Shot <steveo@eircom.net> - 2020-10-05 20:03 +0100
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-05 18:20 -0400
Re: Barcodes Dan Espen <dan1espen@gmail.com> - 2020-10-05 19:05 -0400
Re: Barcodes J. Clarke <jclarke.873638@gmail.com> - 2020-10-05 23:57 -0400
Re: Barcodes scott@slp53.sl.home (Scott Lurndal) - 2020-10-06 15:30 +0000
Re: Barcodes (Was: Keyboards again) Peter Flass <peter_flass@yahoo.com> - 2020-10-05 16:52 -0700
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-05 23:54 -0400
Re: Barcodes (Was: Keyboards again) Quadibloc <jsavard@ecn.ab.ca> - 2020-10-05 21:53 -0700
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-06 07:33 -0400
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-05 11:21 -0400
Re: Barcodes (Was: Keyboards again) Dave Garland <dave.garland@wizinfo.com> - 2020-10-04 22:38 -0500
Re: Barcodes (Was: Keyboards again) Quadibloc <jsavard@ecn.ab.ca> - 2020-10-04 21:19 -0700
Re: Barcodes (Was: Keyboards again) Andy Leighton <andyl@azaal.plus.com> - 2020-10-05 03:04 -0500
Re: Barcodes (Was: Keyboards again) Ahem A Rivet's Shot <steveo@eircom.net> - 2020-10-05 11:01 +0100
Re: Barcodes (Was: Keyboards again) gareth evans <headstone255@yahoo.com> - 2020-10-05 12:50 +0100
Re: Barcodes (Was: Keyboards again) Peter Flass <peter_flass@yahoo.com> - 2020-10-05 05:34 -0700
Re: Barcodes (Was: Keyboards again) Dave Garland <dave.garland@wizinfo.com> - 2020-10-05 10:06 -0500
Re: Barcodes (Was: Keyboards again) maus <maus@dmaus.org> - 2020-10-06 21:16 +0000
Re: Barcodes (Was: Keyboards again) Ahem A Rivet's Shot <steveo@eircom.net> - 2020-10-07 06:38 +0100
Re: Barcodes (Was: Keyboards again) mjb@signal11.invalid (Mike) - 2020-10-05 12:36 +0100
Re: Barcodes (Was: Keyboards again) Andy Burns <usenet@andyburns.uk> - 2020-10-05 08:00 +0100
Re: Barcodes (Was: Keyboards again) mjb@signal11.invalid (Mike) - 2020-10-04 22:28 +0100
Re: Barcodes (Was: Keyboards again) J. Clarke <jclarke.873638@gmail.com> - 2020-10-04 19:06 -0400
Re: Barcodes (Was: Keyboards again) mjb@signal11.invalid (Mike) - 2020-10-05 12:33 +0100
Re: Barcodes (Was: Keyboards again) Andy Burns <usenet@andyburns.uk> - 2020-10-05 08:24 +0100
Re: Keyboards again Andreas Kohlbach <ank@spamfence.net> - 2020-09-12 20:02 -0400
Re: Keyboards again Thomas Koenig <tkoenig@netcologne.de> - 2020-09-13 07:05 +0000
Re: Keyboards again Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-13 09:24 +0100
Re: Keyboards again Bob Eager <news0073@eager.cx> - 2020-09-13 09:38 +0000
Re: Keyboards again Andreas Kohlbach <ank@spamfence.net> - 2020-09-13 19:20 -0400
Re: Keyboards again Bob Eager <news0073@eager.cx> - 2020-09-13 23:54 +0000
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-15 18:47 +0000
Re: Keyboards again Andreas Kohlbach <ank@spamfence.net> - 2020-09-15 18:35 -0400
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-15 18:44 +0000
Re: Keyboards again gareth evans <headstone255@yahoo.com> - 2020-09-15 20:29 +0100
Re: Keyboards again Bob Eager <news0073@eager.cx> - 2020-09-15 21:21 +0000
Re: Keyboards again Peter Flass <peter_flass@yahoo.com> - 2020-09-15 18:49 -0700
Re: Keyboards again Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-16 07:56 +0100
Re: Keyboards again gareth evans <headstone255@yahoo.com> - 2020-09-16 10:16 +0100
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-16 09:55 +0000
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-16 11:25 -0500
Re: Keyboards again Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-09-16 17:42 +0000
Re: Keyboards again Niklas Karlsson <anksil@yahoo.se> - 2020-09-16 18:03 +0000
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-16 13:57 -0500
Re: Keyboards again Niklas Karlsson <anksil@yahoo.se> - 2020-09-16 19:08 +0000
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-16 16:48 -0500
Re: Keyboards again Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-17 06:55 +0100
Re: Keyboards again usenet@only.tnx (Questor) - 2020-09-16 21:03 +0000
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-16 16:53 -0500
Re: Keyboards again Niklas Karlsson <anksil@yahoo.se> - 2020-09-16 21:55 +0000
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-17 07:20 +0000
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-17 10:06 -0500
Re: Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-17 11:15 -0400
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-17 12:37 -0500
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-17 20:07 +0000
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-18 10:01 -0500
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-18 16:45 +0000
Re: Keyboards again Peter Flass <peter_flass@yahoo.com> - 2020-09-18 11:22 -0700
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-17 19:59 +0000
Re: Keyboards again usenet@only.tnx (Questor) - 2020-09-19 23:25 +0000
Re: Keyboards again Chris <xxx.syseng.yyy@gfsys.co.uk> - 2020-09-20 12:03 +0100
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-20 14:27 +0000
Re: Keyboards again Chris <xxx.syseng.yyy@gfsys.co.uk> - 2020-09-20 16:08 +0100
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-20 10:52 -0500
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-20 14:57 -0400
Re: Keyboards again Niklas Karlsson <anksil@yahoo.se> - 2020-09-21 09:09 +0000
Re: Keyboards again Niklas Karlsson <anksil@yahoo.se> - 2020-09-21 09:07 +0000
Re: Keyboards again Chris <xxx.syseng.yyy@gfsys.co.uk> - 2020-09-21 14:32 +0100
Re: Keyboards again Niklas Karlsson <anksil@yahoo.se> - 2020-09-21 13:37 +0000
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-22 12:45 +0000
Re: Keyboards again Niklas Karlsson <anksil@yahoo.se> - 2020-09-22 12:49 +0000
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-22 12:37 +0000
Re: Keyboards again Bob Eager <news0073@eager.cx> - 2020-09-22 13:38 +0000
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-22 09:31 -0500
Re: Keyboards again Peter Flass <peter_flass@yahoo.com> - 2020-09-22 15:39 -0700
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-22 20:55 -0400
Re: Keyboards again Quadibloc <jsavard@ecn.ab.ca> - 2020-09-22 19:39 -0700
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-23 00:13 -0400
Re: Keyboards again maus <maus@dmaus.org> - 2020-09-23 10:52 +0000
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-20 14:48 -0400
Re: Keyboards again usenet@only.tnx (Questor) - 2020-09-21 19:35 +0000
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-22 09:22 -0500
Re: Keyboards again scott@slp53.sl.home (Scott Lurndal) - 2020-09-13 15:34 +0000
Re: Keyboards again Mike Spencer <mds@bogus.nodomain.nowhere> - 2020-09-13 17:54 -0300
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-13 10:53 -0500
Re: the dangers of socialism, not Keyboards again John Levine <johnl@taugh.com> - 2020-09-13 17:50 +0000
Re: the dangers of socialism, not Keyboards again Andy Burns <usenet@andyburns.uk> - 2020-09-13 19:35 +0100
Re: the dangers of socialism, not Keyboards again John Levine <johnl@taugh.com> - 2020-09-13 19:33 +0000
Re: the dangers of socialism, not Keyboards again Bob Martin <bob.martin@excite.com> - 2020-09-14 06:02 +0000
Re: the dangers of socialism, not Keyboards again Andy Burns <usenet@andyburns.uk> - 2020-09-14 07:46 +0100
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-13 15:01 -0500
Re: Keyboards again Andreas Kohlbach <ank@spamfence.net> - 2020-09-13 19:25 -0400
Re: Keyboards again Bob Eager <news0073@eager.cx> - 2020-09-13 09:37 +0000
Barcodes (Was: Keyboards again) Jan van den Broek <fortytwo@xs4all.nl> - 2020-10-03 22:00 +0100
Re: Barcodes (Was: Keyboards again) mjb@signal11.invalid (Mike) - 2020-10-04 14:38 +0100
Re: Barcodes (Was: Keyboards again) mjb@signal11.invalid (Mike) - 2020-10-04 22:36 +0100
Re: Keyboards again Andy Burns <usenet@andyburns.uk> - 2020-09-10 10:39 +0100
Re: Keyboards again Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-09-09 06:02 +0000
Re: Keyboards again Niklas Karlsson <anksil@yahoo.se> - 2020-09-09 14:14 +0000
Re: Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-09 10:18 -0400
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-09 14:49 -0500
Re: Keyboards again mjb@signal11.invalid (Mike) - 2020-09-09 20:36 +0100
Re: Keyboards again Andreas Kohlbach <ank@spamfence.net> - 2020-09-09 18:51 -0400
Re: Keyboards again Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-09-10 16:24 +0000
Re: Keyboards again JimP <chucktheouch@gmail.com> - 2020-09-10 14:58 -0500
Re: Keyboards again Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-10 17:12 +0100
Re: Keyboards again Andreas Kohlbach <ank@spamfence.net> - 2020-09-10 17:49 -0400
Re: Keyboards again Quadibloc <jsavard@ecn.ab.ca> - 2020-09-07 18:09 -0700
Re: Keyboards again Quadibloc <jsavard@ecn.ab.ca> - 2020-09-07 18:14 -0700
Re: Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-07 22:19 -0400
Re: Keyboards again Quadibloc <jsavard@ecn.ab.ca> - 2020-09-07 20:14 -0700
Re: Keyboards again Quadibloc <jsavard@ecn.ab.ca> - 2020-09-07 20:32 -0700
Re: Keyboards again Niklas Karlsson <anksil@yahoo.se> - 2020-09-08 09:44 +0000
Re: Keyboards again Andy Burns <usenet@andyburns.uk> - 2020-09-08 10:49 +0100
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-08 07:17 -0400
Re: Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-08 08:02 -0400
Re: Keyboards again J. Clarke <jclarke.873638@gmail.com> - 2020-09-08 18:33 -0400
Re: Keyboards again Dan Espen <dan1espen@gmail.com> - 2020-09-08 19:59 -0400
Page 9 of 9 — ← Prev page 1 2 3 4 5 6 7 8 [9]
| From | Quadibloc <jsavard@ecn.ab.ca> |
|---|---|
| Date | 2020-09-07 18:09 -0700 |
| Message-ID | <36c5bb2c-f895-4d04-af7e-e260d26fc611o@googlegroups.com> |
| In reply to | #213882 |
On Monday, September 7, 2020 at 5:51:52 PM UTC-6, Dan Espen wrote: > Recently I complained about a keyboard I was interested in but it had no > apparent scroll lock LED. > > So, I got the model wrong. > > The keyboard in question is the Logitech G513. Looked at the product page for it: https://www.logitechg.com/en-ca/products/gaming-keyboards/g513-backlit-mechanical-gaming-keyboard.html There are indeed only *two* lights in the part of the keyboard where you would see Num Lock, Caps Lock, and Scroll Lock on a normal IBM keyboard. The light on the *left* has an A with a circle around it under it, so I guess that's the Caps Lock key. The second light has a G with a circle around it beneath. So I have to conclude that it probably _isn't_ the Num Lock light, and this keyboard doesn't have one of them *either*. Instead, presumably it indicates if the keyboard is in "gaming mode" or some such thing. John Savard
[toc] | [prev] | [next] | [standalone]
| From | Quadibloc <jsavard@ecn.ab.ca> |
|---|---|
| Date | 2020-09-07 18:14 -0700 |
| Message-ID | <16ed04b0-fe20-4e9a-8552-f2afdc1e5d03o@googlegroups.com> |
| In reply to | #213885 |
On Monday, September 7, 2020 at 7:09:19 PM UTC-6, Quadibloc wrote: > On Monday, September 7, 2020 at 5:51:52 PM UTC-6, Dan Espen wrote: > > Recently I complained about a keyboard I was interested in but it had no > > apparent scroll lock LED. > > > > So, I got the model wrong. > > > > The keyboard in question is the Logitech G513. > > Looked at the product page for it: > > https://www.logitechg.com/en-ca/products/gaming-keyboards/g513-backlit-mechanical-gaming-keyboard.html > > There are indeed only *two* lights in the part of the keyboard where you would > see Num Lock, Caps Lock, and Scroll Lock on a normal IBM keyboard. > > The light on the *left* has an A with a circle around it under it, so I guess > that's the Caps Lock key. > > The second light has a G with a circle around it beneath. So I have to conclude > that it probably _isn't_ the Num Lock light, and this keyboard doesn't have one > of them *either*. Instead, presumably it indicates if the keyboard is in "gaming > mode" or some such thing. Yes, FN+F8 puts the keyboard in Game Mode. By default, that disables the window key, but it is configurable to have other effects. John Savard
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2020-09-07 22:19 -0400 |
| Message-ID | <rj6pnu$ohu$2@dont-email.me> |
| In reply to | #213885 |
Quadibloc <jsavard@ecn.ab.ca> writes: > On Monday, September 7, 2020 at 5:51:52 PM UTC-6, Dan Espen wrote: >> Recently I complained about a keyboard I was interested in but it had no >> apparent scroll lock LED. >> >> So, I got the model wrong. >> >> The keyboard in question is the Logitech G513. > > Looked at the product page for it: > > https://www.logitechg.com/en-ca/products/gaming-keyboards/g513-backlit-mechanical-gaming-keyboard.html > > There are indeed only *two* lights in the part of the keyboard where you would > see Num Lock, Caps Lock, and Scroll Lock on a normal IBM keyboard. > > The light on the *left* has an A with a circle around it under it, so I guess > that's the Caps Lock key. > > The second light has a G with a circle around it beneath. So I have to conclude > that it probably _isn't_ the Num Lock light, and this keyboard doesn't have one > of them *either*. Instead, presumably it indicates if the keyboard is in "gaming > mode" or some such thing. Yes, somewhere in my searching, maybe the comments I read that G is Game Mode. On the "A" I'm mystified. I did have the thought about an upper case A indicating cAps lock, but it seemed unlikely. How you work with a keyboard with no numlock/capslock is a mystery to me. I looked at all this stuff this spring. I keep going back hoping that they'll replace the model I really wanted (815) with something similar, but no luck so far. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Quadibloc <jsavard@ecn.ab.ca> |
|---|---|
| Date | 2020-09-07 20:14 -0700 |
| Message-ID | <dbad24b2-f7c9-45a0-9d7c-dccd3ea520afo@googlegroups.com> |
| In reply to | #213891 |
On Monday, September 7, 2020 at 8:19:44 PM UTC-6, Dan Espen wrote: > On the "A" I'm mystified. I did have the thought about an upper case A > indicating cAps lock, but it seemed unlikely. Since many keyboards use "Aa" to indicate caps lock, that was the first possibility that suggested itself to me. Unfortunately, I can't really find much documentation for the keyboard. John Savard
[toc] | [prev] | [next] | [standalone]
| From | Quadibloc <jsavard@ecn.ab.ca> |
|---|---|
| Date | 2020-09-07 20:32 -0700 |
| Message-ID | <13fddccc-6837-4c29-aa1f-5b7c7f89d9abo@googlegroups.com> |
| In reply to | #213896 |
On Monday, September 7, 2020 at 9:14:29 PM UTC-6, Quadibloc wrote: > On Monday, September 7, 2020 at 8:19:44 PM UTC-6, Dan Espen wrote: > > > On the "A" I'm mystified. I did have the thought about an upper case A > > indicating cAps lock, but it seemed unlikely. > > Since many keyboards use "Aa" to indicate caps lock, that was the first > possibility that suggested itself to me. Unfortunately, I can't really find much > documentation for the keyboard. So I found a video review of the keyboard: https://www.youtube.com/watch?v=vso_cDLYKrM but it didn't answer the question. However, I saw a glimpse of Logitech's game control software that goes with the keyboard, and the letter A was next to 'text block', so I wouldn't be surprised if the A light was configurable. Maybe you can see if you're in num lock and scroll lock on your screen. John Savard
[toc] | [prev] | [next] | [standalone]
| From | Niklas Karlsson <anksil@yahoo.se> |
|---|---|
| Date | 2020-09-08 09:44 +0000 |
| Message-ID | <hrp23bFkvgcU1@mid.individual.net> |
| In reply to | #213891 |
On 2020-09-08, Dan Espen <dan1espen@gmail.com> wrote: > > On the "A" I'm mystified. I did have the thought about an upper case A > indicating cAps lock, but it seemed unlikely. FWIW, my bare-bones Deltaco keyboard indicates Caps Lock with an upper case A in a square with rounded corners. Doesn't mean that's the case with the model you found, but it's a data point at least. Niklas -- New, from IKEA: DARCKENSE, the chair. Available in white only. All-natural materials!
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2020-09-08 10:49 +0100 |
| Message-ID | <hrp2dtFl27aU1@mid.individual.net> |
| In reply to | #213885 |
Quadibloc wrote: > The light on the *left* has an A with a circle around it under it, so I guess > that's the Caps Lock key. > > The second light has a G with a circle around it beneath. So I have to conclude > that it probably _isn't_ the Num Lock light, and this keyboard doesn't have one > of them *either*. Wonder whether you could program the scroll-lock and num-lock keys to change their illumination colour if the corresponding lock is 'on'?
[toc] | [prev] | [next] | [standalone]
| From | J. Clarke <jclarke.873638@gmail.com> |
|---|---|
| Date | 2020-09-08 07:17 -0400 |
| Message-ID | <obpelfp42udgjbts8n2idml6a3spdkmt7g@4ax.com> |
| In reply to | #213900 |
On Tue, 8 Sep 2020 10:49:47 +0100, Andy Burns <usenet@andyburns.uk> wrote: >Quadibloc wrote: > >> The light on the *left* has an A with a circle around it under it, so I guess >> that's the Caps Lock key. >> >> The second light has a G with a circle around it beneath. So I have to conclude >> that it probably _isn't_ the Num Lock light, and this keyboard doesn't have one >> of them *either*. > >Wonder whether you could program the scroll-lock and num-lock keys to >change their illumination colour if the corresponding lock is 'on'? I'm wondering the same thing. I'm also wondering if it happens automatically, which is why I need to hook mine up and check.
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2020-09-08 08:02 -0400 |
| Message-ID | <rj7rta$259$1@dont-email.me> |
| In reply to | #213900 |
Andy Burns <usenet@andyburns.uk> writes:
> Quadibloc wrote:
>
>> The light on the *left* has an A with a circle around it under it, so I guess
>> that's the Caps Lock key.
>> The second light has a G with a circle around it beneath. So I have
>> to conclude
>> that it probably _isn't_ the Num Lock light, and this keyboard doesn't have one
>> of them *either*.
>
> Wonder whether you could program the scroll-lock and num-lock keys to
> change their illumination colour if the corresponding lock is 'on'?
I could. I'm just trying to keep my software as generic as possible.
The software I do this with has hard coded:
os.system('xset -led named "Scroll Lock"')
and
os.system('xset led named "Scroll Lock"')
So, I could just change the hard coding.
The software would be useful for anyone though and I have half
a desire to put it on github for general use. So, I'd want
to make the toggle commands customizable.
So, yes I could use the RGB to toggle the color of any of the LEDs,
it's just going to be a bit ugly.
This is part of a tool I wrote that
monitors an IMAP mailbox.
Any unread mail, the scroll lock light goes on, a desktop icon changes
color and the count of unread mails is shown. Each new mail is
optionally run through spamassassin and deleted if spam. Each new
mail is matched to a pattern for the From/To/Subject lines and
a unique sound is played appropriately.
--
Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | J. Clarke <jclarke.873638@gmail.com> |
|---|---|
| Date | 2020-09-08 18:33 -0400 |
| Message-ID | <671glflgdfsgatj75eibirlra4daucbg82@4ax.com> |
| In reply to | #213906 |
On Tue, 08 Sep 2020 08:02:50 -0400, Dan Espen <dan1espen@gmail.com>
wrote:
>Andy Burns <usenet@andyburns.uk> writes:
>
>> Quadibloc wrote:
>>
>>> The light on the *left* has an A with a circle around it under it, so I guess
>>> that's the Caps Lock key.
>>> The second light has a G with a circle around it beneath. So I have
>>> to conclude
>>> that it probably _isn't_ the Num Lock light, and this keyboard doesn't have one
>>> of them *either*.
>>
>> Wonder whether you could program the scroll-lock and num-lock keys to
>> change their illumination colour if the corresponding lock is 'on'?
>
>I could. I'm just trying to keep my software as generic as possible.
>
>
>The software I do this with has hard coded:
>
> os.system('xset -led named "Scroll Lock"')
>and
> os.system('xset led named "Scroll Lock"')
>
>So, I could just change the hard coding.
>The software would be useful for anyone though and I have half
>a desire to put it on github for general use. So, I'd want
>to make the toggle commands customizable.
>
>So, yes I could use the RGB to toggle the color of any of the LEDs,
>it's just going to be a bit ugly.
>
>This is part of a tool I wrote that
>monitors an IMAP mailbox.
>
>Any unread mail, the scroll lock light goes on, a desktop icon changes
>color and the count of unread mails is shown. Each new mail is
>optionally run through spamassassin and deleted if spam. Each new
>mail is matched to a pattern for the From/To/Subject lines and
>a unique sound is played appropriately.
I'm not finding any straightforward way to get a functioning
scroll-lock indicator on the 915. I think that it might be possible
by assigning a couple of layouts, one with the scroll-lock key one
color and another with it a different one (damn this is a nice
keyboard though--much nicer than the 910, at least I'm not hitting as
many typos--but it oughta be for the price) and then putting a macro
on scroll-lock that changes the layout in addition to sending the
scroll-lock. But I don't know if that will work if scroll-lock is set
externally to the keyboard.
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2020-09-08 19:59 -0400 |
| Message-ID | <rj95sj$jqk$1@dont-email.me> |
| In reply to | #213986 |
J. Clarke <jclarke.873638@gmail.com> writes:
> On Tue, 08 Sep 2020 08:02:50 -0400, Dan Espen <dan1espen@gmail.com>
> wrote:
>
>>Andy Burns <usenet@andyburns.uk> writes:
>>
>>> Quadibloc wrote:
>>>
>>>> The light on the *left* has an A with a circle around it under it, so I guess
>>>> that's the Caps Lock key.
>>>> The second light has a G with a circle around it beneath. So I have
>>>> to conclude
>>>> that it probably _isn't_ the Num Lock light, and this keyboard doesn't have one
>>>> of them *either*.
>>>
>>> Wonder whether you could program the scroll-lock and num-lock keys to
>>> change their illumination colour if the corresponding lock is 'on'?
>>
>>I could. I'm just trying to keep my software as generic as possible.
>>
>>
>>The software I do this with has hard coded:
>>
>> os.system('xset -led named "Scroll Lock"')
>>and
>> os.system('xset led named "Scroll Lock"')
>>
>>So, I could just change the hard coding.
>>The software would be useful for anyone though and I have half
>>a desire to put it on github for general use. So, I'd want
>>to make the toggle commands customizable.
>>
>>So, yes I could use the RGB to toggle the color of any of the LEDs,
>>it's just going to be a bit ugly.
>>
>>This is part of a tool I wrote that
>>monitors an IMAP mailbox.
>>
>>Any unread mail, the scroll lock light goes on, a desktop icon changes
>>color and the count of unread mails is shown. Each new mail is
>>optionally run through spamassassin and deleted if spam. Each new
>>mail is matched to a pattern for the From/To/Subject lines and
>>a unique sound is played appropriately.
>
> I'm not finding any straightforward way to get a functioning
> scroll-lock indicator on the 915. I think that it might be possible
> by assigning a couple of layouts, one with the scroll-lock key one
> color and another with it a different one (damn this is a nice
> keyboard though--much nicer than the 910, at least I'm not hitting as
> many typos--but it oughta be for the price) and then putting a macro
> on scroll-lock that changes the layout in addition to sending the
> scroll-lock. But I don't know if that will work if scroll-lock is set
> externally to the keyboard.
Thanks for looking.
Does it have working num-lock and I'm guessing that A light is
caps-lock?
To turn on/off scroll lock I use the commands
xset -led named "Scroll Lock"
xset led named "Scroll Lock"
I don't know if Windows has an equivalent.
But since the keyboard lets me mess with each individual light,
I'll just set up a command to make scroll lock brighter/dimmer or maybe mess
with the light behind the G if that's supported.
I don't ever hit the scroll lock key, I'm just using it as an indicator.
Long ago when I first worked this out I found that turning on the caps
lock or num lock LED actually activated the function too. Turning on
scroll lock didn't do anything I could notice.
Actually, I do sometimes hit the scroll lock key, when I want to invoke
the screen locker. But that doesn't do anything to the light.
I liked the look of the G815 better. I think it should be pretty nice too.
Looks like it'll take a week or so to get here.
--
Dan Espen
[toc] | [prev] | [standalone]
Page 9 of 9 — ← Prev page 1 2 3 4 5 6 7 8 [9]
Back to top | Article view | alt.folklore.computers
csiph-web