I move scroll bar and i see parameters of user code

Bug reports.
yoad
Posts: 39
Joined: Sun May 26, 2013 9:08 am

I move scroll bar and i see parameters of user code

Post by yoad » Wed Aug 07, 2013 9:52 am

hello,
I copy user code from record1.rxrec to record2.rxrec

and I see all parameters of user code when I move scorll bar

please see picture
You do not have the required permissions to view the files attached to this post.

User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA
Contact:

Re: I move scroll bar and i see parameters of user code

Post by Support Team » Fri Aug 09, 2013 3:54 pm

Hello,

Could you please describe in detail what issue you are facing?
By the way which Ranorex version is in use?

Thanks,
Markus

yoad
Posts: 39
Joined: Sun May 26, 2013 9:08 am

Re: I move scroll bar and i see parameters of user code

Post by yoad » Mon Aug 12, 2013 1:22 pm

Hello Markus,
I used in version 4.0.5 of ranorex

please see parameters in the picture:"0ms","usercode","ChooseMenuItem",that they moved from their place
when I move scroll bar in mouse
you are understanding?

regards,
Yoad

User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA
Contact:

Re: I move scroll bar and i see parameters of user code

Post by Support Team » Wed Aug 14, 2013 3:13 pm

Hello Yoad,

May I ask you if you could check if you also see the issue with Ranorex 4.1?
Regards,
Markus

yoad
Posts: 39
Joined: Sun May 26, 2013 9:08 am

Re: I move scroll bar and i see parameters of user code

Post by yoad » Mon Aug 19, 2013 1:41 pm

I have bug in version 4.1
You do not have the required permissions to view the files attached to this post.

User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA
Contact:

Re: I move scroll bar and i see parameters of user code

Post by Support Team » Tue Aug 20, 2013 2:28 pm

Hi,

Please send your Ranorex solution to [email protected].
This will allow us to reproduce and analyze the issue!

Thanks,
Markus