Please go through the module and let me know the solution as soon as possible.

The solution to what?

Have you identified a particular problem, or do you expect me to go through all 907 lines and find it for you as well?

I am waiting for ur reply...

Ur gna B w8ing a tiiiiiiiiiiiiiiiiiiiiiiiiiime.

Life line

If I understand the implications of your posts, you are saying that when you call a particular Win32::GuiTest function, with particular arguments, on 64-bit Windows, you aren't getting the result you expect.

If that is the case, don't throw 1000 lines of code at me -- that I can't run without building an application, and won't demonstrate the problem unless I accidentally hit the exact scenario in which you are seeing failures. Can you not see that you will never get help that way?

Think! Start from the point of known failure. Construct a script that recreates that failure:

• simple: forget OO, forget tests, forget comment blocks, forget your uni/company/personal coding standards.

  You are not creating a work of art, nor a thesis project, nor a legacy for your children, nor an advertisement for your programming skills.

  Your responsibility is to demonstrate the problem as simply as possible.

• short: 20 lines would be good. 100 lines is okay if they are all actually required.

  1000 lines is just taking the piss.

  Without getting silly and golfing, the fewer lines the better.

• standalone: no modules or dependencies.

  Not even your personal favorite test::more::morestill::best::bestist::bestistButBetter::* test suite. I probably don't have; certainly don't want it; wouldn't trust it anyway, and won't install it.

  The easier it is for people to run your sample code, the more likely some of them are to try it.

  Throwing a 1000 line module, with no script that exercises it and no clear indication of the problem you've encountered, doesn't enable that.

Make it easy for those you asking for (free) help. Normally, I would simply be ignoring your post, but you've obviously taken a lot of time and put in a lot of work.

You've just expended it in the wrong place to enable anyone here to help you.