FinalVersion

Well _IsPressed is GetAsyncKeyState wrapped, so just use that.

Can't wait for Mode 4.

Blame that on Microsoft

Well AutoIt doesn't support OOP, or Multiple threads, and the list goes on, pretty clear cut. Think I'll just add those 2 languages to my resume

What's the point of this?

@WeiHeXie Complaining about errors will fix them, everyone on this forum is dedicated to fixing your errors.

You're not serious are you? Most of those errors are simply fixed. We're not your personal Google. And as Mat said, both use MFC, so why even go near they before you can even compile a Hello World program.

How are open source programs resources? Your logic has so many flaws. And if you actually want to learn C++, and make an effort You should read this. Directly from the page I linked:

I like how you added it to the context menu, rarely see that, if ever.

Was wondering how long it would take for a cat picture.

Can I have a function call create a gui, and the gui does what it's suppose to. But can I still be performing other things? The only way I can think of this being done is multiple threads, which I don't know if it is possible in Autoit.

The following code lists all files & folders in the current directory. I was thinking of creating a counter, increase it every time a tree view item is added. Then in a for loop, check each item with a IsFolder() function, but there isn't a function that I'm aware of that does that. #include <GUIConstantsEx.au3> #include <TreeViewConstants.au3> #include <WindowsConstants.au3> Local $frmMain = GUICreate("Tree View", 234, 363, -1, -1) Local $tMain = GUICtrlCreateTreeView(0, 0, 250, 380) $hFiles = FileFindFirstFile("*.*") If $hFiles = -1 Then Exit While 1 $cFile = FileFindNextFile($hFiles) If @error Then ExitLoop GUICtrlCreateTreeViewItem($cFile, $tMain) WEnd FileClose($hFiles) GUISetState(@SW_SHOW) While 1 $nMsg = GUIGetMsg() Switch $nMsg Case $GUI_EVENT_CLOSE Exit EndSwitch WEnd

Wow thanks alot, I almost didn't notice your change.

Bump.

Bump.

I'm getting the error 299, which according to MSDN is "Only part of a ReadProcessMemory or WriteProcessMemory request was completed.". I'm unsure what I've done wrong. Also I'm using Windows 7 & running as Administrator. $pMem = _MemVirtualAllocEx($hProc, 0, StringLen($SomeVar) + 1, $MEM_COMMIT, $PAGE_READWRITE) If $pMem = 0 Then MsgBox(16, $Title, "Failed to allocate memory.") Exit EndIf $nBytes = 0 If _WinAPI_WriteProcessMemory($hProc, $pMem, $SomeVar, StringLen($SomeVar) + 1, $nBytes) = 0 Then MsgBox(0, $Title, "Failed to write to allocated memory." & @CRLF & @CRLF & "Error Code: " & _WinAPI_GetLastError()) Exit EndIf

Didn't see your edit, well that sucks.

Yeah I can do it like that, but I'd like the if and declaration of $var on the same line.

I did, but it's not an optional parameter in AutoIt

_WinAPI_WriteProcessMemory($var1, $var2, $var3, StringLen($var3) + 1, 0)

Why do I have to set the last parameter of _WinAPI_WriteProcessMemory() to NULL ( 0 )? MSDN even says the parameter is optional.

That's only 2 possibilities, 0 or 1. What if I wanted to check for something other then 1 or 0?

Why can't you have this sort of If statement? Or am I just coding it wrong? If ($Var = Function(..., ...)) == 0 Then

I decided to not use Visual Studio's awhile ago, but hey, another try can't hurt.

Is there a designer out there? It's a real pain aligning things pixel by pixel, compiling, adjust 1 more pixel, compile, etc... Thanks