Leaderboard

Done. Thanks

Based on the Outlook UDF written by wooltown, we (wooltown and I) decided to extend the functionality of the Outlook UDF. As the OutlookEX UDF ("EX" like "extended") has a completely different approach compared to the Outlook UDF it's a complete rewrite. We would like to discuss the design of the UDF with the community. Every feedback, function request etc. is highly welcome. As soon as the discussion shows that we are on the right track we would like to release an alpha version for everyone to test. So please don't be shy and post what you think of this UDF or what functions you need! Every item in Outlook is uniquely identified by EntryID and StoreID. The default StoreID is your inbox Every item has properties to describe the item (subject, startdate ..) and methods to act upon the item (move, delete …) The search and action functions are now separated. As an example the user first searches for the items to be deleted and then calls the delete function If a method can be used for more than one item type (e.g. mail, calendar and notes) the function is called _OL_ItemXXX else the function is called _OL_CalendarXXX The number of properties you can get or pass to most functions is not limited by the number of parameters defined for the function. Properties can be passed as parameters (up to 10) or in an unlimited array as parameter 1 The UDF allows to access all kind of folders (see the following listing). Folders can be passed by name or as an object to a function A lot of testing is still needed as we have written and tested the functions using Outlook 2002 SP3 and Outlook 2010 "wrapper" or "shortcut" functions will be available to let you do all tasks in one go e.g. _OL_Wrapper_SendMail for all functions above. Documentation: The documentation for this UDF (aside from the docu in the UDF itself) will be placed in the AutoIt Wiki. So we can easily modify the docu without releasing a new version each time. There will be pages describing the UDF in general and pages for individual item types (like mail) with detailed information and a lot of tips & tricks. Tested with Outlook 2003 and 2010. Some users reported that it works with Outlook 2013 as well. Starting point: http://www.autoitscript.com/wiki/OutlookEX_UDF_-_General Download

I built my own libcurl for AutoIt based on BinaryCall UDF. libcurl - the multiprotocol file transfer library The Features: Pure AutoIt script, no DLLs needed.Build with SSL/TLS and zlib support (without libidn, libiconv, libssh2).Full easy-interface and partial multi-interface support.Data can read from or write to autoit variables or files.Smaller code size (compare to most libcurl DLL).The version information of this build: Curl Version: libcurl/7.42.1SSL Version: mbedTLS/1.3.10Libz Version: 1.2.8Protocols: ftp,ftps,http,httpsHere are the helper functions (not include in libcurl library). Curl_DataWriteCallback()Curl_DataReadCallback()Curl_FileWriteCallback()Curl_FileReadCallback()Curl_Data_Put()Curl_Data_Get()Curl_Data_Cleanup()See the example script for detail usage. Curl.zip

crustymonkey, The script clearly states: The following list of files MUST also be present in the script directory to compileand once I move those files (the include list) to the same folder the script compiles without problem. But this is not recommended practice and coders should normally not have to do this. M23

@Jewtus: the functions from the link are now integrated to the _WinAPI_* lib. E.g. _WinAPI_GetParentProcess.

@TheNewHunter Make sure you post your solution, so that anyone that has the same problem can see how you solved it.

StringSplit all the way my friend, Even if it's just for ease of reading when you come back to a code a few months later (it's amazing how a solution to a problem you face can seem innovative at the time, But then Jargon when you come back to the code.) Even if you're just looking for the left part of the string, StringSplit can accomplish this: $text = "some = text" $Left = StringSplit($text,"=")[1] ;Notice the array number $Right = StringSplit($text,"=")[2] ;These run the stringsplit command, And then return that element to the variable from the resulting array Consolewrite($Left) ConsoleWrite(@CR) ConsoleWrite($Right)Just a handy little trick I discovered after a while of using AutoIt, The same applies to any commands that return arrays. Cheers Javi

Just reporting that I have been sidetracked by other things, including working on my Audio DVD Producer program, and doing my head in from reworking the predictive elements for projected project time and size ... so many variables now. That all means I have avoided further testing and investigation with the latest issue here. Despite that, I have still been using the program and making purchases, and not experienced any further trouble. So upon a little more thought, I reckon the issue only occurs in a specific set of conditions, and probably very unlikely ones at that. The prompt I have already mentioned should address that and make the likelihood of the same conditions even more remote.

232showtime, Nothing is wrong with the ControlCommand. It is just that some applications do not react to some commands in a standard manner, particularly "IsChecked". In the past it has sometimes proved necessary to resort to Pixel* functions to determine the state of a checkbox. M23

GUICtrlSetOnEvent(-1, "MyFunction")

Error checking is missing. If it is run twice, the second script will never recognice numpad+ and will never end. Here my snippet for hotkey usage: _HotKey("{ESC}") _HotKey("^b") Func _HotKey($hotkey = "") ; ! ALT + SHIFT ^ CONTROL # WinKey Switch @HotKeyPressed Case "{ESC}" Exit 0*MsgBox(64 + 262144, Default, "Exit", 1) Case "^b" Beep() ; delete ";" to temporarely disable hotkey ; HotKeySet(@HotKeyPressed) ; send("^b") ; HotKeySet(@HotKeyPressed,"_Hotkey") Case Else If Not IsDeclared("hotkey") Then Return MsgBox(16 + 262144, Default, "No CASE statement defined for hotkey " & @HotKeyPressed) If HotKeySet($hotkey, "_Hotkey") = 0 Then Return MsgBox(16 + 262144, Default, "Hotkey " & $hotkey & " invalid or set by another application.") EndSwitch EndFunc ;==>_HotKey While Sleep(100) ; here should be your application. WEnd ; meanwhile, here is a dummy loop.

put this code at the point where you'd like to flush the clicking While GUIGetMsg() WEnd

​yea ... guess it was getting toooo late for me..

An odd number in the 3rd place (here: 13) denotes a beta vesion. For a version 4 of AutoIt I would expect a low number of 1 or 3

@‌Newb glad to help. Please mark the thread as solved, ... and perhaps a 'like this' to my answer.

There is the case else missing. case else return true