Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 357717

Summary:	Progress bar does not update under some constellation
Product:	[RT] RAP	Reporter:	Manab <manab.nith>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	ivan
Version:	unspecified	Keywords:	needinfo
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Manab

2011-09-14 23:06:41 EDT

Build Identifier: I20080617-2000

This is a random problem which happens in my application. I use display.asyncExec()to update progress in UI. Sometimes there is no progress update and when I click at any place of my browser screen the screen updates just like processing one event. For example if the progress indicated 70 percent then after click it moves to 71 percent. If i keep on clicking it keep on updating.
I tried hard to understand what can cause this problem, but really fail to get any hint. 
Please let me know possible circumstances which can cause this kind of problem.

Reproducible: Sometimes

Steps to Reproduce:
1. Have a RAP workbench with a progress code.
2. Running progress many times results in this problem.
3. The progress stops updating and updates after mouse click

Comment 1 Ivan Furnadjiev

2011-09-15 00:31:37 EDT

Probably the UICallBack breaks and you run into one of these issue( bug 353318 or bug 260117). Which version of RAP are you using? In 1.5M1 we redesigned the UICallBack subsystem. Could you give RAP 1.5M1 a try?

Comment 2 Manab

2011-09-15 08:10:50 EDT

We are using RAP 1.3.1. Can i reproduce this issue if I have a bad network. If so I can be sure of my problem. Is there any work around for this problem.

Thank you very much very much for replying !!

 (In reply to comment #1)
> Probably the UICallBack breaks and you run into one of these issue( bug 353318
> or bug 260117). Which version of RAP are you using? In 1.5M1 we redesigned the
> UICallBack subsystem. Could you give RAP 1.5M1 a try?

(In reply to comment #1)
> Probably the UICallBack breaks and you run into one of these issue( bug 353318
> or bug 260117). Which version of RAP are you using? In 1.5M1 we redesigned the
> UICallBack subsystem. Could you give RAP 1.5M1 a try?

Comment 3 Ivan Furnadjiev

2011-09-15 08:27:52 EDT

(In reply to comment #2)
> We are using RAP 1.3.1. Can i reproduce this issue if I have a bad network. If
> so I can be sure of my problem. Is there any work around for this problem.
If you have a bad connection ( failing request ) the UICallBack breaks in RAP 1.3 (1.4). To reproduce the issue try to hit the ESC key when the progress is running. There is no workaround for this issue, which has been fixed in 1.5M1.

Comment 4 Ivan Furnadjiev

2011-09-15 08:33:01 EDT

I will mark this bug as duplicate of bug 260117. Please reopen if you disagree.

*** This bug has been marked as a duplicate of bug 260117 ***