Welcome, Guest. Please login or register.

Author Topic: keyboard accessibility tools  (Read 1211 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline KarlosTopic starter

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16882
  • Country: gb
  • Thanked: 6 times
    • Show all replies
keyboard accessibility tools
« on: June 28, 2006, 10:54:07 PM »
Hi,

I am wondering what accessibility tools you all might suggest for:

AmigaOS (3.1+)
Linux (KDE desktop)
Windows (sorry)

This couldn't have come at a worse time (serious work commitments) but I have gone and smashed one of the fiddly bones in my left wrist (the scaphoid for the X-Ray types among you) and look to be wearing this damn gypsum gauntlet for quite some time :-(

What would be nice is some tool I could assign a list of commonly typed words to an easy right hand shortcut (thinking numeric pad based here). For coding purposes this would be ideal ;-)

Suggestions?
int p; // A
 

Offline KarlosTopic starter

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16882
  • Country: gb
  • Thanked: 6 times
    • Show all replies
Re: keyboard accessibility tools
« Reply #1 on: June 29, 2006, 09:45:52 AM »
:bump:

A bit of experimentation last night led to the conclusion that the good old AmigaOS FKey commodity is near perfect.

Anything like this available for linux?
int p; // A
 

Offline KarlosTopic starter

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16882
  • Country: gb
  • Thanked: 6 times
    • Show all replies
Re: keyboard accessibility tools
« Reply #2 on: June 29, 2006, 10:20:26 PM »
I wasted an hour today at work setting up KDE's KHotkeys component of the accessibility options. What a complete pile of sh*t it is. It should come under "inaccessibility options".

Defining a simple hotkey -> text insert requires you to define the text insert as a sequence of key strokes. For example, I wanted the following php skeleton text to be inserted for ctrl-numpad_0

class X {

public function __construct()
{
}

public function __destruct()
{
}

}

You have to define it like this:

C:L:A:S:S:Space:Shift+X:Space:Shift+[:Return:Tab:P:U:B:L:I:C:Space:F:U:N:C:T:I:O:N:.... etc

After developing RSI in my good hand writing this crap, the entire thing was borked anyway. For no apparent reason, it grouped all the fricking duplicated keypresses together in order of first appearence. Eg:

F:U:N:C:T:I:O:N -> funnctio
C:O:N:S:T:R:U:C:T -> conssttru

etc.

Doing all the various system updates made not one iota of difference :lol:

Somebody's idea of a joke?
int p; // A