AutoHotkey Community

[Invalid User]

I think a fun way to keep all the users that are active in tune could be a fun game. Something like code based puzzles like "Find What is wrong" could be fun, at least something for us (me) to do. Rewards could be updated versions 10 seconds before public realease... or somthing retarded or of the like, what ever, or maybe just a point system. Who knows. Puzzles could be working tests of code modified so they dont work like they should. I dont know. I just get bored sometimes and want somethign to do. Rules of the game could be...

The puzzle is presented.
the thread is locked for one weeks time
The User to post the most effective code wins, judged by the AHKs best...
And A new problem is posted.

of course if a user posts the code asking for help in any thread is disqualified.

OH dear bordom has hit hard.

[BoBo]

I would be more then happy I've you could teach me HowTo use [ASCIIDoc]

Another perfect thing would be to teach AHK's GUI (in case you're bored), with screenshots, of course!

Invalid User - The GUI (1)

[toralf]

I was already thinking of making a GUI guide, similar to http://www.autohotkey.com/forum/viewtopic.php?t=2307

But if your bored, go ahead.
_________________
Ciao
toralf

[toralf]

How about this as a starting point:

A short guideline that might help with GUIs:

- Try to avoid Goto, use GoSub instead
- Try not to use AutoLabels for Buttons, use g-label (or sometimes just called Labels) instead
- Give every control that has to perform an action (when selected by the user) a g-label
- Give every control that you want to manipulate during run a variable (you can manipulate the control with GuiControl)
- Give each Label and variable a speaking name, e.g. ApplySettings, BuildGUI1MainWindow, ChkBackGround, EdtOptionsMainwindow
- Use SetTimer instead of Loops with Sleep to do task that repeat after a certain time.
- Seperate the code that creates the look of the GUI from the code that performs the action of that GUI (g-labels) by putting them into seperate subroutines.
- With multiple windows, include in every GUI and GuiControl command the Gui ID. Otherwise AHK might at times not know which window to work on.

[...]

- In any other question read and search the manual, all questions are mostly answered. Otherwise look for examples. And then ask for support in the forum.
_
_________________
Ciao
toralf

[Chris]

[Invalid User]

I too have started creating a Neophytes guide to AHK it am breaking it down into lesson and it covers everything to Guis to String processing. it should be in depth but easy to understand for a beginner
_________________
my lame sig