jinyue115 Posted May 17, 2010 Posted May 17, 2010 --Launch a Apps and use AutoIT Window Info to get the Control ID . --Close the Apps then relanuch it , now note the the control ID is not same with previous. How it comes?
trancexx Posted May 17, 2010 Posted May 17, 2010 Anybody who can explain this ? Thank you !Your first post was sufficient enough for vast majority of readers. Probably you wouldn't want the answer from the rest. Also in English you do not put a space before an exclamation or question mark. Makes you look dumb really.But to answer your questions (in reverse order):YesSometimes it's done deliberately. To make (unwanted) automation harder. ♡♡♡ . eMyvnE
doudou Posted May 17, 2010 Posted May 17, 2010 --Launch a Apps and use AutoIT Window Info to get the Control ID .--Close the Apps then relanuch it , now note the the control ID is not same with previous.How it comes?Additionally to the reason mentioned by trancexx most applications that generate GUI controls dynamically would produce different IDs for each instance. AU3 GUIs give shiny example. UDFS & Apps: Spoiler DDEML.au3 - DDE Client + ServerLocalization.au3 - localize your scriptsTLI.au3 - type information on COM objects (TLBINF emulation)TLBAutoEnum.au3 - auto-import of COM constants (enums)AU3Automation - export AU3 scripts via COM interfacesTypeLibInspector - OleView was yesterday Coder's last words before final release: WE APOLOGIZE FOR INCONVENIENCE
jinyue115 Posted May 18, 2010 Author Posted May 18, 2010 Additionally to the reason mentioned by trancexx most applications that generate GUI controls dynamically would produce different IDs for each instance. AU3 GUIs give shiny example.Thx
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