Intersoft Community - WebCombo - ClientSideEvents OnKeyDown Critical Problems

ClientSideEvents OnKeyDown Critical Problems

PRISMAY — Tue, 07 Jun 2011 08:23:40 GMT

Glad to hear. Thanks Yudi.

ClientSideEvents OnKeyDown Critical Problems

yudi — Tue, 07 Jun 2011 08:21:05 GMT

The “passes null for controlId and some random value for keyValue” has been fixed in 2011 R1.

To add a client-side event, I recommend you to add it in OnInit or OnLoad event instead of in OnPreRender.

ClientSideEvents OnKeyDown Critical Problems

PRISMAY — Thu, 02 Jun 2011 09:23:30 GMT

Yudi,

Has this been fixed in 2011 R1?

ClientSideEvents OnKeyDown Critical Problems

PRISMAY — Thu, 24 Jun 2010 08:09:07 GMT

Hi Yudi,

No we can't go back, but thankfully we have a workaround which works right now. My only concern in the workaround implmentation is that it can break if the architecture changes in a future release and that's why it would be nice to have a fix so we don't have to rely on infused code for a workaround. Thanks a lot.

ClientSideEvents OnKeyDown Critical Problems

yudi — Wed, 23 Jun 2010 16:53:45 GMT

Thank you very much for your patience and understanding.

I’ll inform you at once if I heard any news regarding this work item. Meanwhile, is it possible for your project to use the old version of WebCombo 4 assembly?

ClientSideEvents OnKeyDown Critical Problems

PRISMAY — Tue, 22 Jun 2010 17:40:25 GMT

Hi Yudi,

Thanks for checking. We have a workaround for now but would really like this fixed soon. Also, we do not hard-code control names into any of our client-side code because we can't since we don't know what control triggers this handler. It's easy to do that when you have a simple page, but we work with a very complicated application with many controls.

I hope we can get a fix soon though. Thanks again.

ClientSideEvents OnKeyDown Critical Problems

yudi — Tue, 22 Jun 2010 16:38:21 GMT

I have checked the status of work item #702 and find that the work item has not been fixed yet.

You may try to replace controlId parameter with the id of your WebCombo as a workaround of this issue.

function WebCombo1_OnKeyDown(controlId, keyValue) {
    //ISGetObject(controlId) is equals to
    //ISGetObject("WebCombo1")
    //Note: WebCombo1 is the ID of the corresponding WebCombo
    var WebCombo1 = ISGetObject(controlId);
    var WebCombo1 = ISGetObject("WebCombo1");

    return true;
}

I’ll keep you updated as soon as I heard news from the team regarding status of this work item.

ClientSideEvents OnKeyDown Critical Problems

PRISMAY — Mon, 21 Jun 2010 09:43:28 GMT

I have forwarded this issue to WebCombo development team. A work item, #702, has been submitted regarding this minor glitch. ...

Yudi,

Will you update threads when an item has been fixed and is released in a build/patch? Basically, how will I know when this (or any other) fix has been implemented? Thank you.

ClientSideEvents OnKeyDown Critical Problems

PRISMAY — Mon, 24 May 2010 10:15:20 GMT

Thank you, but I would not consider this a "minor" glitch as it creates a big headache for the workaround we had to create.

ClientSideEvents OnKeyDown Critical Problems

yudi — Fri, 07 May 2010 16:48:42 GMT

I have forwarded this issue to WebCombo development team. A work item, #702, has been submitted regarding this minor glitch.

I’ll keep you updated with any new I heard from the team regarding this work item.

Thank you for your valuable feedback.

ClientSideEvents OnKeyDown Critical Problems

PRISMAY — Thu, 06 May 2010 14:54:11 GMT

Hello,

We're running into several problems implementing this. You'll be able to duplicate this with a simple project. Please make sure to test with both bound and unbound data sets.

OnKeyDown fires but passes null for controlId and some random value for keyValue
Inside a control that derives from WebCombo, OnKeyDown will only fire if it's set in OnInit or OnLoad but will not fire/render when set in OnPreRender using a line like this as an example:

this.LayoutSettings.ClientSideEvents.OnKeyDown = "MyClient.OnKeyDown";

Our main concern though is that when it is firing, we're not getting the control id and this very very bad since we can't determine the source of the call.

I'll try, in the meantime, to add our own HTML onkeydown by using the HTML attributes and see if that does what we need, but we do need a resolution to this right away please. Thank you.