strange behavior

[ayatest]

I'm using only variables to store window/control sizes and positions on the screen, hotkeys and mouseclicks (combined with these variables).

I noticed, that sometimes after modification - script isn't working correctly (each time) - mouse is shifted from proper positions. But after I push the script through debugger - it works fine there, and after that - it works correctly when running normally.

What an be reason for that?

[JohnOne]

Could be line 56.

[MikahS]

We would only be shooting in the dark trying to give suggestions. Can you post your script, please?

[ayatest]

It happens with all scripts, and probably not always. Only one script is running at the time, win81. Scripts are edited in non-autoit editor. So the question is regarding autoit and possibility for such problems to happen.

[MikahS]

Please, post your script so that we can see what you are seeing. If this problem was happening to everyone, then I would understand not posting it, but that is not the case.

What are you also trying to automate?

[Bowmore]

Could be line 56.

I don't think that's the problem I think the negative X value on line 428 is more likely the cause of the problem.

[water]

Sorry to disagree with you guys. But as Douglas Adams stated: The Answer is 42.

[SadBunny]

Sorry to disagree with you guys. But as Douglas Adams stated: The Answer is 42.

 

The answer is clear. The question is what the question is.

[AlisPT]

Post your script, it's easier for us to check what the problem might be. Try using AutoIT original editor and see if it works fine.

Edited March 25, 2015 by AlisPT

[ayatest]

Part of my job is to isolate problems in (related to) software.

This issue does not have to do with any particular script, it happens with various scripts. I noticed it today, so I'm not sure yet whether terminatng scripts may start cause it (that's why I pointed what kind of groups/types of operators I use) or something else. It looks as if each script was somehow "cached" by autoit when starting them, and if script is modified - some new values/variables were mixed with that cache. Debugger seems to clear the problem (at stage of use).

The question was whether someone experienced similar issues or whether this can happen in autoit under some "wrong" circumstances.

I will post something when I'm able to isolate some replicable basic routine to play with.

[JohnOne]

With your situation, and with the information I have, I'd look at firing the person who's writing the scripts.

[jdelaney]

It looks as if each script was somehow "cached" by autoit when starting them, and if script is modified - some new values/variables were mixed with that cache. Debugger seems to clear the problem (at stage of use).

Nope...there is no way to inject logic|coding into a running script...unless you are reading a file, or some outside source dictates what the script will do and THAT is modified.

Or, if your script is executing another script multiple times, and someone modifies the target script prior to the driver calling it.

Edited March 25, 2015 by jdelaney

[ayatest]

Consider this. Among constants. there are groups of problems that may happen to host app like autoit, groups of problems that may be present in scripts, and groups of problems that are some in between and ambiguous, and groups of problems that may be related to environment. This is what I'm being taught, and this is the perspective I look through. I don't want to repair any script or "bad routine" here, at least not at the moment; I clearly defined the scope of the question. Maybe I don't know autoit like you, but this is no reason to insult/abuse me in this indirect way you do, don't you think?

[ayatest]

Nope...there is no way to inject logic|coding into a running script...unless you are reading a file, or some outside source dictates what the script will do and THAT is modified.

Or, if your script is executing another script multiple times, and someone modifies the target script prior to the driver calling it.

 

Thanks for clarification on this part.

[JohnOne]

You list a lot of things that can "happen" there.

Here's another thing that can happen, that is not in your list...

The author of the scripts is useless at it, and that is why all the scripts have seemingly random errors.

If you can not accept that, or at least consider it, then, what is your job title again?

[ayatest]

It's not random.

Now you are offensive.

[Melba23]

ayatest,

Many people around the world use AutoIt daily and do not seem to suffer the same "random errors" as you appear to see. This suggests to me that the fault is more likely to be in the specific code you use rather then in AutoIt itself. But you are not providing any code samples nor specific instances of the errors you claim to see, so it is completely impossible to offer you any sensible advice on what might be the cause. >

While not being as blunt as JohnOne, I share his opinion on the most likely cause being the manner in which the scripts you use have been written. So I suggest you provide some code which we can run to test, because otherwise we are all just wasting bandwidth. To prevent this thread deteriorating further I am locking it - if and when you PM me some code to test I will reopen it.

M23

Edited March 25, 2015 by Melba23
English grammar