RobertKipling

I played with this a bit; my compiler seems mad that the $current_win and $child_hWnd are "possibly used before declaration". Doesn't seem like a big deal, though...

Whoops, I took another look at the code: Apparently you don't need to include textedit.au3 with the program, since all the functions already take care of themselves. RKPad also keeps the name of the current file displayed in the titlebar, which might be difficult to add with that UDF.

Take a look at the tutorial helpfile -- it'll give you an idea how to use the barest scripting functions. And if you use your keyboard enough, you should be able to do the rest with a tiny bit of trial-and-error. Switching from VB to AutoIt is a breeze.

Try this: 1. after closing your popup, get the handle of the topmost window 2. while the window is not active... 3. try to activate it 4. *then* send Ctrl+C. Local $topgui = WinGetHandle("") While Not WinActive($topgui) WinActivate($topgui) WEnd Send("^c")

If you're looking for a quick fix, create a tiny window that's topmost with a "toolbar button" on it that follows the closest Firefox around and positions itself over top. Otherwise, sorry to say I've never written a plugin for Firefox in my life.

Have you tried anything in AutoIt yet? Can we see what you've written?

Did you consider using HotKeySet, or maybe accelerators? (They're heaps of fun, but the user's manual has the best examples.)

Messing with HTML in webpages isn't fun. (I should know; half of the scripts I write are some kind of mass content-extracting ones.) AutoIt supports a web browser object; could you just download the file with InetGet, change the content, and display it in a GUI form? I know it's not what you're looking for, but IE doesn't let you save changes to documents without a fight.

Ouch! My apologies on the source code (I should have tested them on a version of AutoIt before posting). Apparently I haven't updated the compiler either since late 2007. I didn't think commands would be depreciated that quickly. When was TextEdit made? It would have been a timesaver back when I created this...

After leaving it dormant for at least a year, I've finally decided to finish what I started and just complete RKPad already literally in a "midnight release." I had already "enhanced" a buggy version of it for programming in Assembly Language, but on another computer I had created one with functioning Find and Replace. Well, enough rambling; I'll just do a sales pitch for RKPad Text Editor *Fully customizable to suit any programmer's needs! *Comes with a few dozen auto-content commands already confugured *Open or run files in any external editor *Making plugins is a snap (with optional AutoIt compiler) *Backwards-compatible to Windows 95 New in 2009: *Fully functional Find/Replace! *Easier than ever create auto-content menus. *Extra options for plugins -- easier than before to access parts of a file's name *Vista-ready (window resizing bug fixed) Future plans *Make textbox into RichTextBox (experiencing bugs in ANSI versions of Windows) *Make configurable for several languages from a master INI file *Documentation all in one place Download here! RKPad 2009 rkpad09.zip Source code included and documented For Windows 95-Vista Bugs found, improvements made? Please PM me and I'll make necessary changes.

I've had a little trouble with getting events triggered with ListBoxes in the past... is there a simple way to get the ListBox to notify on single click instead of double click?

This topic looks almost identical to another one that appeared a little while ago... Hmm. Must have been a coincidence.

Here's the source code for the project; sorry I didn't include it earlier but it's a lot of content. prompt.zip

Try pressing TAB multiple times while in the Flash window. It might cycle through clickable elements. There's a recording tool that comes with AutoIt, it's okay, but getting the timing right might take a little more effort.

Long story short, I'm trying to write an advanced command prompt. Some of the programs will be launched from the GUI I created (which resembles the DOS prompt), and some of them will be user-interactive, with their output streamed into a text box and the input taken from either the keyboard or another text box below it. The problem is, when I got the program to interact, output-only functions like "dir" worked perfectly, but other ones, like "prompt" which required input, would freeze the program and really mess up the processor. Any suggestions? $foo = Run(@ComSpec & " /c " & $data, $currentdir, @SW_HIDE, $STDIN_CHILD + $STDOUT_CHILD) do ;; run While 1 $line = StdoutRead($foo) If @error Then ExitLoop if $line <> "" Then GUICtrlSetData($txtMain, $line, "add") ;MsgBox(0, "STDOUT read:", $line) Wend if not WinExists($foo) then ExitLoop do $msg = GUIGetMsg() until $msg = $button1 MsgBox(0,"","Writing OUT") StdinWrite($foo, GUICtrlRead($txtPrompt)& @CRLF) StdinWrite($foo) until not WinExists($foo)