Takis Posted July 24, 2021 Share Posted July 24, 2021 Hello guys. When i run my script as application which uses ImageSearch after a while i get this message(+>@OSArch = x64 @Autoitx64=0 therefore using x32 Imagesearch DLL). What i want is to make this message not to appear. Is that possible???? Link to comment Share on other sites More sharing options...
Nine Posted July 24, 2021 Share Posted July 24, 2021 If the message comes from the DLL then it needs to be recompiled without it. But I am curious, what is so bad about showing such a message ? “They did not know it was impossible, so they did it” ― Mark Twain Spoiler Block all input without UAC Save/Retrieve Images to/from Text Monitor Management (VCP commands) Tool to search in text (au3) files Date Range Picker Virtual Desktop Manager Sudoku Game 2020 Overlapped Named Pipe IPC HotString 2.0 - Hot keys with string x64 Bitwise Operations Multi-keyboards HotKeySet Recursive Array Display Fast and simple WCD IPC Multiple Folders Selector Printer Manager GIF Animation (cached) Screen Scraping Multi-Threading Made Easy Link to comment Share on other sites More sharing options...
Takis Posted July 24, 2021 Author Share Posted July 24, 2021 First of all thanks for the fast reply. The problem is that when it shows up it appears in front of the picture that i need to find so Imagesearch cant spot the picture. What do you mean recompiled without it?? I created the scipt in computer "A" and moved it to another computer which doesnt have autoit script editor so it runs as an application. Link to comment Share on other sites More sharing options...
Nine Posted July 24, 2021 Share Posted July 24, 2021 2 minutes ago, Takis said: What do you mean recompiled without it? I mean, owner of the dll needs to recompile the dll without the message. 3 minutes ago, Takis said: when it shows up it appears in front of the picture Really ? Could you take a screenshot of the message over the picture and show us here... One thing you could try is to run your script in x64, maybe there will be no message then ? “They did not know it was impossible, so they did it” ― Mark Twain Spoiler Block all input without UAC Save/Retrieve Images to/from Text Monitor Management (VCP commands) Tool to search in text (au3) files Date Range Picker Virtual Desktop Manager Sudoku Game 2020 Overlapped Named Pipe IPC HotString 2.0 - Hot keys with string x64 Bitwise Operations Multi-keyboards HotKeySet Recursive Array Display Fast and simple WCD IPC Multiple Folders Selector Printer Manager GIF Animation (cached) Screen Scraping Multi-Threading Made Easy Link to comment Share on other sites More sharing options...
Takis Posted July 24, 2021 Author Share Posted July 24, 2021 here is the screenshot. it doesnt matter if you run it in x64 or x32. if you run it as an application and not as a script it always show this message when Imagesearch find the first picture Link to comment Share on other sites More sharing options...
Nine Posted July 24, 2021 Share Posted July 24, 2021 I see, that seems to be a AutoIt tooltip. Maybe it is the UDF itself that is displaying it and not the DLL ? Maybe you should use the DLL directly without the UDF ! Or look inside the UDF code to see if there is a tooltip message somewhere and remove it. “They did not know it was impossible, so they did it” ― Mark Twain Spoiler Block all input without UAC Save/Retrieve Images to/from Text Monitor Management (VCP commands) Tool to search in text (au3) files Date Range Picker Virtual Desktop Manager Sudoku Game 2020 Overlapped Named Pipe IPC HotString 2.0 - Hot keys with string x64 Bitwise Operations Multi-keyboards HotKeySet Recursive Array Display Fast and simple WCD IPC Multiple Folders Selector Printer Manager GIF Animation (cached) Screen Scraping Multi-Threading Made Easy Link to comment Share on other sites More sharing options...
Takis Posted July 24, 2021 Author Share Posted July 24, 2021 ok, i will try and see if it changes anything.Thanks for the reply Link to comment Share on other sites More sharing options...
JockoDundee Posted July 24, 2021 Share Posted July 24, 2021 Take @Nine’s suggestion - from 2 years ago: Code hard, but don’t hard code... Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now