Wiki: Troubleshooting Article Needs Reorganization
IMO, the current Troubleshooting [Keyboard Maestro Wiki] article is too long, and thus becomes overwhelming to many users, including me. My eyes glaze over.
Maybe we need a simple top-level page, which is just the top-level of the below outline. Then a separate page for each major heading. OR, maybe the top-level page should be the complete TOC, so the user can search/scan?? What do you guys think/prefer?
I propose that we reorganize it with headings and subheading, something like this. This is just a draft and needs your review and feedback.
I have tried to put the outline in the order of most-often occurring issue:
Table of Contents
Macros Not Firing (Triggered)
Macros Not Firing After I Login
Macros Not Being Saved
Timing (of Actions)
Sometimes the Wrong Thing is Pasted
Sometimes Typing in Password Fields Drops Characters
Removing Styles Changes The Text
No Palettes or Dialogs Appear
The Global Floating Palette has disappeared
Typed String Triggers Not Working
Not Being Able To Enter a Hot Key
Unable to Use Typed String Trigger (Secure Input Mode)
Something Unexpected is Happening
Run-Away Login Macros
Reinstall Keyboard Maestro
Preference Write Failed (how would the user know?)
App Translocation Security
Issues with Other Applications
Apple Mail -- Insertion Cursor Vanishes ( current title: The Case of the Vanishing Insertion Cursor in Mail
Photoshop and Finale -- The Select Menu Item Action Is Not Working
Google Chrome -- Actions are Not Working
Safari -- Actions are Not Working
Scripts Are Not Working Because the Path is Wrong When Executed in Keyboard Maestro
Execute Script Actions are Not Working
User Interface Issues
White Menus or White Switchers or Palettes
Stuck Modifiers Keys and Wacom Drivers
Yosemite GM and Accessibility Settings Problems
Yosemite and Accessibility Settings Problems
Virtual Machine Issues
Not Working With Parallels
Other troubleshooting information
Also a number of the headings that many users many not recognize or understand.
- The headings need to be in terms the user will understand.
- They need to be in terms of the symptom the user sees.
@peternlewis, is there any automated way to reorganize the wiki page using just a new TOC? Or does it require the usual hard labor?