Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/19/2019 in all areas

  1. Melba23

    new website

    Bye! M23
    2 points
  2. seadoggie01

    The Missing Mouse

    Oh. Well, isn't that convenient. Guess I'll google my issue next time. (Thank you though, I try)
    1 point
  3. BrewManNH

    The Missing Mouse

    <snip> wrong section
    1 point
  4. Got it sorted !!!!!!!!!!!!!!! 🙂 I ran the ".au3" script and got the error message. However, I then went into Task Manager and clicked on the Autoit3.exe process. Then I selected "Open File Location". It was running an old version of Autoit3 located within a folder (it was for a small portable app that I created for my memory stick). I deleted that version and when I ran the script again it worked!!!! Really weird as the default pointed to the Programs(x86) folder, and I also tried the "open with" menu option (and navigated to the Programs(x86) folder). Anyway, it is all working again 🙂 Many thanks for all your help. Hopefully, one day I will be as knowledgable as you guys 🙂 Best regards, Pete
    1 point
  5. Macro BlockInput(bool) BlockInput_(bool) EndMacro BlockInput(1) Delay(3000) BlockInput(0) I fixed two functions. There it is not possible to get the size of the field to return data. Procedure.s DriveGetLabel(Drive$) Protected Label$ Label$=Space(#MAX_PATH+1) If Not GetVolumeInformation_(Drive$,Label$,#MAX_PATH+1,0,0,0,0,0) Procedure_Error = 1 ProcedureReturn "" EndIf ProcedureReturn Label$ EndProcedure MessageRequester("Disk label", DriveGetLabel("C:\")) Procedure.s DriveGetFileSystem(Drive$) Protected FileSystem$ FileSystem$=Space(#MAX_PATH+1) If GetVolumeInformation_(Drive$,0,0,0,0,0,@FileSystem$,#MAX_PATH+1) ProcedureReturn FileSystem$ Else Procedure_Error = 1 ProcedureReturn "1" EndIf EndProcedure MessageRequester("File system type", DriveGetFileSystem("C:\"))
    1 point
  6. Epicface, FrancescoDiMuro is quite right - please read the Forum rules - particularly the bit about not discussing game automation - before you post again. Thread locked. But welcome to the AutoIt forum - and see you soon with a legitimate question I hope. M23
    1 point
  7. junkew

    Some help with ControlClick

    Uia and control functionality should not be mixed as that will not work. Study examples from uia thread or try simplespy that will give some direction.
    1 point
  8. If the source Excel file is essentially permanent data, your best friend will be to extract an array (an SQL table in fact) from the sheet using Excel ADO interface and create an SQLite DB from that. You'll get all desirable flexibility with this setup. If your source is expected to significantly vary over time (i.e. it isn't a one-time operation) you can just use Excel ADO to query it.
    1 point
  9. A Excel workbook can be accessed like a database using ADO (example). This allows to bypass all Excel limitations.
    1 point
  10. It's almost the same; only the way you get the 2-Dimension array changes. You need to read the whole sheet in an array, then make a comparsion of a value to extract the data in separate files. One of the easiest way yo do that is using _Excel_RangeRead() with the parameter $bForceFunc set to true as @water suggested, so you'll have the array with all the values, and then you can do whatever you want. But, you could think to use an SQLite database either, which could save you for sure some time. You can find Excel to SQLite converter(s) online, and manage all the SQLite stuffs using _SQLite_* functions in AutoIt
    1 point
  11. @RTFC Thanks for the vote of confidence, I am also hoping to learn a lot of new things and gain interesting experiences when working on this project
    1 point
  12. Interesting thread, somehow missed it before. For what it's worth, speaking from personal experience, I think it's worth pursuing (regardless of the merits of having a native AutoInux), because nothing ever taught me more about programming design and coherent, consistent language structure than when I had to develop my own programming environment a few years back (now mainly used by other people). If you can spare the time and effort and you think it's worthwhile, make it happen.
    1 point
  13. So I think it's time to publish this little tutorial I have made on using DllCall() and DllStructs. It's not near completion but I think it's a good start at least This tutorial is mostly aimed for people who have never used DllCall() before or have very limited knowledge about it. In the future I will update it with more advanced topics so more advanced users can make use of it too. Well here goes. Dealing_with_Dll.pdf Previous downloads: 31 Suggestions, language corrections and errors in the tutorial is of course welcome.
    1 point
×
×
  • Create New...