#Good mouseless games code#

XCoordToUse := ConvertInputCoord(XcoordInput, 'X') Global VerticalScale, numberOfRows, numberOfCols, GridHeight, GridWidth, rowSpacing, colSpacing Gui, Show, W%GridWidth% H%GridHeight%, CoordGrid Gui, add, edit, x%colXCoord% y%rowYCoord%, %colXCoordAlpha%%rowYCoordAlpha% gui, add, edit, x%colXCoord% y%rowYCoord% ReadOnly cRed, %colXCoordAlpha%%rowYCoordAlpha% StringUpper, colXCoordAlpha, colXCoordAlpha StringUpper, rowYCoordAlpha, rowYCoordAlpha RowYCoord := (numberOfRows - 1 - rowCounter) * rowSpacing

Global VerticalScale, numberOfRows, numberOfCols, GridHeight, GridWidth, rowSpacing, colSpacing, KeyArray GridHeight := VerticalScale * A_ScreenHeightĬolSpacing := 1.025 * GridWidth / numberOfCols I've attached a screenshot showing the grid overlaying a Notepad++ window, part of a Chrome window, and part of my desktop. I might need to tweak the small values added and subtracted from the coordinates to ensure that the click is sent as close to the centre of each button as possible, and also the colSpacing constant. As most clicking activity tends to happen round the edges of the screen and not in the middle, I might look at reducing the row / column spacing round the edges only I might add coordinates 0-9 for screens with more pixels I chose 'Edit' controls as buttons as their white background made them easy to read. There's a trade-off between minimizing the size of the buttons so as not to obscure what's behind them, and keeping them big enough to read. There are a few things I'd like to improve: You could even look at it as an accessibility tool. on any given screen, most buttons will probably not be usefulīut as somebody who likes to avoid using the mouse, I already find it useful - I hope others will too. you won't always be able to click on everything you need to

#Good mouseless games code#

Includes code around timing of key presses which 'scriptor' (thanks!) posted here: Inspired by the cVim chrome plugin, which provides shortcut keys to most links / buttons on web pages. Pressing NumKeyEnter thereafter toggles the grid (it displays much faster after the first time, as it has already been built) You can then emulate a mouse-click (or a touchscreen 'touch') at any of those 676 locations by entering the coordinates, as displayed on each button, as keyboard shortcuts. When you press NumKeyEnter, this script builds then displays a 26*26 grid of buttons (actually AHK edit controls), labelled AA-ZZ, overlaying the whole screen.

(I finally got round to a solution for the question I posted last year at. AHKCoordGrid - overlay grid of buttons to provide (some level of) mouseless screen navigation