cancel
Showing results for 
Search instead for 
Did you mean: 

Focus not coming on Text Edit

Former Member
0 Kudos

Hi all,

I have created an application in which i read data from the service and display on the view.

Whenever i run the application, all data gets displayed on the view correctly.

when i click on the TextEdit UI on the screen to enter then on a single click cursor is not getting displayed inside the UI.

If i wait for sometime and then after click it gets displayed

Any help would be greatly appreciated.

Regards,

Amol

Accepted Solutions (1)

Accepted Solutions (1)

siarhei_pisarenka3
Active Contributor
0 Kudos

Hi Amol

Such behavior depends on the WebDynpro Runtime version. If you have a chance to upgrade WebDynpro then the issue will disappear. For example, in my 7.00 SP13 it does not appear. If not - just forget about this, because you cannot do anything to fix it.

BR, Siarhei

Former Member
0 Kudos

Hi Siarhei,

You have told that upgrading WebDynpro will solve the issue

Is there any way to do that or you have any reference to look to solve the issue?

Thanks for your reply

siarhei_pisarenka3
Active Contributor
0 Kudos

Hi Amol

If you have a possibility to test your application on another WebDynpro version perhaps you will see the right behavior of the text edit control. If you have an access to another development server with another SP version then just deploy your app and test it.

I remember similar issue with focus in Input Fields. I cannot say exactly the version, but it was around 7.00 SP11 (maybe).

Sorry, but I cannot provide you with more detailed problem description.

BR, Siarhei

Former Member
0 Kudos

Hi Amol,

What it seems is the UI element (Text Edit) is not fully loaded by the time rest of the UI Elements load. Probably this is because it tries to read the context attribute (String type) to which it is bound and then try formatting the string to FormattedString which takes Tab Spaces and Newline characters into account before displaying. Definitely it takes larger time to consume the attribute value than the rest of the UI Elements. So, you cant much do anything about it.

But, this performance issue has been well addressed in the later versions of NWDS.

What you can do at max is to set the containing value to the context attribute at the erliest under wdDoInit().

Regards,

Tushar Sinha

Answers (3)

Answers (3)

Former Member
0 Kudos

Not answered, closing

former_member191569
Active Participant
0 Kudos

Hi Arnol,

we faced same problem when we upgrade from 7.0 SP14 to 7.0 SP17.

Looked like the problem arised because a component was not correctly upgraded, when they fixed it (fixed the component) the edit boxes behaviour was then correct.

Former Member
0 Kudos

Hello Amol,

This could be because of the portal settings. You can check with the portal administrator.

Regards,

Divyata