[Solved] TouchHandlerController generate memory leak?

[Alessio]

Hi,

I've found a possible cause of memory leak inside ScheduleView, it doesn't destroyed due to TouchHandlerController.

I'm using 2012.3.1129.1050 version: how I can disable touch feature, PinchToZoom or other?

Thanks a lot.

- Alessio

[Rosi]

Hi,

At this stage you can set the IsTouchEnabled property of the TouchManager instance on application level.

Setting it to False will destroy any existent TouchHandlers and unsubscribe from any MS TouchEvents internally. This will also prevent the further creation of such handlers until it is set back to True.

Setting it to True on a later stage will again turn on the creation of new elements, however, it will not restore any of the previously disposed ones.

Hope this helps.

Regards,
Rosi
Telerik

 

 

[Alessio]

Hi Rosi,

Thanks for the answer.

In my 2012.3.1129.1050 Version I can't find TouchManager, where is it?

[Rosi]

Hi,

The IsTouchEnabled property that you can use is introduced in version Q2 2014. To complete the task I suggest you upgrade to higher version of the controls.

Regards,
Rosi
Telerik

 

 

[Alessio]

I don't know if my customer's license covers this upgrade and, let me say, we are already in production environment so an upgrade requires a lot of no-regression test.

Can I do anything else?

[Rosi]

Hello,

I understand the situation, however before Q2 2014 a option for disabling the touch support is not available.

I am sorry for the inconvenience that this causes to you.

Regards,
Rosi
Telerik