Intersoft Community - WebInput - WebInput setting readOnly in client side issue

WebInput setting readOnly in client side issue

lud310 — Mon, 04 Oct 2010 12:17:22 GMT

Your suggestion appears to be working. Thank you.

WebInput setting readOnly in client side issue

handy@intersoftpt.com — Wed, 29 Sep 2010 11:26:21 GMT

Hello Mark,

Please use SetReadOnly() instead of properties. It should be working as expected.

e.g IS_WI.SetReadOnly(true); //set read only

or IS_WI.SetReadOnly(false); // set writeable

Regards,
Handy

WebInput setting readOnly in client side issue

handy@intersoftpt.com — Tue, 28 Sep 2010 10:59:27 GMT

Hello Mark,

Ok, I will note this to our developer teams. I will get back to you when the fix is ready.

Regards,
Handy

WebInput setting readOnly in client side issue

lud310 — Tue, 28 Sep 2010 08:49:04 GMT

Handy,

I need this solved urgently. There are around ten web input controls in this application and this issue is causing major problem. Please escalate this and provide fix asap otherwise i'm in danger of missing dealine to release this application.

Thanks again

Mark

WebInput setting readOnly in client side issue

handy@intersoftpt.com — Mon, 27 Sep 2010 16:41:36 GMT

Hello Mark,

Ok, I can replicate the issue in here. I will report this to our developer teams.

Regards,
Handy

WebInput setting readOnly in client side issue

lud310 — Mon, 27 Sep 2010 11:44:38 GMT

I’m having a problem with WebInput setting ReadOnly property to true in client side.

IS_WI.ReadOnly = true;

var IS_WI = ISGetObject(controlId);

if (IS_WI) {

IS_WI.ReadOnly = true;

return true;

Steps to recreate issue

1.After form loads check if all the controls are usable(they should be)

2.Click on “make readonly” button

3.Click on the field with 2010-Oct-11 (we made this field read only)

4.Click on the other fields… that is where the issue is…other controls stopped responding until I click on “make writable” which sets IS_WI.ReadOnly = false;

Please investigate.

WebInput ver 4.0.7200.4

I’m attaching a sample code.

Mark

Using Enable()/Disable() is not an option for me.