Leaderboard

Here is a small and simple little script for creating a tiny cpu indicator bar that sits right above the taskbar like in the pic below. I got the idea from an android phone app called micro cpu and liked the concept. _TinyCPU.au3

November 26, 2007 Ver 1.4.8 * Over 19 InterActive GUI's * Over 50 Step-by-Step Scripts * Verbal Instructions * Complete with Demonstrations. * and Answers * Exe Format for New People DOWNLOAD AUTOIT 1-2-3 Written completely with AutoIt to Demonstrate some of the Capabilities of AutoIt May not Work with Windows 98 ( tested once = fail) Re-Testing is now possible ( Click "Search Help" then type in "me dummy, you fix" ) Enjoy!!! Valuater 8) When you have completed Autoit 1-2-3, be sure to see XSkin.au3 Due to Jon's request to "trim" this thread.... Only Level III Exams will remain....Thanks

Use     $idFileTreeView = GUICtrlCreateTreeView(10, 10, 250, 350)     $hFileTreeView = GUICtrlGetHandle($idFileTreeView)

@seadoggie01 Yes I have found this documentation. After quite a bit of trial/error, I had come to the conclusion that we need to launch the ActiveX in order to successfully use the object.

You could also try to use COM object to print. I have been using it successfully like this : #include <Constants.au3> #include <GUIConstants.au3> Global $oMyError = ObjEvent("AutoIt.Error", "_ComErrFunc") _Print_PDF() Func _Print_PDF() Local $hGUI = GUICreate("Example") Local $idPrint = GUICtrlCreateButton("&Print", 310, 370, 85, 25) GUISetState() Local $sFile While 1 Switch GUIGetMsg() Case $GUI_EVENT_CLOSE ExitLoop Case $idPrint $sFile = FileOpenDialog("Choose a PDF File", @ScriptDir, "PDF Files(*.pdf)", $FD_FILEMUSTEXIST+$FD_PATHMUSTEXIST) If Not @error Then _AcroPrint ($sFile) EndSwitch WEnd EndFunc ;==>_Print_PDF Func _AcroPrint($sFile) If Not FileExists($sFile) Then Return SetError(1) Local $oPDF = ObjCreate("AcroPDF.PDF.1") If Not IsObj($oPDF) Then Return SetError(2) ConsoleWrite($oPDF.GetVersions & @CRLF) $oPDF.src = $sFile GUICreate("") GUICtrlCreateObj($oPDF, 0, 0) $oPDF.PrintAll() EndFunc ;==>_AcroPrint Func _ComErrFunc() MsgBox($MB_SYSTEMMODAL, "AutoItCOM Error", _ "We intercepted a COM Error !" & @CRLF & @CRLF & _ "Description is: " & @TAB & $oMyError.description & @CRLF & _ "Win Description:" & @TAB & $oMyError.windescription & @CRLF & _ "Number is: " & @TAB & Hex($oMyError.number, 8) & @CRLF & _ "Last Dll Error is: " & @TAB & $oMyError.lastdllerror & @CRLF & _ "Script Line is: " & @TAB & $oMyError.scriptline & @CRLF & _ "Source is: " & @TAB & $oMyError.source) SetError(100) EndFunc ;==>_ComErrFunc

I don't understand exactly what you want, but maybe this concept/princip: Func body2() While 1 Sleep(500) $red = PixelSearch(111, 264, 146, 288, 0xFF290C) $red_ok = Not @error If $red_ok Then Sleep(200) MouseWheel("down", 10) Sleep(400) ContinueLoop EndIf $white = PixelSearch(103, 218, 141, 241, 0xFFFFFF) $white_ok = Not @error If $white_ok Then Sleep(200) MouseMove(123, 243, 2) Sleep(100) MouseDown("left") Sleep(300) MouseUp("left") Sleep(100) ExitLoop EndIf If Not ($red_ok Or $white_ok) Then Sleep(300) MouseWheel("up", 10) Sleep(300) MouseWheel("down", 10) Sleep(1000) EndIf WEnd EndFunc ;==>body2

Look here - catch TVN_SELCHANGE in WM_NOTIFY:

If only all apples and oranges were the same, and they all fell off the tree at the same time. A bit hard to do a conclusive test I reckon. Sluggishness on my power challenged Netbook resolved itself after I disabled said items, so that is conclusive enough for me in my circumstance.

The console says nothing, I've been trouble shooting this for months and I can't figure it out... Here is what I've tried so far... Compiling sections of the program into .exes (Helped) Writing the variables into arrays then to .csv & pulling from them from each section of the program(Helped) Loading all the variables from a .csv into global Arrays & read/writing in each section of the program(made it worse) Used reducememory at the end each 1 minute and reinitialized the global variables into arrays from a .csv(Helped) There aren't any visible memory leaks in task manager & there isn't an explanation I could find anywhere. I rewrote all the variables & function executions into nested for loops & nested arrays. (Maybe helped?) Only thing I know for SURE is keeping the code as simple as possible IE less than 300 lines of code it never crashes. Anyone have any ideas?