* http://ivanw.club.fr/AG/front_carl_diff.gif
* http://ivanw.club.fr/AG/back_carl.gif
...please tell me if there is something wrong with these images, they
are on-line and can be corrected easlily
- Ivan
* http://ivanw.club.fr/AG/AG5.ahk.html
I am currently not changing anything, just trying to make it more
simple to read and understand.
BTW, Carl, feel free to tell me if this is ok for you that we play with
your work here.
- Ivan
Was there a reason for changing the ordering of the numbers? I put
those back; numbers and F keys. I also found Enter, Space and
Backspace to be used far too frequently to require a shift; I created a
double-key function for them. I swapped the CTRL and ALT on the right
side, so that CTRL is always to the outside and ALT to the inside.
Finally, I swapped the blue and red function keys; I use blue far more
than red and the blue was easier to reach, at least for my hand size.
Here is my key layout and .ahk file:
http://wsucougs.org/tumbleson.jpg
http://wsucougs.org/tumblesonthumb.jpg
http://wsucougs.org/AG-5_TMBLSN.ahk
Home and End are double-key combinations, also, F-U and D-L,
respectively; this was a little difficult to draw on my diagram.
It still works fine!!!
o Added tunable parameter entries near the top of the script for easy
editing:
- A tunable TRA Icon parameter
- A tunable boost-factor parameter for the mouse (may disable boost)
o Added a TRAY Icon entry when the script executes
o Augmented Carl's DESIGN NOTES to explain how things are organized
o Renamed variables to make sense for a passing-by reader
o Added a Welcome+Usage and an Exit message box
- PrintScreen is still there to Suspend
- Added ScrollLock to stop
o Columnized the code for readability
And I did not change Carl's mapping so far! Now that I can understand
what's in there, I can say that Carl did a great job! This is still a
work in progress. An updated and illustrated on line html of the script
is here: http://ivanw.club.fr/AG/AG5.ahk.html
...
1. How do I assign r-h and g-m chords? I have added:
Ch1 := "r"
Ch2 := "h"
Key2B%Ch1%_%Ch2% := 38
Key2B%Ch2%_%Ch1% := 38
I also need to add something under 'hotkeys for dual press keys', but
what?
2. Can someone please explain the reasoning for changing the order of
the numbers? I really like this layout, for the most part, but without
a really good reason, why re-arrange these numbers?
*g::AG_HK2downa("g","m","","")
*g up::AG_HK2upa("g","m","","")
*r::AG_HK2downa("r","h","","")
*r up::AG_HK2upa("r","h","","")
*m::AG_HK2downa("m","g","","")
*m up::AG_HK2upa("m","g","","")
*h::AG_HK2downa("h","r","","")
*h up::AG_HK2upa("h","r","","")
Here's my current setup:
Your layout with extensive chording is certainly worth exploring,
Beware of the learning curve though. You will know whether you have
made a good design only after several weeks of training and practice
with a steady layout.
I have to note that I DON'T have my AG-5 yet, so all what I'm
saying here is only reasoning based on related experience...
We can look at chording with the AG as those uncomfortable reaches we
have with a standard keyboard layout. The less we have of those, the
better.
If given the choice, I would prefer mode switching with the thumb at
driving the game. The color-shift press is chording too but when other
fingers are involved, it seems they are not doing their natural job.
I am not saying that it is just bad, only that it should be considered
a second choice solution, reserved for extra-bonus, those you can
survive if you don't have them. I noticed that most of your chording
are alternatives to color-shifted keystrokes. So when is it you can
benefit from chording rather than shifting? What is the idea?
--
Hey Mike you'd better manage something with this guy if you want to
keep diving ;o). Anyway, it seems that you can get addicted in a very
short time. Maybe you've just invented some sort of virus that may
spread like hell soon, who knows?
Anyway, the reason for the extensive chording is the ability to type
something (like this entire post) without ever having to shift. The
thumb buttons are too 'recessed' for my comfort. When I stretch my
thumb up to a shift button, I pull my digits off of their 'home'
positions. The REAL solution to this is to put three buttons under
each finger. In fact, I think that FIVE 3-position buttons are what is
really needed. The index finger would have two of these (6 buttons
total) and the other digits a single 3-position button. This would
allow STRICT qwerty correlation.
I also don't think the the 'thumb' area should be recessed, it should
stay on the same plane as the LEDs. Maybe my hands (or just my thumbs)
are too short. I posted on that elsewhere in this group. My hand is 7
3/4" from wrist (I measured this from the 2nd crease, not the one that
curves up toward the palm) to end of my middle finger and I can't
figure out a good way to measure my thumb.
If the thumb buttons were positioned more naturally (for me), then I
probably wouldn't be so interested in chording.
The only characters that I had to shift in this post were numbers,
quotes and the apostrophe. However, I still have two chords open,
guess what I'm going to put there...
Yes! The idea of STRICT qwerty correlation is really attractive.
Even without having experienced the current layout, it makes much sense
to have a standard keyboard sort of folded to satisfy the AG concept.
A pity that AutoHotkey has nothing for us to emulate tri-state buttons!
Not sure if you have mused yet about a 3-position key and its design.
I think it ought to be a rocker key that you can also press directly
downward, to make 3 possible keypresses. I wish I could find such a
key, but I'm not sure it exists yet - I have been looking at various
industrial key suppliers and can't seem to find one.
Once I scrounge up $100 (assuming the company doesn't go out of
business, then I'd need $1000 to get it off of ebay) to get my own
AG-5, I'm gonna get a Dvorak based layout, and I'll show you all!
At least I'll show you all how well it should work for simple text. I
don't really code that much, it's been over a year since I had to write
a paper in a foreign language, and I have never been able to be
effective with a trackball in first person shooters.
This last part is not any easy part though. It has to be damned clever
to be used by other than power users. I think it even should be a major
feature on the way of the late arrival of a computer input device yet
to come. With a bunch of keys aligned on a rectangular area -- i.e. a
keyboard -- you can't expect any software could help at calling this
something else than a board of keys!
>From my experience with an exceptional combination of hardware and
software that is the FingerWorks device, I can tell that I look at the
AG as one of the same category. I mean that it definitely deserves a
software able to excite user's initiative. It has to be a good one,
softwareLand is where you find the more rubbish in the universe ;o)
Here is what I mean by layout customization: (sorry for the monomania)
http://fingerfans.dreamhosters.com/forum/viewtopic.php?t=161
AutoHotkey is wonderful, still it is one of those softwareLand elements
because it is NEARLY perfect with the AG. The device still sends a
single set of hard-coded keystrokes. With AHK, some transcoding takes
place somewhere between the system layer and an application. This is
clumsy and USB is ready for customizable firmware through a user
friendly software tool based on DFU mode (Device Firmware Upgrade).
One clumsiness for instance, Windows keeps wanting to toggle CapsLock
even when you ask AutoHotkey to handle it like a chording modifier...
It looks just too good to be this easy. If it were only a question of
folding an ordinary keyboard like this we would not be there... :-\
Maybe Mike has a prototype quite like this in a drawer...
Mike?
Here's an exercise I encourage you to try to understand the impact of
such a design:
1) Hold your hands together so your fingers are pointing outwards, as
though you are praying. Try separating your index fingers, then middle,
and all the others. Piece of cake, right?
2) Now put your hands on a table, palms down and elbows out, so that
the middle fingers touch. Now try separating the middle fingers. Pretty
hard, right! Same goes for other fingers - that lateral movement is
very unnatural and quite a stress on your hands.
Whatever multi-press buttons you go with should tend towards the first
type of movement as much as possible. I think this means that lateral
positioning of finger-specific keys is a bad idea. I also think the
keys should be quite small, so that the fingers don't have to move too
much. Unfortunately I don't think there is much chance of creating a
key that moves in more than two directions/has more than two keys and
also minimizes movement. But it is hard to visualize without some
prototype in my hands...
-rob
I must be confused, Lee. The picture I saw was with 4 buttons for each
finger (8 for the index because there are two rows). I think we have
different definitions of this term "lateral movement"? It is that row
of 4 keys that I think would be a strain on the fingers, although it
would be reduced if the keys were small enough.
I think that Carl's monster keys were about the approach I think would
work for 3 key movements from one particular key. Minimal movement to
push or pull for 2 regular keys and then a clickable press for the
third movement. With 4 rows on each hand, this would give 24
non-chorded characters. You could probably add another row for each
index or perhaps just a regular button press for those other keys.
-rob
Even considering the very low 20 grams of the DataHand, the point is
not about how much it takes to activate a key. The single notion of
having the job done is the point. We all put extra force in the process
in order to compensate for variations due to different possible hand
positions when reaching for a key.
With this in mind, lateral activation and lateral positioning are quite
different things. Even with a standard keyboard, which is not what
cares about ergonomics, index movements are not a major concern. But
there are limits though, and pinkies stress is definitely off limits!
I see no problem concerning the two rows for the smart index and your
dividers give a kind of home row to each of the other fingers.
That looks good for the moment! What's next?
What I'm saying is that hitting the four keys requires a lot of
movement that will probably stress the fingers (using the exercises I
mentioned earlier to clarify). Curling the finger in with the knuckle
above the top of the hand causes some stress - while the act of
"closing" the hand/finger (under the bottom of the hand) is less
stressful.
-rob
Mike
-----Original Message-----
From: alph...@googlegroups.com [mailto:alph...@googlegroups.com] On
Behalf Of oggie rob
Sent: Friday, April 07, 2006 8:20 AM
To: alphagrip
Subject: Re: Layouts + images + Carl + AutoHotkey
Using both Ivan's latest config file (dated 20060410) and Lee's config
file, I've combined both together to get the easy readability of
Ivan's version with Lee's extra functionality. That can be found at:
http://www.haveno.net/AG/tmblsn-prettified.ahk
As reference, I used the following as my source:
http://ivanw.club.fr/AG/AG5.ahk.html
http://tmblsn.blogspot.com/2006/03/alphagrip-ag-5.html
There was a "bug" where 'x' was mapped to "Ctrl" and 'z' was mapped to
"Alt" - I switched them to mirror the left side. I also added some
lines to remove any output from hitting a modifier key (shift, ctrl,
alt, Win) with the "thumb" keys.
Additionally, from this "prettified" version of Lee's config, I
created a "dvorak-like" layout. I mostly changed just the alpha
characters. I also added a chorded '-' and '_' to a couple of blank
spaces and swapped the Ctrl/Alt thumb modifiers. The layout looks like
(borrowed from Lee's image):
http://www.haveno.net/AG/AG-nomaded-dvorak.jpg
and the autohotkey config file:
http://www.haveno.net/AG/nomaded-dvorak-prettified.ahk
The "dvorak-like" layout is a work in progress. I would love to get
feedback on this.
-- Edmund.
--
Edmund C. Ng
nom...@gmail.com
"Old joke about the optimist and the pessimist:
The pessimist says, 'Everything is terrible. It can't get any worse.'
The optimist says, 'Oh, yes it can.'"
> There was a "bug" where 'x' was mapped to "Ctrl" and 'z'
> was mapped to "Alt" - I switched them to mirror the left side.
--
Now you mention it, this is an evident disruption of the mirror trait
of all other front side keys.
As the graphics and script hotkeys coding are in sync, either Carl
missed the harmony aspect or he looked at this as a feature, like in:
- to the left for CTRL
- to the right for ALT
...Carl?
> I also added some lines to remove any output from hitting
> a modifier key (shift, ctrl, alt, Win) with the "thumb" keys.
--
I have a hard time to figure out what would be the best way to keep
different flavors of this script in sync.
What you did here with the description of the course of action
necessary to build the resulting script may be all we need for the
moment.
Still, some modularity can be easily achieved with the "include"
instruction supported by AutoHotkey.
Taken from Help documentation, it "Causes the script to behave as
though the specified file's contents are present at this exact
position".
A line like this is all we need to separate the layout configuration
from the implementation part:
#include my_layout.ahk
I like this layout, i'm in a similar position to others, just rec'd my
AG and looking for the most ideal layout to learn. I am hoping to find
an ideal solution for writing c# code in comfort. :)
Writing in visual studio with intellisense, I liked Carl's latest one
with the unshifted arrow keys, but it seems instead it has some other
keys that are shifted that i would be using a lot like . and ;
This layout seems to be a good middle ground, I guess the ideal
solution is going to depend heavily on a persons usage and the tools
they use.
Lee
I can definitely see why you set it up this way now - it does make
sense, but I also agree that it seems hard to do in practice. The
reason I changed it was that I wanted it symetrical, to do the
other-hand-modifier thing.
Man, that was hard/slow to type on the AG-5, even with my dvorak-like config.
-- Edmund.
--
Lee
-- Edmund.
On 4/12/06, Daren <gda...@gmail.com> wrote:
>
>
> >
I have changed this layout so that . and ; are chorded instead of
shifted. I want to take a look at the various other maps that are out
there (like Edmund's) before I release it, but it will be soon. Any
other suggestions for keys that should be unshifted, anyone?
I personally would rather see less finger movement - that is a big
reason I moved to the AG in the first place.
I think there must exist some way to compress all these individual keys
into a smaller form factor.
Carl, considering a new release what do you think about some #include
directives to separate configuration and parameters from
implementation? Several ".akh" files near the ".ini" would be easier to
manipulate if you focus on some specialized tasks.
I did that for the Trackball that I want to use without any mapping
change first, something like
#include AG5_trackball.ahk at the bottom of the ini file
* With MOUSE_BOOST_FACTOR still defined in the ini to keep the default
single point to look for parameters...
* But that AG5_trackball.ahk is made smart enough to be able to behave
standalone if required, even with it's own tray icon and suspendable
feature.
I am going to put the mod online shortly. The not so easy part is about
choosing the best solution for both a standalone and an #include-able
script. I've got one that seems to be working.
- Ivan
I think we should start with Carl's "prettified" config, with
MouseBooster as an optional add-on. It should include Lee's additional
chorded keys. Then, as an optional add-on, Lee's layout/changes. And,
then, after I'm done playing around with this "dvorak-like" layout, we
might want to add that.
-- Edmund.
This is a kind of Request For Comments ;-) We currently have a list of
two identified pluggable components that are the layout and the
trackball. We can start thinking about how to specify these black boxes
inputs and outputs, where they should be uploaded and documented.
In the mean time, any online repository will do. Let's just pick some
peaces here and there and talk about goods and bads. All this will make
sense in time.
I like the idea of separating top-level code functions into various
files/modules so that (skilled) users can choose what to include. It
would be nice if we could figure out a way that people could easily mix
and match the various different ways of implementing various AG
features. Then if someone comes up with a new mod they could just make
it a file to be #included.
>From a software engineering POV, ideally one should make these modules
as self-contained as possible. So ideally we would want all the code
for, say, the mouse booster, to be in one file. Then a user could come
in and just delete the "include mousebooster" line and include their
own mousebooster code instead. I'm not sure if this is possible with
Autohotkey because of its requirements about which program elements
have to precede others - we should look into that.
At first glance, looks good. However, I don't like the 'GPMY' on the
left hand. I think it gives a non-intuitive layout to those coming
from Dvorak.
Then again, I'm a blindingly loyal Dvorak fanboy, I haven't used an
AG-5 yet and not familiar with its limitations, and I don't know how
much commas, periods, and apostrophes are used these days.
-----Original Message-----
From: alph...@googlegroups.com [mailto:alph...@googlegroups.com] On
Behalf Of Didgers
Sent: Wednesday, April 12, 2006 9:39 PM
To: alphagrip
Subject: Re: Layouts + images + Carl + AutoHotkey
The script AG5_trackball.ahk can work standalone as well as #included
by the main script AG5.ahk
* http://ivanw.club.fr/AG/AG5.ahk.html
* http://ivanw.club.fr/AG/AG5_trackball.ahk.html
The icones referenced by those script are here:
* http://ivanw.club.fr/AG/large-green-sphere.ico
* http://ivanw.club.fr/AG/large-blue-sphere.ico
[Shift PrtScr]
... will suspend and resume trackball acceleration
[Win PrtScr]
... will suspend and resume both script processing
[Shift ScrLk]
... will terminate trackball script when it is working standalone (or
suspend it otherwise)
[Win ScrLk]
... will terminate AG5 script
This could be a start for modularization...
-- Edmund.
-----Original Message-----
From: alph...@googlegroups.com [mailto:alph...@googlegroups.com] On
Behalf Of Edmund Ng
Sent: Thursday, April 13, 2006 7:12 PM
To: alph...@googlegroups.com
Subject: Re: Layouts + images + Carl + AutoHotkey
Hey, I just did not realize that Mike went to the same conclusion!
What could be the next choice for theses suspend/exit gestures?
This is an opened choice anyway. With AutoHokey, some smart dedicated
cheat-code sequence could be a better solution than stealing a mod+key
combination. We should keep a buffer with a bunch of last typed in
letters... Anything shorter than "you're dismissed" would be fine...
Win+printscreen
Um, scroll lock is used by my KVM switch for changing computer systems
through keyboard action. It would be very useful if it were available.
Dale
The solution to make everybody happy with our scripts could be to use a
modifier with a keystroke sequence to trigger Suspend and ExitApp
I think that there should not be many of those multiple hotkeys
sequence already in use nowadays.
Anyway this character sequence would be defined at the very beginning
of each script, that each user could easily adjust.
Well personally as someone who codes in c# i'd like unshifted " and
opening brackets ( { [ I don't need closing brackets since i have a
coding aid that automatically adds them, but i think a remap that did
that would then be very specific to coding users.
Perhaps some spare chord combinations in the remap and some
instructions for how somone who hasnt read the autohotkey manual could
duplicate a shifted key to a chorded key would be useful.
I would suggest looking at Ivan's autohotkey config file on how to
reconfigure the layout to your liking. His file has a lot of comments
documenting what each section does.
You only really need to modify a small section near the top, labeled
LETTERS, REDS, etc.
-- Edmund.