Jump to content

Leaderboard

Popular Content

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

  1. @mLipok Thank you for the suggestion works better
    1 point
  2. BrewManNH

    Help with input box

    You can use ControlClick, but it doesn't use the mouse coordinates, it's used to click on a control.
    1 point
  3. Melba23

    Help with input box

    Zag8888, Welcome to the AutoIt forums. For your future coding, as InputBox returns a string, you should really write the comparison as follows: If ($xi = "1") Then as AutoIt can sometimes give you unexpected results if you compare different datatypes. This is because its automatic data conversion "feature" might not convert the elements in the way you think it should. So it is always best to force the elements into the same datatype - string in this case. M23
    1 point
  4. Rex

    Help with input box

    You need to tell Mouse click which button to use: MouseClick ( "button" [, x, y [, clicks = 1 [, speed = 10]]] ) From the help file #include <AutoItConstants.au3> ; Double click at the current mouse position. MouseClick($MOUSE_CLICK_LEFT) MouseClick($MOUSE_CLICK_LEFT) ; Double click at the x, y position of 0, 500. MouseClick($MOUSE_CLICK_LEFT, 0, 500, 2) ; Double click at the x, y position of 0, 500. This is a better approach as it takes into account left/right handed users. MouseClick($MOUSE_CLICK_PRIMARY, 0, 500, 2) So this should do the trick #include <AutoItConstants.au3> $x1 = InputBox("xx", "xxxx?") if ($x1 = 1) Then MouseClick($MOUSE_CLICK_LEFT,132,393,1) Sleep(5000) EndIf Cheers /Rex
    1 point
  5. Is http://signin@com a valid URL? Doubtfully.
    1 point
  6. 0xC3 is the first byte of a number of UTF8 sequences. By itself it's invalid unless followed by a suitable sequence, forming a valid UTF8 codepoint representation. For instance 'à' (U+00E0) encodes as 0xC3 0xA0 in UTF8. Invalid lone 0xC3 in the middle of a UTF8 string (the source in pic 4) probably confuses the UTF8 detection. Overwrite all the bad-looking à in the UTF8 source and all should work fine.
    1 point
  7. As you are on start with using ADO (I suppose) ..... I suggest to you to use my ADO.au3 UDF.
    1 point
  8. @TheDcoder, ...just go for it. Do your thing. Am sure that, as working code gets done, ppl will help. I for once voted for testing, as I'm not a programmer. If I was, and had the know how, and the experience, and the time, and the drive, I'd go at it. The worst that could happen is that you learn a thing or two. Follow your muse.
    1 point
  9. Look if you want to do it then what’s stopping you? It’s not my vote you asked for my opinion and I gave it but if you want to do it then don’t let any of us stop you
    1 point
  10. Come on folks, where is your heart, don't be so outright discouraging with your voting. Why so negative? Everything starts with a dream, and not all dreams come true, but allow him that one in a million chance ... you know you really want it. Truth or reality is often stranger than fiction. Anyway, a good experiment for the lad, and a wonderful journey .... sure to learn a thing or three. It's not like he is going to mortgage his house in this endeavor.
    1 point
  11. Try something like this here: #include <GDIPlus.au3> #include <GUIConstantsEx.au3> _GDIPlus_Startup() Global $hImage = _GDIPlus_ImageLoadFromFile(@ScriptDir & "\Dimp.png") Global $aDim = _GDIPlus_ImageGetDimension($hImage) Global $hImage_Negative = _GDIPlus_BitmapCreateNegative($hImage) Global $hGUI = GUICreate("Test", $aDim[0], $aDim[1]) GUISetState() Global $hCanvas = _GDIPlus_GraphicsCreateFromHWND($hGUI) _GDIPlus_GraphicsDrawImageRect($hCanvas, $hImage_Negative, 0, 0, $aDim[0], $aDim[1]) Do Until GUIGetMsg() = $GUI_EVENT_CLOSE _GDIPlus_GraphicsDispose($hCanvas) _GDIPlus_ImageDispose($hImage_Negative) _GDIPlus_ImageDispose($hImage) _GDIPlus_Shutdown() Func _GDIPlus_BitmapCreateNegative($hBitmap) Local $aDim = _GDIPlus_ImageGetDimension($hBitmap) Local $hBitmap_Neg = _GDIPlus_BitmapCreateFromScan0($aDim[0], $aDim[1]) Local $hGfx = _GDIPlus_ImageGetGraphicsContext($hBitmap_Neg) Local $hIA = _GDIPlus_ImageAttributesCreate() Local $tNegMatrix = _GDIPlus_ColorMatrixCreateNegative() Local $pNegMatrix = DllStructGetPtr($tNegMatrix) _GDIPlus_ImageAttributesSetColorMatrix($hIA, 0, True, $pNegMatrix) _GDIPlus_GraphicsDrawImageRectRect($hGfx, $hBitmap, 0, 0, $aDim[0], $aDim[1], 0, 0, $aDim[0], $aDim[1], $hIA) _GDIPlus_ImageAttributesDispose($hIA) _GDIPlus_GraphicsDispose($hGfx) Return $hBitmap_Neg EndFunc ;==>_GDIPlus_BitmapCreateNegative
    1 point
  12. Is the picture the same size in its default open size as what is seen on the screen? If you can post the 1.bmp and let me know where it is to be found I will try to fix it. *Edit - Found where you got your code In the comments of that video it says: Replace the dll by one compatible with Windows 7 and/or 64 bit operating systems. Reinstall AutoIt for x68 operating system. I can only test it in Windows 7 x64 and xp x32 on my end.
    1 point
  13. I jumped from AutoIT into PHP. They're extremely similar. For me all I had to really do most of the time was lookup what function in autoit was similar to what in PHP. AutoIt / PHP StringLen / Strlen FileWrite / FilePutContents FileRead / FileGetContents DirCreate / MkDir FileDelete / Unlink StringLower / StrToLower and all of those functions have the SAME arguments as AutoIt. I had a working registration script in probably an hour first time with PHP. ; \/ AutoIt \/ $name = "Eude" $loves = "Cake" If ($name == "Eude") Then If ($loves == "not Cake") Then Else ConsoleWrite($name & " loves " & $loves) EndIf EndIf ; \/ PHP \/ $name = 'Eude'; $loves = 'Cake'; If ($name == 'Eude') { If ($loves == 'not cake') { } else { echo $name . ' loves ' . $loves; } }
    0 points
×
×
  • Create New...