Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/28/2023 in all areas

  1. This is related to the use of Clipboard which will be gone in the next version... It was a nice try but isn't working as hoped. I don't have the issue in my current version... hope to be able to share it soon.
    2 points
  2. Progress Update Animation aspects of battle mode are more or less in place, shaky but improving. Working on smoothing out some kinks and adding more animation stuff. Have a few bugs to work out that are causing some of the animations to be a little jumpy on screen. (You can see in the video when opponent goes to defend an attack using a force field ability). Will be tackling that next. I've also got to add in the rest of the mathematics for HP and MP calculation, and to reflect that result in the health bars. I think after that, as far as code goes for this "arcade" battle mode, the base process for that will be done. (Still need to draw a bunch of stuff too). Once I have this done, I'm going to work on finishing the GUI and getting the rest of the interface to a more operable state. Also added a shortcut to the screen recording at the top of the original post in this thread. PS @TheDcoder ShareX is cool, but I still like OBS better I'll play around with ShareX some for the next screen recordings.
    2 points
  3. Take a look at _WD_Status and _WD_CheckContext.
    1 point
  4. Maybe a better option is to refrain from making such a comment when you have no clue as it In this case it is a one time issue when the new cache files are created so hence not so obvious as that only happens when they don't exist or a newer AutoIt3 is loaded, so this would not show up for anybody upgrading the FULL SciTE4AutoI3. ... and honestly these kind of silly comments don't belong here either. This is not the Chat forum where you guys normally dump your every thought into many threads. For clarity: I am fine you all enjoy the Chats there.
    1 point
  5. That's impossible to determine: binary data may contain NULL byte at any place, so contrary to strings, there is no stop sign. Only the allocator of the binary data knows how large it is. And you never know if the pointer is pointing to the base or in-between the data.
    1 point
  6. #NoTrayIcon #include <WinAPI.au3> #include <GUIConstants.au3> Local $hApp = WinWait("My App") Local $iHeight = _WinAPI_GetSystemMetrics($SM_CYCAPTION) Local $iWidth = 100 Local $aPos = WinGetPos($hApp), $aPosPrev = $aPos Local $hOver = GUICreate("Over", $iWidth - 8, $iHeight + 7, $aPos[0] + $aPos[2] - $iWidth, $aPos[1] + 1, $WS_POPUP, $WS_EX_TOOLWINDOW, $hApp) ; * <- 1 ;~ GUISetBkColor(0xFFFFFF) GUISetState(@SW_SHOWNOACTIVATE) WinActivate($hApp) ; * <- 2 $newColor = PixelGetColor($aPos[0] + $aPos[2] - 106, $aPos[1] + 14) GUISetBkColor($newColor, $hOver) ;~ _WinAPI_SetWindowLong($hOver, $GWL_HWNDPARENT, $hApp) While WinExists($hApp) Sleep(10) ;~ $newColor = PixelGetColor($aPos[0] + $aPos[2] - 106, $aPos[1] + 14) ;~ GUISetBkColor($newColor, $hOver) If WinActive($hOver) Then WinActivate($hApp) ; * <- 3 $aPos = WinGetPos($hApp) If @error Then Exit ConsoleWrite('-> unexpected exit' & @CRLF) ; * <- 4 If $aPos[0] = $aPosPrev[0] And $aPos[1] = $aPosPrev[1] Then ContinueLoop $aPosPrev = $aPos ; * <- 5 WinMove($hOver, "", $aPos[0] + $aPos[2] - $iWidth, $aPos[1] + 1) WEnd
    1 point
  7. A few thoughts about your project. I think it is a big project with a lot of work (DESIGN, coding, testing, debugging, documenting ...) you have started. I have emphasised the DESIGN phase as this is - from my point of view - crucial for such a big project. If I would start such a project I would run a poll to see how many users have the need to automate OO/LO Ask people about their priority. Means: Which modules do they need most (Writer, Calc, ...) I would split this project into multiple files: a general file with those functions needed by all modules like copy/paste, formatting, saving/exporting ... a file for each module I would try to copy the functionality from Word/Excel UDF to OO/LO because the user's requirements are always the same, regardless of the software product used. Just my 2 cents worth. Good luck with your project!
    1 point
  8. Thank you so much, it started working now after removing the extra unnecessary lines - But now it only works in case no Chrome windows were open when I run the script, otherwise, it will start a new window, without navigating to the link. And when I remove the user profile tags from the capabilities, it starts working again (even if I've previously opened Chrome tabs). Here is the updated code: #include "wd_helper.au3" #include "wd_capabilities.au3" #include "wd_core.au3" SetupChrome() local $sDesiredCapabilities = '{"capabilities": {"alwaysMatch": {"goog:chromeOptions": {"w3c": true, "args":["--user-data-dir=C:\\Users\\' & @UserName & '\\AppData\\Local\\Google\\Chrome\\User Data\\", "--profile-directory=Profile 2"]}}}}' $sSession = _WD_CreateSession($sDesiredCapabilities) _WD_Navigate($sSession, "https://www.google.com") Func SetupChrome() _WD_Option('Driver', 'chromedriver.exe') _WD_Option('Port', 9515) _WD_Option('DriverParams', '--verbose --log-path="' & @ScriptDir & '\chrome.log"') _WD_Option('DriverParams', '--marionette-port 2828') ;~ $_WD_DEBUG = $_WD_DEBUG_None ; EndFunc Error Log (in case a Chrome window was already open). _WD_Option ==> Success [0] : Parameters: Option=Driver Value=chromedriver.exe _WD_Option ==> Success [0] : Parameters: Option=Port Value=9515 _WD_Option ==> Success [0] : Parameters: Option=DriverParams Value=--verbose --log-path="C:\Users\mm\autoit\SciTe\chrome.log" _WD_Option ==> Success [0] : Parameters: Option=DriverParams Value=--marionette-port 2828 __WD_Post ==> Webdriver Exception [10] : HTTP status = 500 _WD_CreateSession ==> Webdriver Exception [10] __WD_Post ==> Invalid session ID [15] : HTTP status = 404 _WD_Navigate ==> Invalid session ID [15] : Parameters: URL=https://www.google.com Thank you for all the help!
    1 point
  9. It might be helpful it you showed us what was displayed there. Marionette only applies to Firefox, so this doesn't belong here. You manually defined the Capabilities in SetupChrome, so these lines aren't needed. Please remove or comment out this line and then show us the complete output from running your code above.
    1 point
×
×
  • Create New...